[web] bump F21 Sysadmin guide
Pete Travis
immanetize at fedoraproject.org
Fri Mar 6 05:46:43 UTC 2015
commit 30b774f52cf0ba0f27c5733f7e60728163afc1d1
Author: Pete Travis <immanetize at fedoraproject.org>
Date: Thu Mar 5 22:46:41 2015 -0700
bump F21 Sysadmin guide
fedoradocs.db | Bin 1086464 -> 1086464 bytes
public_html/Sitemap | 52 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/as-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/as-IN/opds-Fedora_Core.xml | 2 +-
public_html/as-IN/opds-Fedora_Documentation.xml | 2 +-
.../as-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/as-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/as-IN/opds.xml | 16 +-
public_html/as-IN/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bg-BG/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bg-BG/opds-Fedora_Core.xml | 2 +-
public_html/bg-BG/opds-Fedora_Documentation.xml | 2 +-
.../bg-BG/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bg-BG/opds-Fedora_Security_Team.xml | 2 +-
public_html/bg-BG/opds.xml | 16 +-
public_html/bg-BG/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bn-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bn-IN/opds-Fedora_Core.xml | 2 +-
public_html/bn-IN/opds-Fedora_Documentation.xml | 2 +-
.../bn-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bn-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/bn-IN/opds.xml | 16 +-
public_html/bn-IN/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/bs-BA/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/bs-BA/opds-Fedora_Core.xml | 2 +-
public_html/bs-BA/opds-Fedora_Documentation.xml | 2 +-
.../bs-BA/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/bs-BA/opds-Fedora_Security_Team.xml | 2 +-
public_html/bs-BA/opds.xml | 16 +-
public_html/bs-BA/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ca-ES/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ca-ES/opds-Fedora_Core.xml | 2 +-
public_html/ca-ES/opds-Fedora_Documentation.xml | 2 +-
.../ca-ES/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ca-ES/opds-Fedora_Security_Team.xml | 2 +-
public_html/ca-ES/opds.xml | 16 +-
public_html/ca-ES/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/cs-CZ/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/cs-CZ/opds-Fedora_Core.xml | 2 +-
public_html/cs-CZ/opds-Fedora_Documentation.xml | 2 +-
.../cs-CZ/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/cs-CZ/opds-Fedora_Security_Team.xml | 2 +-
public_html/cs-CZ/opds.xml | 16 +-
public_html/cs-CZ/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/da-DK/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/da-DK/opds-Fedora_Core.xml | 2 +-
public_html/da-DK/opds-Fedora_Documentation.xml | 2 +-
.../da-DK/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/da-DK/opds-Fedora_Security_Team.xml | 2 +-
public_html/da-DK/opds.xml | 16 +-
public_html/da-DK/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/de-DE/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/de-DE/opds-Fedora_Core.xml | 2 +-
public_html/de-DE/opds-Fedora_Documentation.xml | 2 +-
.../de-DE/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/de-DE/opds-Fedora_Security_Team.xml | 2 +-
public_html/de-DE/opds.xml | 16 +-
public_html/de-DE/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/el-GR/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/el-GR/opds-Fedora_Core.xml | 2 +-
public_html/el-GR/opds-Fedora_Documentation.xml | 2 +-
.../el-GR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/el-GR/opds-Fedora_Security_Team.xml | 2 +-
public_html/el-GR/opds.xml | 16 +-
public_html/el-GR/toc.html | 14 +-
...edora-21-System_Administrators_Guide-en-US.epub | Bin 14290504 -> 14797564 bytes
.../images/managing_users.png | Bin 0 -> 34627 bytes
.../images/printconf-main.png | Bin 13800 -> 18637 bytes
.../images/redhat-filter-enable.png | Bin 0 -> 967679 bytes
.../images/redhat-filter-sample.png | Bin 0 -> 358405 bytes
.../images/redhat-filters.png | Bin 0 -> 309252 bytes
.../images/redhat-logviewer-add.png | Bin 0 -> 965881 bytes
.../images/redhat-logviewer-monitoring.png | Bin 0 -> 967679 bytes
.../images/redhat-logviewer.png | Bin 0 -> 965270 bytes
.../images/rsyslog_message_flow.png | Bin 0 -> 73315 bytes
.../System_Administrators_Guide/index.html | 4942 +++++++++++++-------
.../app-Revision_History.html | 9 +-
.../ch-Automating_System_Tasks.html | 10 +-
.../ch-Configuring_PTP_Using_ptp4l.html | 2 +-
.../ch-Configuring_the_Date_and_Time.html | 2 +-
.../ch-Directory_Servers.html | 336 +-
.../ch-File_and_Print_Servers.html | 120 +-
.../ch-Mail_Servers.html | 12 +-
.../ch-Managing_Users_and_Groups.html | 28 +-
.../ch-Manually_Upgrading_the_Kernel.html | 20 +-
.../System_Administrators_Guide/ch-OProfile.html | 37 +-
.../System_Administrators_Guide/ch-OpenSSH.html | 20 +-
.../ch-Opening_GUI_Applications.html | 2 +-
.../html/System_Administrators_Guide/ch-RPM.html | 66 +-
.../ch-Services_and_Daemons.html | 4 +-
...h-System_Locale_and_Keyboard_Configuration.html | 4 +-
.../ch-System_Monitoring_Tools.html | 8 +-
.../System_Administrators_Guide/ch-TigerVNC.html | 22 +-
.../ch-Viewing_and_Managing_Log_Files.html | 311 +--
.../ch-Web_Servers.html | 244 +-
.../ch-Working_with_Kernel_Modules.html | 12 +-
.../ch-Working_with_the_GRUB_2_Boot_Loader.html | 47 +
.../html/System_Administrators_Guide/ch-yum.html | 18 +-
.../System_Administrators_Guide/ch01s03s03.html | 2 +-
.../images/managing_users.png | Bin 0 -> 34627 bytes
.../images/printconf-main.png | Bin 13800 -> 18637 bytes
.../images/redhat-filter-enable.png | Bin 0 -> 967679 bytes
.../images/redhat-filter-sample.png | Bin 0 -> 358405 bytes
.../images/redhat-filters.png | Bin 0 -> 309252 bytes
.../images/redhat-logviewer-add.png | Bin 0 -> 965881 bytes
.../images/redhat-logviewer-monitoring.png | Bin 0 -> 967679 bytes
.../images/redhat-logviewer.png | Bin 0 -> 965270 bytes
.../images/rsyslog_message_flow.png | Bin 0 -> 73315 bytes
.../21/html/System_Administrators_Guide/index.html | 8 +-
.../21/html/System_Administrators_Guide/ix01.html | 2 +-
.../part-Basic_System_Configuration.html | 4 +-
.../part-Infrastructure_Services.html | 4 +-
...art-Kernel_Module_and_Driver_Configuration.html | 4 +-
.../part-Monitoring_and_Automation.html | 4 +-
.../part-Package_Management.html | 4 +-
.../System_Administrators_Guide/part-Servers.html | 4 +-
.../21/html/System_Administrators_Guide/pr01.html | 4 +-
.../html/System_Administrators_Guide/pr01s03.html | 4 +-
.../System_Administrators_Guide/pr01s03s02.html | 2 +-
.../System_Administrators_Guide/pr01s03s03.html | 2 +-
.../html/System_Administrators_Guide/pr01s04.html | 2 +-
.../s1-Changing_the_Keyboard_Layout.html | 2 +-
.../s1-Configuring_the_Hardware_Clock_update.html | 2 +-
.../html/System_Administrators_Guide/s1-FTP.html | 6 +-
.../s1-Using_the_Journal.html | 73 +
.../s1-autotasks-additional-resources.html | 2 +-
.../s1-autotasks-at-batch.html | 2 +-
.../s1-basic_configuration_of_rsyslog.html | 117 +
.../s1-check-rpm-sig.html | 40 +-
.../s1-debugging_rsyslog.html | 22 +
.../s1-email-additional-resources.html | 4 +-
.../System_Administrators_Guide/s1-email-mda.html | 4 +-
.../System_Administrators_Guide/s1-email-mta.html | 4 +-
.../System_Administrators_Guide/s1-email-mua.html | 14 +-
.../s1-email-types.html | 4 +-
.../s1-find-verify-rpm.html | 25 +
.../s1-interaction_of_rsyslog_and_journal.html | 39 +
.../s1-kernel-boot-loader.html | 38 +-
.../s1-kernel-download.html | 8 +-
.../s1-kernel-modules-additional-resources.html | 6 +-
.../s1-kernel-perform-upgrade.html | 8 +-
.../s1-kernel-preparing.html | 26 +-
.../s1-log-files-additional-resources.html | 36 +-
...aging_log_files_in_a_graphical_environment.html | 53 +
.../s1-openssh-additional-resources.html | 2 +-
.../s1-oprofile-analyzing-data.html | 27 +-
.../s1-oprofile-and-systemtap.html | 12 +-
.../s1-oprofile-configuring.html | 24 +-
.../s1-oprofile-dev-oprofile.html | 10 +-
.../s1-oprofile-example-usage.html | 8 +-
.../s1-oprofile-gui.html | 24 +-
.../s1-oprofile-java-support.html | 24 +-
.../s1-oprofile-saving-data.html | 12 +-
.../s1-oprofile-starting.html | 14 +-
.../s1-oprofile_additional_resources.html | 21 +
.../s1-printing-additional-resources.html | 4 +-
.../s1-printing-edit.html | 8 +-
.../s1-printing-ipp-printer.html | 6 +-
.../s1-printing-jetdirect-printer.html | 2 +-
.../s1-printing-smb-printer.html | 2 +-
.../s1-rpm-additional-resources.html | 20 +-
.../s1-rpm-usage-examples.html | 27 +
.../System_Administrators_Guide/s1-rpm-using.html | 80 +-
.../s1-services-running.html | 2 +-
.../s1-ssh-beyondshell.html | 2 +-
.../s1-ssh-clients.html | 4 +-
.../s1-ssh-configuration.html | 4 +-
.../s1-structured_logging_with_rsyslog.html | 55 +
.../s1-sysinfo-cpu.html | 2 +-
.../s1-sysinfo-filesystems.html | 2 +-
.../s1-sysinfo-hardware.html | 2 +-
.../s1-sysinfo-memory-usage.html | 2 +-
.../s1-users-configui.html | 16 +-
.../s1-users-tools.html | 50 +-
.../s1-using-operf.html | 31 +
.../s1-using_rsyslog_modules.html | 77 +
.../System_Administrators_Guide/s1-using_ssh.html | 10 +-
.../s1-working_with_queues_in_rsyslog.html | 113 +
.../s2-Access_Control.html | 13 +
.../System_Administrators_Guide/s2-Actions.html | 137 +
.../s2-Enabling_Persistent_Storage.html | 29 +
.../s2-Filtering_Messages.html | 59 +
.../System_Administrators_Guide/s2-Rulesets.html | 44 +
.../System_Administrators_Guide/s2-Templates.html | 75 +
.../s2-Using_The_Live_View.html | 13 +
.../s2-compatibility_with_syslogd.html | 13 +
.../s2-email-mta-fetchmail.html | 16 +-
.../s2-email-mta-sendmail.html | 22 +-
.../s2-email-procmail-recipes.html | 16 +-
.../s2-email-related-books.html | 2 +-
.../s2-email-switchmail.html | 4 +-
.../s2-email-types-mda.html | 2 +-
.../s2-email-types-mua.html | 2 +-
.../s2-email-useful-websites.html | 2 +-
.../s2-enabling_encrypted_transport.html | 15 +
.../s2-exporting_messages_to_a_database.html | 20 +
.../s2-filtering_structured_messages.html | 17 +
.../s2-ftp-resources.html | 6 +-
.../s2-ftp-servers.html | 2 +-
.../s2-ftp-vsftpd-conf.html | 18 +-
.../s2-ftp-vsftpd-start.html | 8 +-
.../s2-global_directives.html | 17 +
.../s2-kernel-boot-loader-iseries.html | 6 +-
.../s2-kernel-boot-loader-pseries.html | 6 +-
.../s2-log_rotation.html | 74 +
.../s2-logfiles-adding.html | 17 +
.../s2-logfiles-examining.html | 13 +
.../s2-managing_queues.html | 49 +
.../s2-operf-categorization.html | 13 +
.../s2-operf-events.html | 53 +
.../s2-oprofile-events.html | 187 +-
.../s2-oprofile-module-output.html | 8 +-
.../s2-oprofile-reading-opannotate.html | 12 +-
.../s2-oprofile-reading-opreport-single.html | 28 +-
.../s2-oprofile-starting-separate.html | 20 +-
.../s2-parsing_JSON.html | 19 +
.../s2-rpm-freshening.html | 24 +-
.../s2-rpm-querying.html | 37 +-
.../s2-rpm-uninstalling.html | 29 +-
.../s2-rpm-verifying.html | 120 +-
.../s2-ssh-beyondshell-tcpip.html | 2 +-
.../s2-ssh-clients-scp.html | 2 +-
.../s2-ssh-clients-sftp.html | 2 +-
.../s2-ssh-configuration-keypairs.html | 14 +-
.../s2-ssh-configuration-requiring.html | 2 +-
.../s2-ssh-configuration-sshd.html | 6 +-
.../s2-storing_messages_in_the_mongodb.html | 25 +
.../s2-sysinfo-filesystems-blkid.html | 2 +-
.../s2-sysinfo-filesystems-df.html | 4 +-
.../s2-sysinfo-filesystems-du.html | 2 +-
.../s2-sysinfo-filesystems-findmnt.html | 2 +-
.../s2-sysinfo-filesystems-partx.html | 2 +-
.../s2-sysinfo-filesystems-system_monitor.html | 2 +-
.../s2-sysinfo-hardware-lscpu.html | 2 +-
.../s2-sysinfo-hardware-lspcmcia.html | 2 +-
.../s2-sysinfo-hardware-lsusb.html | 2 +-
.../s2-sysinfo-memory-usage-system_monitor.html | 2 +-
.../s2-users-tools-groups-add.html | 6 +-
.../s2-users-tools-groups-directories.html | 18 +-
.../s2-users-tools-password-aging.html | 6 +-
.../System_Administrators_Guide/s2-using_RELP.html | 11 +
.../s2-using_the_new_configuration_format.html | 26 +
.../s3-ftp-vsftpd-conf.html | 2 +-
.../System_Administrators_Guide/s5-vnc-viewer.html | 4 +-
.../s6-connecting-vnc-viewer.html | 10 +-
.../s9-additional-sources.html | 4 +-
.../sec-Adding_Other_Printer.html | 2 +-
.../sec-Adding_a_new_Entry.html | 21 +
.../sec-Additional_Resources.html | 2 +-
.../sec-Booting_to_Emergency_Mode.html | 21 +
...c-Changing_and_Resetting_the_Root_Password.html | 107 +
.../sec-Configuring_Yum_and_Yum_Repositories.html | 6 +-
.../sec-Configuring_timemaster_Options.html | 41 +
.../sec-Creating_a_Yum_Repository.html | 2 +-
.../sec-Customizing_GRUB_2_Menu.html | 57 +
.../sec-Displaying_Information_About_a_Module.html | 18 +-
.../sec-Displaying_Package_Information.html | 4 +-
.../sec-Editing_an_Entry.html | 25 +
.../sec-GRUB_2_Password_Protection.html | 66 +
.../sec-GRUB_2_over_Serial_Console.html | 32 +
.../sec-Improving_Accuracy.html | 14 +-
.../sec-Installing.html | 4 +-
.../sec-Listing_Packages.html | 24 +-
.../sec-Loading_a_Module.html | 21 +-
.../sec-Managing_Yum_Repositories.html | 2 +-
.../sec-PTP_additional_resources.html | 10 +-
.../sec-PTP_useful-websites.html | 6 +-
.../sec-Packages_and_Package_Groups.html | 4 +-
.../sec-Password_Encryption.html | 27 +
.../sec-Persistent_Module_Loading.html | 10 +-
.../sec-Plugin_Descriptions.html | 10 +-
.../sec-Printer_Configuration.html | 20 +-
.../sec-Reinstalling_GRUB_2.html | 21 +
.../System_Administrators_Guide/sec-Removing.html | 8 +-
.../sec-Resetting_and_Reinstalling_GRUB_2.html | 31 +
.../sec-Serving_NTP_Time_with_PTP.html | 16 +-
.../sec-Setting_Module_Parameters.html | 14 +-
.../sec-Setting_Printer.html | 8 +-
.../sec-Setting_repository_Options.html | 2 +-
.../sec-Starting_ptp4l.html | 6 +
...ronize_to_PTP_or_NTP_Time_Using_timemaster.html | 17 +
.../sec-Synchronizing_the_Clocks.html | 12 +-
.../sec-Terminal_Menu_Editing_During_Boot.html | 25 +
.../sec-UEFI_Secure_Boot.html | 29 +
...standing_the_timemaster_Configuration_File.html | 79 +
.../sec-Unloading_a_Module.html | 12 +-
.../System_Administrators_Guide/sec-Using_PTP.html | 2 +-
.../sec-Using_Yum_Variables.html | 2 +-
.../sec-Using_only_a_Custom_Menu.html | 79 +
...ng_screen_to_Connect_to_the_Serial_Console.html | 19 +
.../sec-Verifying_the_Initial_RAM_Disk_Image.html | 66 +-
...he_GRUB_2_Boot_Loader-Additional_Resources.html | 17 +
.../sec-Yum_Plugins.html | 4 +-
.../sec-printing-LPDLPR-printer.html | 4 +-
.../sect-Keyboard_Configuration-Resources.html | 2 +-
.../sect-Preface-Book_Organization.html | 4 +-
.../sect-Users_and_Groups-Resources.html | 43 +
...sect-enrolling-public-key-on-target-system.html | 35 +
...-generating-a-public-private-x509-key-pair.html | 37 +
.../sect-kernel-module-authentication.html | 198 +
.../sect-loading-signed-kernel-module.html | 24 +
...signing-kernel-module-with-the-private-key.html | 21 +
...ect-signing-kernel-modules-for-secure-boot.html | 69 +
...Fedora-21-System_Administrators_Guide-en-US.pdf | Bin 11103263 -> 11492221 bytes
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/en-US/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/en-US/opds-Fedora_Core.xml | 2 +-
public_html/en-US/opds-Fedora_Documentation.xml | 2 +-
.../en-US/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/en-US/opds-Fedora_Security_Team.xml | 2 +-
public_html/en-US/opds.xml | 16 +-
public_html/en-US/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/es-ES/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/es-ES/opds-Fedora_Core.xml | 2 +-
public_html/es-ES/opds-Fedora_Documentation.xml | 2 +-
.../es-ES/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/es-ES/opds-Fedora_Security_Team.xml | 2 +-
public_html/es-ES/opds.xml | 16 +-
public_html/es-ES/toc.html | 8 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fa-IR/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fa-IR/opds-Fedora_Core.xml | 2 +-
public_html/fa-IR/opds-Fedora_Documentation.xml | 2 +-
.../fa-IR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fa-IR/opds-Fedora_Security_Team.xml | 2 +-
public_html/fa-IR/opds.xml | 16 +-
public_html/fa-IR/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fi-FI/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fi-FI/opds-Fedora_Core.xml | 2 +-
public_html/fi-FI/opds-Fedora_Documentation.xml | 2 +-
.../fi-FI/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fi-FI/opds-Fedora_Security_Team.xml | 2 +-
public_html/fi-FI/opds.xml | 16 +-
public_html/fi-FI/toc.html | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/fr-FR/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/fr-FR/opds-Fedora_Core.xml | 2 +-
public_html/fr-FR/opds-Fedora_Documentation.xml | 2 +-
.../fr-FR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/fr-FR/opds-Fedora_Security_Team.xml | 2 +-
public_html/fr-FR/opds.xml | 16 +-
public_html/fr-FR/toc.html | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/gu-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/gu-IN/opds-Fedora_Core.xml | 2 +-
public_html/gu-IN/opds-Fedora_Documentation.xml | 2 +-
.../gu-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/gu-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/gu-IN/opds.xml | 16 +-
public_html/gu-IN/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/he-IL/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/he-IL/opds-Fedora_Core.xml | 2 +-
public_html/he-IL/opds-Fedora_Documentation.xml | 2 +-
.../he-IL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/he-IL/opds-Fedora_Security_Team.xml | 2 +-
public_html/he-IL/opds.xml | 16 +-
public_html/he-IL/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/hi-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/hi-IN/opds-Fedora_Core.xml | 2 +-
public_html/hi-IN/opds-Fedora_Documentation.xml | 2 +-
.../hi-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/hi-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/hi-IN/opds.xml | 16 +-
public_html/hi-IN/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/hu-HU/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/hu-HU/opds-Fedora_Core.xml | 2 +-
public_html/hu-HU/opds-Fedora_Documentation.xml | 2 +-
.../hu-HU/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/hu-HU/opds-Fedora_Security_Team.xml | 2 +-
public_html/hu-HU/opds.xml | 16 +-
public_html/hu-HU/toc.html | 14 +-
.../ia/opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ia/opds-Fedora.xml | 4 +-
.../ia/opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ia/opds-Fedora_Core.xml | 2 +-
public_html/ia/opds-Fedora_Documentation.xml | 2 +-
public_html/ia/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ia/opds-Fedora_Security_Team.xml | 2 +-
public_html/ia/opds.xml | 16 +-
public_html/ia/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/id-ID/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/id-ID/opds-Fedora_Core.xml | 2 +-
public_html/id-ID/opds-Fedora_Documentation.xml | 2 +-
.../id-ID/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/id-ID/opds-Fedora_Security_Team.xml | 2 +-
public_html/id-ID/opds.xml | 16 +-
public_html/id-ID/toc.html | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/it-IT/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/it-IT/opds-Fedora_Core.xml | 2 +-
public_html/it-IT/opds-Fedora_Documentation.xml | 2 +-
.../it-IT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/it-IT/opds-Fedora_Security_Team.xml | 2 +-
public_html/it-IT/opds.xml | 16 +-
public_html/it-IT/toc.html | 10 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ja-JP/opds-Fedora.xml | 2 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ja-JP/opds-Fedora_Core.xml | 2 +-
public_html/ja-JP/opds-Fedora_Documentation.xml | 2 +-
.../ja-JP/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ja-JP/opds-Fedora_Security_Team.xml | 2 +-
public_html/ja-JP/opds.xml | 16 +-
public_html/ja-JP/toc.html | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/kn-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/kn-IN/opds-Fedora_Core.xml | 2 +-
public_html/kn-IN/opds-Fedora_Documentation.xml | 2 +-
.../kn-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/kn-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/kn-IN/opds.xml | 16 +-
public_html/kn-IN/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ko-KR/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ko-KR/opds-Fedora_Core.xml | 2 +-
public_html/ko-KR/opds-Fedora_Documentation.xml | 2 +-
.../ko-KR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ko-KR/opds-Fedora_Security_Team.xml | 2 +-
public_html/ko-KR/opds.xml | 16 +-
public_html/ko-KR/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/lt-LT/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/lt-LT/opds-Fedora_Core.xml | 2 +-
public_html/lt-LT/opds-Fedora_Documentation.xml | 2 +-
.../lt-LT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/lt-LT/opds-Fedora_Security_Team.xml | 2 +-
public_html/lt-LT/opds.xml | 16 +-
public_html/lt-LT/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ml-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ml-IN/opds-Fedora_Core.xml | 2 +-
public_html/ml-IN/opds-Fedora_Documentation.xml | 2 +-
.../ml-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ml-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/ml-IN/opds.xml | 16 +-
public_html/ml-IN/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/mr-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/mr-IN/opds-Fedora_Core.xml | 2 +-
public_html/mr-IN/opds-Fedora_Documentation.xml | 2 +-
.../mr-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/mr-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/mr-IN/opds.xml | 16 +-
public_html/mr-IN/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/nb-NO/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/nb-NO/opds-Fedora_Core.xml | 2 +-
public_html/nb-NO/opds-Fedora_Documentation.xml | 2 +-
.../nb-NO/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/nb-NO/opds-Fedora_Security_Team.xml | 2 +-
public_html/nb-NO/opds.xml | 16 +-
public_html/nb-NO/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/nl-NL/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/nl-NL/opds-Fedora_Core.xml | 2 +-
public_html/nl-NL/opds-Fedora_Documentation.xml | 2 +-
.../nl-NL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/nl-NL/opds-Fedora_Security_Team.xml | 2 +-
public_html/nl-NL/opds.xml | 16 +-
public_html/nl-NL/toc.html | 20 +-
public_html/opds.xml | 92 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/or-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/or-IN/opds-Fedora_Core.xml | 2 +-
public_html/or-IN/opds-Fedora_Documentation.xml | 2 +-
.../or-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/or-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/or-IN/opds.xml | 16 +-
public_html/or-IN/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pa-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pa-IN/opds-Fedora_Core.xml | 2 +-
public_html/pa-IN/opds-Fedora_Documentation.xml | 2 +-
.../pa-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pa-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/pa-IN/opds.xml | 16 +-
public_html/pa-IN/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pl-PL/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pl-PL/opds-Fedora_Core.xml | 2 +-
public_html/pl-PL/opds-Fedora_Documentation.xml | 2 +-
.../pl-PL/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pl-PL/opds-Fedora_Security_Team.xml | 2 +-
public_html/pl-PL/opds.xml | 16 +-
public_html/pl-PL/toc.html | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pt-BR/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pt-BR/opds-Fedora_Core.xml | 2 +-
public_html/pt-BR/opds-Fedora_Documentation.xml | 2 +-
.../pt-BR/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pt-BR/opds-Fedora_Security_Team.xml | 2 +-
public_html/pt-BR/opds.xml | 16 +-
public_html/pt-BR/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/pt-PT/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/pt-PT/opds-Fedora_Core.xml | 2 +-
public_html/pt-PT/opds-Fedora_Documentation.xml | 2 +-
.../pt-PT/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/pt-PT/opds-Fedora_Security_Team.xml | 2 +-
public_html/pt-PT/opds.xml | 16 +-
public_html/pt-PT/toc.html | 16 +-
.../ro/opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ro/opds-Fedora.xml | 4 +-
.../ro/opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ro/opds-Fedora_Core.xml | 2 +-
public_html/ro/opds-Fedora_Documentation.xml | 2 +-
public_html/ro/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ro/opds-Fedora_Security_Team.xml | 2 +-
public_html/ro/opds.xml | 16 +-
public_html/ro/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ru-RU/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ru-RU/opds-Fedora_Core.xml | 2 +-
public_html/ru-RU/opds-Fedora_Documentation.xml | 2 +-
.../ru-RU/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ru-RU/opds-Fedora_Security_Team.xml | 2 +-
public_html/ru-RU/opds.xml | 16 +-
public_html/ru-RU/toc.html | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sk-SK/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sk-SK/opds-Fedora_Core.xml | 2 +-
public_html/sk-SK/opds-Fedora_Documentation.xml | 2 +-
.../sk-SK/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sk-SK/opds-Fedora_Security_Team.xml | 2 +-
public_html/sk-SK/opds.xml | 16 +-
public_html/sk-SK/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sr-Latn-RS/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sr-Latn-RS/opds-Fedora_Core.xml | 2 +-
.../sr-Latn-RS/opds-Fedora_Documentation.xml | 2 +-
.../sr-Latn-RS/opds-Fedora_Draft_Documentation.xml | 2 +-
.../sr-Latn-RS/opds-Fedora_Security_Team.xml | 2 +-
public_html/sr-Latn-RS/opds.xml | 16 +-
public_html/sr-Latn-RS/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sr-RS/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sr-RS/opds-Fedora_Core.xml | 2 +-
public_html/sr-RS/opds-Fedora_Documentation.xml | 2 +-
.../sr-RS/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sr-RS/opds-Fedora_Security_Team.xml | 2 +-
public_html/sr-RS/opds.xml | 16 +-
public_html/sr-RS/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/sv-SE/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/sv-SE/opds-Fedora_Core.xml | 2 +-
public_html/sv-SE/opds-Fedora_Documentation.xml | 2 +-
.../sv-SE/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/sv-SE/opds-Fedora_Security_Team.xml | 2 +-
public_html/sv-SE/opds.xml | 16 +-
public_html/sv-SE/toc.html | 12 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/ta-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/ta-IN/opds-Fedora_Core.xml | 2 +-
public_html/ta-IN/opds-Fedora_Documentation.xml | 2 +-
.../ta-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/ta-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/ta-IN/opds.xml | 16 +-
public_html/ta-IN/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/te-IN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/te-IN/opds-Fedora_Core.xml | 2 +-
public_html/te-IN/opds-Fedora_Documentation.xml | 2 +-
.../te-IN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/te-IN/opds-Fedora_Security_Team.xml | 2 +-
public_html/te-IN/opds.xml | 16 +-
public_html/te-IN/toc.html | 14 +-
public_html/toc.html | 44 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/uk-UA/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/uk-UA/opds-Fedora_Core.xml | 2 +-
public_html/uk-UA/opds-Fedora_Documentation.xml | 2 +-
.../uk-UA/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/uk-UA/opds-Fedora_Security_Team.xml | 2 +-
public_html/uk-UA/opds.xml | 16 +-
public_html/uk-UA/toc.html | 10 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/zh-CN/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/zh-CN/opds-Fedora_Core.xml | 2 +-
public_html/zh-CN/opds-Fedora_Documentation.xml | 2 +-
.../zh-CN/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/zh-CN/opds-Fedora_Security_Team.xml | 2 +-
public_html/zh-CN/opds.xml | 16 +-
public_html/zh-CN/toc.html | 14 +-
.../opds-Community_Services_Infrastructure.xml | 2 +-
public_html/zh-TW/opds-Fedora.xml | 4 +-
.../opds-Fedora_Contributor_Documentation.xml | 2 +-
public_html/zh-TW/opds-Fedora_Core.xml | 2 +-
public_html/zh-TW/opds-Fedora_Documentation.xml | 2 +-
.../zh-TW/opds-Fedora_Draft_Documentation.xml | 2 +-
public_html/zh-TW/opds-Fedora_Security_Team.xml | 2 +-
public_html/zh-TW/opds.xml | 16 +-
public_html/zh-TW/toc.html | 14 +-
648 files changed, 8563 insertions(+), 4124 deletions(-)
---
diff --git a/fedoradocs.db b/fedoradocs.db
index e0a4478..01f6c02 100755
Binary files a/fedoradocs.db and b/fedoradocs.db differ
diff --git a/public_html/Sitemap b/public_html/Sitemap
index 2b73f57..b542539 100644
--- a/public_html/Sitemap
+++ b/public_html/Sitemap
@@ -409,7 +409,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/ca-ES/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-ca-ES.pdf</loc>
+ <loc>http://docs.fedoraproject.org/ca-ES/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-ca-ES.pdf</loc>
<lastmod>2011-09-10</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -691,7 +691,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/cs-CZ/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-cs-CZ.pdf</loc>
+ <loc>http://docs.fedoraproject.org/cs-CZ/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-cs-CZ.pdf</loc>
<lastmod>2011-09-10</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -997,7 +997,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/de-DE/Fedora/18/pdf/Burning_ISO_images_to_disc/Fedora-17-Burning_ISO_images_to_disc-de-DE.pdf</loc>
+ <loc>http://docs.fedoraproject.org/de-DE/Fedora/18/pdf/Burning_ISO_images_to_disc/Fedora-18-Burning_ISO_images_to_disc-de-DE.pdf</loc>
<lastmod>2013-04-12</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -2048,25 +2048,25 @@
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora/21/epub/System_Administrators_Guide/Fedora-21-System_Administrators_Guide-en-US.epub</loc>
- <lastmod>2014-12-10</lastmod>
+ <lastmod>2015-03-06</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora/21/html/System_Administrators_Guide/index.html</loc>
- <lastmod>2014-12-10</lastmod>
+ <lastmod>2015-03-06</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora/21/html-single/System_Administrators_Guide/index.html</loc>
- <lastmod>2014-12-10</lastmod>
+ <lastmod>2015-03-06</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
<url>
<loc>http://docs.fedoraproject.org/en-US/Fedora/21/pdf/System_Administrators_Guide/Fedora-21-System_Administrators_Guide-en-US.pdf</loc>
- <lastmod>2014-12-10</lastmod>
+ <lastmod>2015-03-06</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
</url>
@@ -2635,7 +2635,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/en-US/Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf</loc>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf</loc>
<lastmod>2013-04-18</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -2827,7 +2827,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/en-US/Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf</loc>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf</loc>
<lastmod>2012-05-29</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -2941,7 +2941,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/en-US/Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf</loc>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf</loc>
<lastmod>2012-05-29</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -3367,7 +3367,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/en-US/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf</loc>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf</loc>
<lastmod>2011-09-10</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -5095,7 +5095,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf</loc>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf</loc>
<lastmod>2014-07-14</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -5167,7 +5167,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/pdf/Users_Guide/Publican-1.6-Users_Guide-en-US.pdf</loc>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/pdf/Users_Guide/Fedora_Contributor_Documentation-1-Users_Guide-en-US.pdf</loc>
<lastmod>2010-07-07</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -5809,7 +5809,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf</loc>
+ <loc>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf</loc>
<lastmod>2013-05-28</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -6487,7 +6487,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/es-ES/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-es-ES.pdf</loc>
+ <loc>http://docs.fedoraproject.org/es-ES/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-es-ES.pdf</loc>
<lastmod>2010-05-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -9163,7 +9163,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/he-IL/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-he-IL.pdf</loc>
+ <loc>http://docs.fedoraproject.org/he-IL/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-he-IL.pdf</loc>
<lastmod>2011-09-10</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -11623,7 +11623,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/ja-JP/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-ja-JP.pdf</loc>
+ <loc>http://docs.fedoraproject.org/ja-JP/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-ja-JP.pdf</loc>
<lastmod>2011-09-10</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -13123,7 +13123,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/nl-NL/Fedora/18/pdf/Virtualization_Getting_Started_Guide/Fedora-18-Virtualization_Getting_Started_Guide-nl-NL.pdf</loc>
+ <loc>http://docs.fedoraproject.org/nl-NL/Fedora/18/pdf/Virtualization_Getting_Started_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Getting_Started_Guide-nl-NL.pdf</loc>
<lastmod>2013-03-15</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -13291,7 +13291,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/nl-NL/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-nl-NL.pdf</loc>
+ <loc>http://docs.fedoraproject.org/nl-NL/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-nl-NL.pdf</loc>
<lastmod>2011-09-10</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -13537,7 +13537,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/nl-NL/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-nl-NL.pdf</loc>
+ <loc>http://docs.fedoraproject.org/nl-NL/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-nl-NL.pdf</loc>
<lastmod>2010-05-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -14209,7 +14209,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/nl-NL/Fedora/11/pdf/Security_Guide/fedora-11-Security_Guide-nl-NL.pdf</loc>
+ <loc>http://docs.fedoraproject.org/nl-NL/Fedora/11/pdf/Security_Guide/Fedora-11-Security_Guide-nl-NL.pdf</loc>
<lastmod>2010-06-13</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -16285,7 +16285,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/pt-PT/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-pt-PT.pdf</loc>
+ <loc>http://docs.fedoraproject.org/pt-PT/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-pt-PT.pdf</loc>
<lastmod>2010-05-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -17077,7 +17077,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/ru-RU/Fedora/18/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-ru-RU.pdf</loc>
+ <loc>http://docs.fedoraproject.org/ru-RU/Fedora/18/pdf/Fedora_Live_Images/Fedora-18-Fedora_Live_Images-ru-RU.pdf</loc>
<lastmod>2013-01-17</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -17173,7 +17173,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/ru-RU/Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-ru-RU.pdf</loc>
+ <loc>http://docs.fedoraproject.org/ru-RU/Fedora/17/pdf/Fedora_Live_Images/Fedora-18-Fedora_Live_Images-ru-RU.pdf</loc>
<lastmod>2012-06-04</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -20815,7 +20815,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/zh-CN/Fedora/18/pdf/Release_Notes/Fedora-17-Release_Notes-zh-CN.pdf</loc>
+ <loc>http://docs.fedoraproject.org/zh-CN/Fedora/18/pdf/Release_Notes/Fedora-18-Release_Notes-zh-CN.pdf</loc>
<lastmod>2013-01-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
@@ -21061,7 +21061,7 @@
<priority>0.8</priority>
</url>
<url>
- <loc>http://docs.fedoraproject.org/zh-CN/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-zh-CN.pdf</loc>
+ <loc>http://docs.fedoraproject.org/zh-CN/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-zh-CN.pdf</loc>
<lastmod>2010-05-22</lastmod>
<changefreq>monthly</changefreq>
<priority>0.8</priority>
diff --git a/public_html/as-IN/opds-Community_Services_Infrastructure.xml b/public_html/as-IN/opds-Community_Services_Infrastructure.xml
index 045beb0..5c9974a 100644
--- a/public_html/as-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/as-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:18:50</updated>
+ <updated>2015-03-06T05:43:14</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora.xml b/public_html/as-IN/opds-Fedora.xml
index 5f8df7b..be2249d 100644
--- a/public_html/as-IN/opds-Fedora.xml
+++ b/public_html/as-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:18:51</updated>
+ <updated>2015-03-06T05:43:17</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>as-IN</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
index 5ca7afe..d0da4a3 100644
--- a/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:18:51</updated>
+ <updated>2015-03-06T05:43:17</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 96b1c47..8bc753d 100644
--- a/public_html/as-IN/opds-Fedora_Core.xml
+++ b/public_html/as-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:18:52</updated>
+ <updated>2015-03-06T05:43:17</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Documentation.xml b/public_html/as-IN/opds-Fedora_Documentation.xml
index 2ef693f..78792fb 100644
--- a/public_html/as-IN/opds-Fedora_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:18:52</updated>
+ <updated>2015-03-06T05:43:17</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 f0bdaba..62174f0 100644
--- a/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/as-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:18:52</updated>
+ <updated>2015-03-06T05:43:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds-Fedora_Security_Team.xml b/public_html/as-IN/opds-Fedora_Security_Team.xml
index 9958ffd..7d7384f 100644
--- a/public_html/as-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/as-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/as-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:18:52</updated>
+ <updated>2015-03-06T05:43:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/as-IN/opds.xml b/public_html/as-IN/opds.xml
index 1e5da2b..d4003de 100644
--- a/public_html/as-IN/opds.xml
+++ b/public_html/as-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/as-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:18:52</updated>
+ <updated>2015-03-06T05:43:18</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/as-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:18:50</updated>
+ <updated>2015-03-06T05:43:14</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:18:51</updated>
+ <updated>2015-03-06T05:43:17</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:18:51</updated>
+ <updated>2015-03-06T05:43:17</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:18:52</updated>
+ <updated>2015-03-06T05:43:17</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:18:52</updated>
+ <updated>2015-03-06T05:43:17</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:18:52</updated>
+ <updated>2015-03-06T05:43:18</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/as-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:18:52</updated>
+ <updated>2015-03-06T05:43:18</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/as-IN/toc.html b/public_html/as-IN/toc.html
index c33818a..50d7f57 100644
--- a/public_html/as-IN/toc.html
+++ b/public_html/as-IN/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/bg-BG/opds-Community_Services_Infrastructure.xml b/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
index 0bbff92..771f49c 100644
--- a/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
+++ b/public_html/bg-BG/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:18:52</updated>
+ <updated>2015-03-06T05:43:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora.xml b/public_html/bg-BG/opds-Fedora.xml
index ceb797c..85853a8 100644
--- a/public_html/bg-BG/opds-Fedora.xml
+++ b/public_html/bg-BG/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:18:52</updated>
+ <updated>2015-03-06T05:43:18</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>bg-BG</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
index 55ebd92..da35c29 100644
--- a/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:18:52</updated>
+ <updated>2015-03-06T05:43:18</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 a86f01b..f3d4d59 100644
--- a/public_html/bg-BG/opds-Fedora_Core.xml
+++ b/public_html/bg-BG/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:18:53</updated>
+ <updated>2015-03-06T05:43:18</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Documentation.xml b/public_html/bg-BG/opds-Fedora_Documentation.xml
index 65b8f23..f285235 100644
--- a/public_html/bg-BG/opds-Fedora_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:18:53</updated>
+ <updated>2015-03-06T05:43:19</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 81415f9..91f3586 100644
--- a/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bg-BG/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:18:53</updated>
+ <updated>2015-03-06T05:43:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds-Fedora_Security_Team.xml b/public_html/bg-BG/opds-Fedora_Security_Team.xml
index cf8d6ca..c5cf951 100644
--- a/public_html/bg-BG/opds-Fedora_Security_Team.xml
+++ b/public_html/bg-BG/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bg-BG/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:18:53</updated>
+ <updated>2015-03-06T05:43:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bg-BG/opds.xml b/public_html/bg-BG/opds.xml
index 283971d..2efe751 100644
--- a/public_html/bg-BG/opds.xml
+++ b/public_html/bg-BG/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bg-BG/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:18:53</updated>
+ <updated>2015-03-06T05:43:19</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/bg-BG/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:18:52</updated>
+ <updated>2015-03-06T05:43:18</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:18:52</updated>
+ <updated>2015-03-06T05:43:18</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:18:53</updated>
+ <updated>2015-03-06T05:43:18</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:18:53</updated>
+ <updated>2015-03-06T05:43:19</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:18:53</updated>
+ <updated>2015-03-06T05:43:19</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:18:53</updated>
+ <updated>2015-03-06T05:43:19</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/bg-BG/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:18:53</updated>
+ <updated>2015-03-06T05:43:19</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/bg-BG/toc.html b/public_html/bg-BG/toc.html
index 2de2a8c..cea6da8 100644
--- a/public_html/bg-BG/toc.html
+++ b/public_html/bg-BG/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -484,7 +484,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -528,7 +528,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Resource_Management_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.Resource_Management_Guide.types');">
@@ -715,7 +715,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1444,7 +1444,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1471,7 +1471,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>
@@ -1831,7 +1831,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/bn-IN/opds-Community_Services_Infrastructure.xml b/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
index b3058b7..5c33bfa 100644
--- a/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/bn-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:18:53</updated>
+ <updated>2015-03-06T05:43:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora.xml b/public_html/bn-IN/opds-Fedora.xml
index 86a6ee0..9a547f1 100644
--- a/public_html/bn-IN/opds-Fedora.xml
+++ b/public_html/bn-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:18:53</updated>
+ <updated>2015-03-06T05:43:19</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>bn-IN</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
index 551326b..c087a45 100644
--- a/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:19</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 45d43d8..25445e7 100644
--- a/public_html/bn-IN/opds-Fedora_Core.xml
+++ b/public_html/bn-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Documentation.xml b/public_html/bn-IN/opds-Fedora_Documentation.xml
index 5a8851f..e378794 100644
--- a/public_html/bn-IN/opds-Fedora_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:19</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 5325f9f..d5d566c 100644
--- a/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bn-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds-Fedora_Security_Team.xml b/public_html/bn-IN/opds-Fedora_Security_Team.xml
index 9f9470e..e9667f9 100644
--- a/public_html/bn-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/bn-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bn-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bn-IN/opds.xml b/public_html/bn-IN/opds.xml
index 473084a..d7d2dec 100644
--- a/public_html/bn-IN/opds.xml
+++ b/public_html/bn-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bn-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:19</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/bn-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:18:53</updated>
+ <updated>2015-03-06T05:43:19</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:19</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:19</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:19</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:19</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:19</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/bn-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:19</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/bn-IN/toc.html b/public_html/bn-IN/toc.html
index 64b9fc5..0051c30 100644
--- a/public_html/bn-IN/toc.html
+++ b/public_html/bn-IN/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/bs-BA/opds-Community_Services_Infrastructure.xml b/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
index 0ced0de..d380e4e 100644
--- a/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
+++ b/public_html/bs-BA/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:19</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora.xml b/public_html/bs-BA/opds-Fedora.xml
index 5e17103..cb43509 100644
--- a/public_html/bs-BA/opds-Fedora.xml
+++ b/public_html/bs-BA/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:20</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>bs-BA</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
index e0027e6..f6d35b2 100644
--- a/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:20</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 4c6ae25..671b2a9 100644
--- a/public_html/bs-BA/opds-Fedora_Core.xml
+++ b/public_html/bs-BA/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Documentation.xml b/public_html/bs-BA/opds-Fedora_Documentation.xml
index 7a5bf6f..40910a2 100644
--- a/public_html/bs-BA/opds-Fedora_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:20</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 e2037a3..173fe5a 100644
--- a/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/bs-BA/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds-Fedora_Security_Team.xml b/public_html/bs-BA/opds-Fedora_Security_Team.xml
index f80345b..4de74e6 100644
--- a/public_html/bs-BA/opds-Fedora_Security_Team.xml
+++ b/public_html/bs-BA/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/bs-BA/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/bs-BA/opds.xml b/public_html/bs-BA/opds.xml
index 34a0e8b..524456e 100644
--- a/public_html/bs-BA/opds.xml
+++ b/public_html/bs-BA/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/bs-BA/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:20</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/bs-BA/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:19</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:20</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:20</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:20</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:20</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:20</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/bs-BA/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:20</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/bs-BA/toc.html b/public_html/bs-BA/toc.html
index 75c5b18..f5244dc 100644
--- a/public_html/bs-BA/toc.html
+++ b/public_html/bs-BA/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ca-ES/opds-Community_Services_Infrastructure.xml b/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
index f851a77..67290fa 100644
--- a/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ca-ES/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:20</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora.xml b/public_html/ca-ES/opds-Fedora.xml
index 5d726ec..a5eafe8 100644
--- a/public_html/ca-ES/opds-Fedora.xml
+++ b/public_html/ca-ES/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>ca-ES</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
index ac56918..e1e0a5c 100644
--- a/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:21</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 f9231d9..045267a 100644
--- a/public_html/ca-ES/opds-Fedora_Core.xml
+++ b/public_html/ca-ES/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Documentation.xml b/public_html/ca-ES/opds-Fedora_Documentation.xml
index 12c8f01..beffc9d 100644
--- a/public_html/ca-ES/opds-Fedora_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:21</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 65d03d9..2737e3f 100644
--- a/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ca-ES/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds-Fedora_Security_Team.xml b/public_html/ca-ES/opds-Fedora_Security_Team.xml
index 12b2613..b708056 100644
--- a/public_html/ca-ES/opds-Fedora_Security_Team.xml
+++ b/public_html/ca-ES/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ca-ES/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ca-ES/opds.xml b/public_html/ca-ES/opds.xml
index e422f92..e418197 100644
--- a/public_html/ca-ES/opds.xml
+++ b/public_html/ca-ES/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ca-ES/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:21</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ca-ES/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:20</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:21</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:21</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:21</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:21</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:21</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ca-ES/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:21</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ca-ES/toc.html b/public_html/ca-ES/toc.html
index 6b8cbf9..d0acc5b 100644
--- a/public_html/ca-ES/toc.html
+++ b/public_html/ca-ES/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -697,7 +697,7 @@
<a class="type" href="./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-ca-ES.epub" >epub</a>
<a class="type" href="./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-ca-ES.pdf" onclick="window.top.location='./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-ca-ES.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-ca-ES.pdf" onclick="window.top.location='./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-ca-ES.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml b/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
index 22d043d..f7b90cf 100644
--- a/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
+++ b/public_html/cs-CZ/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:21</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora.xml b/public_html/cs-CZ/opds-Fedora.xml
index 93777db..a155328 100644
--- a/public_html/cs-CZ/opds-Fedora.xml
+++ b/public_html/cs-CZ/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>cs-CZ</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
index ad80ae5..45a2adc 100644
--- a/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:22</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 f845a79..5c92fcc 100644
--- a/public_html/cs-CZ/opds-Fedora_Core.xml
+++ b/public_html/cs-CZ/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Documentation.xml b/public_html/cs-CZ/opds-Fedora_Documentation.xml
index f55f7c8..4ab2847 100644
--- a/public_html/cs-CZ/opds-Fedora_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:22</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 5ed7080..0efecdd 100644
--- a/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/cs-CZ/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds-Fedora_Security_Team.xml b/public_html/cs-CZ/opds-Fedora_Security_Team.xml
index aee59c6..788834e 100644
--- a/public_html/cs-CZ/opds-Fedora_Security_Team.xml
+++ b/public_html/cs-CZ/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/cs-CZ/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/cs-CZ/opds.xml b/public_html/cs-CZ/opds.xml
index 17e084c..ffe0d05 100644
--- a/public_html/cs-CZ/opds.xml
+++ b/public_html/cs-CZ/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/cs-CZ/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:18:57</updated>
+ <updated>2015-03-06T05:43:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/cs-CZ/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:21</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:22</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:22</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:22</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:22</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:22</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/cs-CZ/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:22</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/cs-CZ/toc.html b/public_html/cs-CZ/toc.html
index 15a868c..9c2715d 100644
--- a/public_html/cs-CZ/toc.html
+++ b/public_html/cs-CZ/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -697,7 +697,7 @@
<a class="type" href="./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-cs-CZ.epub" >epub</a>
<a class="type" href="./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-cs-CZ.pdf" onclick="window.top.location='./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-cs-CZ.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-cs-CZ.pdf" onclick="window.top.location='./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-cs-CZ.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/da-DK/opds-Community_Services_Infrastructure.xml b/public_html/da-DK/opds-Community_Services_Infrastructure.xml
index 7aeb870..a32b35c 100644
--- a/public_html/da-DK/opds-Community_Services_Infrastructure.xml
+++ b/public_html/da-DK/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:18:57</updated>
+ <updated>2015-03-06T05:43:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora.xml b/public_html/da-DK/opds-Fedora.xml
index 59576f0..90d8a07 100644
--- a/public_html/da-DK/opds-Fedora.xml
+++ b/public_html/da-DK/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:18:57</updated>
+ <updated>2015-03-06T05:43:22</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>da-DK</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
index 3f37f4f..360a4fe 100644
--- a/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:18:57</updated>
+ <updated>2015-03-06T05:43:22</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 83e7855..5008c63 100644
--- a/public_html/da-DK/opds-Fedora_Core.xml
+++ b/public_html/da-DK/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:18:57</updated>
+ <updated>2015-03-06T05:43:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Documentation.xml b/public_html/da-DK/opds-Fedora_Documentation.xml
index e717345..da22918 100644
--- a/public_html/da-DK/opds-Fedora_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:18:57</updated>
+ <updated>2015-03-06T05:43:22</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 fa57505..a8ce2fb 100644
--- a/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/da-DK/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:18:58</updated>
+ <updated>2015-03-06T05:43:22</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds-Fedora_Security_Team.xml b/public_html/da-DK/opds-Fedora_Security_Team.xml
index 9606817..2c61b09 100644
--- a/public_html/da-DK/opds-Fedora_Security_Team.xml
+++ b/public_html/da-DK/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/da-DK/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:18:58</updated>
+ <updated>2015-03-06T05:43:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/da-DK/opds.xml b/public_html/da-DK/opds.xml
index 2fde5a3..2ccfce8 100644
--- a/public_html/da-DK/opds.xml
+++ b/public_html/da-DK/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/da-DK/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:18:58</updated>
+ <updated>2015-03-06T05:43:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/da-DK/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:18:57</updated>
+ <updated>2015-03-06T05:43:22</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:18:57</updated>
+ <updated>2015-03-06T05:43:22</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:18:57</updated>
+ <updated>2015-03-06T05:43:22</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:18:57</updated>
+ <updated>2015-03-06T05:43:22</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:18:57</updated>
+ <updated>2015-03-06T05:43:22</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:18:58</updated>
+ <updated>2015-03-06T05:43:22</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/da-DK/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:18:58</updated>
+ <updated>2015-03-06T05:43:23</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/da-DK/toc.html b/public_html/da-DK/toc.html
index 031732c..4eccb0a 100644
--- a/public_html/da-DK/toc.html
+++ b/public_html/da-DK/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/de-DE/opds-Community_Services_Infrastructure.xml b/public_html/de-DE/opds-Community_Services_Infrastructure.xml
index 5dbdb26..c021f65 100644
--- a/public_html/de-DE/opds-Community_Services_Infrastructure.xml
+++ b/public_html/de-DE/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:18:58</updated>
+ <updated>2015-03-06T05:43:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora.xml b/public_html/de-DE/opds-Fedora.xml
index a32d8b9..8d1b7ac 100644
--- a/public_html/de-DE/opds-Fedora.xml
+++ b/public_html/de-DE/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:18:58</updated>
+ <updated>2015-03-06T05:43:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>de-DE</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
index 24a2583..ec5e09d 100644
--- a/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:18:58</updated>
+ <updated>2015-03-06T05:43:23</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 5eb1fbc..29ca1e3 100644
--- a/public_html/de-DE/opds-Fedora_Core.xml
+++ b/public_html/de-DE/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:18:59</updated>
+ <updated>2015-03-06T05:43:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Documentation.xml b/public_html/de-DE/opds-Fedora_Documentation.xml
index ddd6aa8..3425cbd 100644
--- a/public_html/de-DE/opds-Fedora_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:18:59</updated>
+ <updated>2015-03-06T05:43:23</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 17a54a3..807e577 100644
--- a/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/de-DE/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:18:59</updated>
+ <updated>2015-03-06T05:43:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds-Fedora_Security_Team.xml b/public_html/de-DE/opds-Fedora_Security_Team.xml
index 9aca6cf..65c0922 100644
--- a/public_html/de-DE/opds-Fedora_Security_Team.xml
+++ b/public_html/de-DE/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/de-DE/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:18:59</updated>
+ <updated>2015-03-06T05:43:23</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/de-DE/opds.xml b/public_html/de-DE/opds.xml
index 2891bcb..8d333cf 100644
--- a/public_html/de-DE/opds.xml
+++ b/public_html/de-DE/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/de-DE/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:18:59</updated>
+ <updated>2015-03-06T05:43:23</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/de-DE/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:18:58</updated>
+ <updated>2015-03-06T05:43:23</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:18:58</updated>
+ <updated>2015-03-06T05:43:23</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:18:58</updated>
+ <updated>2015-03-06T05:43:23</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:18:59</updated>
+ <updated>2015-03-06T05:43:23</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:18:59</updated>
+ <updated>2015-03-06T05:43:23</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:18:59</updated>
+ <updated>2015-03-06T05:43:23</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/de-DE/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:18:59</updated>
+ <updated>2015-03-06T05:43:23</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/de-DE/toc.html b/public_html/de-DE/toc.html
index 2886970..9f35ad7 100644
--- a/public_html/de-DE/toc.html
+++ b/public_html/de-DE/toc.html
@@ -319,7 +319,7 @@
<a class="type" href="./Fedora/18/epub/Burning_ISO_images_to_disc/Fedora-18-Burning_ISO_images_to_disc-de-DE.epub" >epub</a>
<a class="type" href="./Fedora/18/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='./Fedora/18/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="./Fedora/18/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='./Fedora/18/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/18/pdf/Burning_ISO_images_to_disc/Fedora-17-Burning_ISO_images_to_disc-de-DE.pdf" onclick="window.top.location='./Fedora/18/pdf/Burning_ISO_images_to_disc/Fedora-17-Burning_ISO_images_to_disc-de-DE.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/18/pdf/Burning_ISO_images_to_disc/Fedora-18-Burning_ISO_images_to_disc-de-DE.pdf" onclick="window.top.location='./Fedora/18/pdf/Burning_ISO_images_to_disc/Fedora-18-Burning_ISO_images_to_disc-de-DE.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18' class="version collapsed untranslated" onclick="toggle(event, 'Fedora.18.untrans_books');">
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -1500,7 +1500,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1527,7 +1527,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>
@@ -1887,7 +1887,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/el-GR/opds-Community_Services_Infrastructure.xml b/public_html/el-GR/opds-Community_Services_Infrastructure.xml
index 96f2043..43c20f7 100644
--- a/public_html/el-GR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/el-GR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:18:59</updated>
+ <updated>2015-03-06T05:43:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora.xml b/public_html/el-GR/opds-Fedora.xml
index d3abcd0..8e084c8 100644
--- a/public_html/el-GR/opds-Fedora.xml
+++ b/public_html/el-GR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>el-GR</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
index df3fd26..986710b 100644
--- a/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</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 bef869f..b551653 100644
--- a/public_html/el-GR/opds-Fedora_Core.xml
+++ b/public_html/el-GR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Documentation.xml b/public_html/el-GR/opds-Fedora_Documentation.xml
index 8ba8a52..90e9239 100644
--- a/public_html/el-GR/opds-Fedora_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</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 14de263..70cfdb6 100644
--- a/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/el-GR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds-Fedora_Security_Team.xml b/public_html/el-GR/opds-Fedora_Security_Team.xml
index 382dd00..aa7c33c 100644
--- a/public_html/el-GR/opds-Fedora_Security_Team.xml
+++ b/public_html/el-GR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/el-GR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/el-GR/opds.xml b/public_html/el-GR/opds.xml
index 45b0496..5a362f8 100644
--- a/public_html/el-GR/opds.xml
+++ b/public_html/el-GR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/el-GR/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/el-GR/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:18:59</updated>
+ <updated>2015-03-06T05:43:24</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/el-GR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/el-GR/toc.html b/public_html/el-GR/toc.html
index 52ea591..90ff65b 100644
--- a/public_html/el-GR/toc.html
+++ b/public_html/el-GR/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/en-US/Fedora/21/epub/System_Administrators_Guide/Fedora-21-System_Administrators_Guide-en-US.epub b/public_html/en-US/Fedora/21/epub/System_Administrators_Guide/Fedora-21-System_Administrators_Guide-en-US.epub
index a389db2..6820147 100644
Binary files a/public_html/en-US/Fedora/21/epub/System_Administrators_Guide/Fedora-21-System_Administrators_Guide-en-US.epub and b/public_html/en-US/Fedora/21/epub/System_Administrators_Guide/Fedora-21-System_Administrators_Guide-en-US.epub differ
diff --git a/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/managing_users.png b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/managing_users.png
new file mode 100644
index 0000000..0e020b3
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/managing_users.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/printconf-main.png b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/printconf-main.png
index dfd18c4..bce2701 100644
Binary files a/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/printconf-main.png and b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/printconf-main.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-filter-enable.png b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-filter-enable.png
new file mode 100644
index 0000000..e0e4051
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-filter-enable.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-filter-sample.png b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-filter-sample.png
new file mode 100644
index 0000000..66ce188
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-filter-sample.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-filters.png b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-filters.png
new file mode 100644
index 0000000..40dd5f8
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-filters.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-logviewer-add.png b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-logviewer-add.png
new file mode 100644
index 0000000..f2cf04d
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-logviewer-add.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-logviewer-monitoring.png b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-logviewer-monitoring.png
new file mode 100644
index 0000000..5f66789
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-logviewer-monitoring.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-logviewer.png b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-logviewer.png
new file mode 100644
index 0000000..365d52c
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/redhat-logviewer.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/rsyslog_message_flow.png b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/rsyslog_message_flow.png
new file mode 100644
index 0000000..7503f4a
Binary files /dev/null and b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/images/rsyslog_message_flow.png differ
diff --git a/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/index.html b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/index.html
index c7a4fd5..4fe22e4 100644
--- a/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/index.html
+++ b/public_html/en-US/Fedora/21/html-single/System_Administrators_Guide/index.html
@@ -6,11 +6,11 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><div xml:lang="en-US" class="book" id="idm225355386880" 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">21</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="idm225355386880" class="title">System Administrator's
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 21</h2></div><p class="edition">Edition 1.0</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+ </script></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><div xml:lang="en-US" class="book" id="idm261720985968" 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">21</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="idm261720985968" class="title">System Administrator's
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 21</h2></div><p class="edition">Edition 1.0</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
<span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> </object></span>
- </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="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</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:jhradilek at redhat.com">jhradilek at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Douglas</span> <span class="surname">Silas</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:silas at redhat.com">silas at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Martin</span> <span class="surname">Prpič</span></h3><d
iv class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:mprpic at redhat.com">mprpic at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:swadeley at redhat.com">swadeley at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Eliška</span> <span class="surname">Slobodová</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:eslobodo at redhat.com">eslobodo at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname
">Tomáš</span> <span class="surname">Čapek</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:tcapek at redhat.com">tcapek at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Petr</span> <span class="surname">Kovář</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:pkovar at redhat.com">pkovar at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Miroslav</span> <span class="surname">Svoboda</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:msvoboda at redhat.com">msvoboda at 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</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</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</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</span> <span class="orgdiv">Engineering Content Services</span></div></div></div></div><hr /><d
iv font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="idm225464677536" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
- Copyright <span class="trademark"></span>© 2014 Red Hat, Inc. and others.
+ </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</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:jhradilek at redhat.com">jhradilek at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Douglas</span> <span class="surname">Silas</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:silas at redhat.com">silas at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Martin</span> <span class="surname">Prpič</span></h3><d
iv class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:mprpic at redhat.com">mprpic at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:swadeley at redhat.com">swadeley at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Eliška</span> <span class="surname">Slobodová</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:eslobodo at redhat.com">eslobodo at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname
">Tomáš</span> <span class="surname">Čapek</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:tcapek at redhat.com">tcapek at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Petr</span> <span class="surname">Kovář</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:pkovar at redhat.com">pkovar at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Miroslav</span> <span class="surname">Svoboda</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:msvoboda at redhat.com">msvoboda at 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</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</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</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</span> <span class="orgdiv">Engineering Content Services</span></div></div></div></div><hr /><d
iv font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="idm261717223040" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2015 Red Hat, Inc. and others.
</div><div class="para">
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
</div><div class="para">
@@ -31,7 +31,7 @@
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">System Administrator's Guide</em> documents relevant information regarding the deployment, configuration, and administration of Fedora 21. It is oriented towards system administrators with a basic understanding of the system.
- </div></div></div></div><hr /></div><div class="toc"><dl class="toc"><dt><span class="preface"><a href="#idm225449337456">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="#idm225451968192">3. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="#idm225473504768">3.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="#idm225425141184">3.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="#idm225457571360">3.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="#idm225449959504">4. We Need 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-Ba
sic_System_Configuration">I. Basic System Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-Opening_GUI_Applications">1. Opening Graphical Applications</a></span></dt><dd><dl><dt><span class="section"><a href="#gui-from_cli">1.1. Opening graphical applications from the command line</a></span></dt><dt><span class="section"><a href="#gui-alt_f2">1.2. Launching Applications with <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> </a></span></dt><dt><span class="section"><a href="#gui-from_menu">1.3. Launching applications from the Desktop Menu</a></span></dt><dd><dl><dt><span class="section"><a href="#gui-from_menu-gnome">1.3.1. Using GNOME menus</a></span></dt><dt><span class="section"><a href="#gui-from_menu-kde">1.3.2. Using KDE menus </a></span></dt><dt><span class="section"><a href="#idm225459881376">1.3.3. Using menus in LXDE, MATE, and XFCE</a></span></dt></dl></dd></dl></dd><dt><span class="chapte
r"><a href="#ch-System_Locale_and_Keyboard_Configuration">2. System Locale and Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Setting_the_System_Locale">2.1. Setting the System Locale</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Displaying_the_Current_Status">2.1.1. Displaying the Current Status</a></span></dt><dt><span class="section"><a href="#s2-Listing_Available_Locales">2.1.2. Listing Available Locales</a></span></dt><dt><span class="section"><a href="#s2-Setting_the_Locale">2.1.3. Setting the Locale</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-Changing_the_Keyboard_Layout">2.2. Changing the Keyboard Layout</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Displaying_the_Current_Settings">2.2.1. Displaying the Current Settings</a></span></dt><dt><span class="section"><a href="#s2-Listing_Available_Keymaps">2.2.2. Listing Available Keymaps</a></span></dt><dt><span class="section"><a hre
f="#s2-Setting_the_Keymap">2.2.3. Setting the Keymap</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Keyboard_Configuration-Resources">2.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_the_Date_and_Time">3. Configuring the Date and Time</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl">3.1. Using the timedatectl Command</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Display">3.1.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Time">3.1.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Date">3.1.3. Changing the Current Date</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone
">3.1.4. Changing the Time Zone</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-NTP">3.1.5. Synchronizing the System Clock with a Remote Server</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date">3.2. Using the date Command</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date-Display">3.2.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date-Time">3.2.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date-Date">3.2.3. Changing the Current Date</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-hwclock">3.3. Using the hwclock Command</a></span></dt><dd><dl><dt><span class="section"><a href="#sect2-displaying-time-hwclock">3.3.1. Displaying the Curre
nt Date and Time</a></span></dt><dt><span class="section"><a href="#sect3-changing-date-time-hwclock">3.3.2. Setting the Date and Time</a></span></dt><dt><span class="section"><a href="#sect4-synchronizing-date-time-hwclock">3.3.3. Synchronizing the Date and Time</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Date_and_Time-Resources">3.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Managing_Users_and_Groups">4. Managing Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-users-groups-introduction">4.1. Introduction to Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-groups-private-groups">4.1.1. User Private Groups</a></span></dt><dt><span class="section"><a href="#s2-users-groups-shadow-utilities">4.1.2. Shadow Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-configui">4.2. Using the User Manager Tool</a></span></dt><dd><d
l><dt><span class="section"><a href="#s2-redhat-config-users-list">4.2.1. Viewing Users and Groups</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-tools">4.3. Using Command Line Tools</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-tools-users-add">4.3.1. Adding a New User</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-add">4.3.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="#s2-users-tools-password-aging">4.3.3. Enabling Password Aging</a></span></dt><dt><span class="section"><a href="#s2-users-tools-users-logout">4.3.4. Enabling Automatic Logouts</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-directories">4.3.5. Creating Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-groups-additional-resources">4.4. Additional Resources</a></span></dt></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-yum">5. Yum</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_For_and_Updating_Packages">5.1. Checking For and Updating Packages</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_For_Updates">5.1.1. Checking For Updates</a></span></dt><dt><span class="section"><a href="#sec-Updating_Packages">5.1.2. Updating Packages</a></span></dt><dt><span class="section"><a href="#sec-Preserving_Configuration_File_Changes">5.1.3. Preserving Configuration File Changes</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Packages_and_Package_Groups">5.2. Packages and Package Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Searching_Packages">5.2.1. Searching Packages</a></span></dt><dt><span class="section"><a href="#sec-Listing_Packages">5.2.2. Listing Packages</a></span></dt><dt><span class="section"><a href="#sec-Displaying_Package
_Information">5.2.3. Displaying Package Information</a></span></dt><dt><span class="section"><a href="#sec-Installing">5.2.4. Installing Packages</a></span></dt><dt><span class="section"><a href="#sec-Removing">5.2.5. Removing Packages</a></span></dt><dt><span class="section"><a href="#sec-Yum-Transaction_History">5.2.6. Working with Transaction History</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Yum_and_Yum_Repositories">5.3. Configuring Yum and Yum Repositories</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_main_Options">5.3.1. Setting [main] Options</a></span></dt><dt><span class="section"><a href="#sec-Setting_repository_Options">5.3.2. Setting [repository] Options</a></span></dt><dt><span class="section"><a href="#sec-Using_Yum_Variables">5.3.3. Using Yum Variables</a></span></dt><dt><span class="section"><a href="#sec-Viewing_the_Current_Configuration">5.3.4. Viewing the Current Configuration</a></span></dt><dt><
span class="section"><a href="#sec-Managing_Yum_Repositories">5.3.5. Adding, Enabling, and Disabling a Yum Repository</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Yum_Repository">5.3.6. Creating a Yum Repository</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Yum_Plugins">5.4. Yum Plug-ins</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">5.4.1. Enabling, Configuring, and Disabling Yum Plug-ins</a></span></dt><dt><span class="section"><a href="#sec-Installing_More_Yum_Plugins">5.4.2. Installing Additional Yum Plug-ins</a></span></dt><dt><span class="section"><a href="#sec-Plugin_Descriptions">5.4.3. Plug-in Descriptions</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Additional_Resources">5.5. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#part-Infrastructure_Services">III. Infrastructure Services</a></span></dt><dd><dl
><dt><span class="chapter"><a href="#ch-Services_and_Daemons">6. Services and Daemons</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-services-configuring">6.1. Configuring Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-configuration-enabling">6.1.1. Enabling the Service</a></span></dt><dt><span class="section"><a href="#s3-services-configuration-disabling">6.1.2. Disabling the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-running">6.2. Running Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-running-checking">6.2.1. Checking the Service Status</a></span></dt><dt><span class="section"><a href="#s3-services-running-running">6.2.2. Running the Service</a></span></dt><dt><span class="section"><a href="#s3-services-running-stopping">6.2.3. Stopping the Service</a></span></dt><dt><span class="section"><a href="#s3-services-running-restarting">6.2.4. Restarting the Serv
ice</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-additional-resources">6.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-additional-resources-installed">6.3.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-services-additional-resources-books">6.3.2. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-OpenSSH">7. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ssh-protocol">7.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-why">7.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a href="#s2-ssh-features">7.1.2. Main Features</a></span></dt><dt><span class="section"><a href="#s2-ssh-versions">7.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="#s2-ssh-conn">7.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="sect
ion"><a href="#s1-ssh-configuration">7.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-configuration-configs">7.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-sshd">7.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-requiring">7.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-keypairs">7.2.4. Using Key-based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-clients">7.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-clients-ssh">7.3.1. Using the ssh Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-scp">7.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-sftp">7.3.3. Using the <code class="command">s
ftp</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-beyondshell">7.4. More Than a Secure Shell</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-beyondshell-x11">7.4.1. X11 Forwarding</a></span></dt><dt><span class="section"><a href="#s2-ssh-beyondshell-tcpip">7.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-openssh-additional-resources">7.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-TigerVNC">8. TigerVNC</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-vnc-server">8.1. VNC Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-vnc-installation">8.1.1. Installing VNC Server</a></span></dt><dt><span class="section"><a href="#s3-configuring-vnc-server">8.1.2. Configuring VNC Server</a></span></dt><dt><span class="section"><a href="#s4-starting-vncserver">8.1.3. Starting VNC Server</a></span></dt><dt><span class="section"
><a href="#terminating-vnc-session">8.1.4. Terminating a VNC session</a></span></dt></dl></dd><dt><span class="section"><a href="#s5-vnc-viewer">8.2. VNC Viewer</a></span></dt><dd><dl><dt><span class="section"><a href="#installing-vncviewer">8.2.1. Installing VNC Viewer</a></span></dt><dt><span class="section"><a href="#s6-connecting-vnc-viewer">8.2.2. Connecting to VNC Server</a></span></dt><dt><span class="section"><a href="#s1-using_ssh">8.2.3. Connecting to VNC Server using SSH</a></span></dt></dl></dd><dt><span class="section"><a href="#s9-additional-sources">8.3. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#part-Servers">IV. Servers</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-Web_Servers">9. Web Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-The_Apache_HTTP_Server">9.1. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-changes">9.1.1. Notable C
hanges</a></span></dt><dt><span class="section"><a href="#s2-apache-version2-migrating">9.1.2. Updating the Configuration</a></span></dt><dt><span class="section"><a href="#s2-apache-running">9.1.3. Running the httpd Service</a></span></dt><dt><span class="section"><a href="#s2-apache-editing">9.1.4. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="#s2-apache-dso">9.1.5. Working with Modules</a></span></dt><dt><span class="section"><a href="#s2-apache-virtualhosts">9.1.6. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="#s2-apache-mod_ssl">9.1.7. Setting Up an SSL Server</a></span></dt><dt><span class="section"><a href="#s2-apache-resources">9.1.8. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Mail_Servers">10. Mail Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-email-protocols">10.1. Email Protocols</a></span></dt><dd><dl><dt><span class="sectio
n"><a href="#s2-email-protocols-send">10.1.1. Mail Transport Protocols</a></span></dt><dt><span class="section"><a href="#s2-email-protocols-client">10.1.2. Mail Access Protocols</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-types">10.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-types-mta">10.2.1. Mail Transport Agent</a></span></dt><dt><span class="section"><a href="#s2-email-types-mda">10.2.2. Mail Delivery Agent</a></span></dt><dt><span class="section"><a href="#s2-email-types-mua">10.2.3. Mail User Agent</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mta">10.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-mta-postfix">10.3.1. Postfix</a></span></dt><dt><span class="section"><a href="#s2-email-mta-sendmail">10.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="#s2-email-mta-fetchmail">10.3.3. Fetchmail</a></span><
/dt><dt><span class="section"><a href="#s2-email-switchmail">10.3.4. Mail Transport Agent (MTA) Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mda">10.4. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-procmail-configuration">10.4.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="#s2-email-procmail-recipes">10.4.2. Procmail Recipes</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mua">10.5. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-security">10.5.1. Securing Communication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-additional-resources">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-installed-docs">10.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-email-useful-websites">10.6.2. Useful Websites</a></spa
n></dt><dt><span class="section"><a href="#s2-email-related-books">10.6.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Directory_Servers">11. Directory Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-OpenLDAP">11.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-introduction">11.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-installation">11.1.2. Installing the OpenLDAP Suite</a></span></dt><dt><span class="section"><a href="#s2-ldap-configuration">11.1.3. Configuring an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="#s2-ldap-running">11.1.4. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="#s2-ldap-pam">11.1.5. Configuring a System to Authenticate Using OpenLDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-resources">11.1.6. Additional Resources</a></span></dt></dl></dd></dl></dd><dt
><span class="chapter"><a href="#ch-File_and_Print_Servers">12. File and Print Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Samba">12.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="#samba-rgs-overview">12.1.1. Introduction to Samba</a></span></dt><dt><span class="section"><a href="#s2-samba-daemons">12.1.2. Samba Daemons and Related Services</a></span></dt><dt><span class="section"><a href="#s2-samba-connect-share">12.1.3. Connecting to a Samba Share</a></span></dt><dt><span class="section"><a href="#s2-samba-configuring">12.1.4. Configuring a Samba Server</a></span></dt><dt><span class="section"><a href="#s2-samba-startstop">12.1.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="#s2-samba-servers">12.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">12.1.7. Samba Security Modes</a></span></dt><dt><s
pan class="section"><a href="#s2-samba-account-info-dbs">12.1.8. Samba Account Information Databases</a></span></dt><dt><span class="section"><a href="#s2-samba-network-browsing">12.1.9. Samba Network Browsing</a></span></dt><dt><span class="section"><a href="#s2-samba-cups">12.1.10. Samba with CUPS Printing Support</a></span></dt><dt><span class="section"><a href="#s2-samba-programs">12.1.11. Samba Distribution Programs</a></span></dt><dt><span class="section"><a href="#s2-samba-resources">12.1.12. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-FTP">12.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-protocol">12.2.1. The File Transfer Protocol</a></span></dt><dt><span class="section"><a href="#s2-ftp-servers">12.2.2. FTP Servers</a></span></dt><dt><span class="section"><a href="#s3-ftp-vsftpd-conf">12.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href=
"#s2-ftp-vsftpd-start">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf">12.2.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-resources">12.2.6. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Printer_Configuration">12.3. Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Starting_Printer_Config">12.3.1. Starting the Printer Configuration Tool</a></span></dt><dt><span class="section"><a href="#sec-Setting_Printer">12.3.2. Starting Printer Setup</a></span></dt><dt><span class="section"><a href="#sec-Adding_Other_Printer">12.3.3. Adding a Local Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-jetdirect-printer">12.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="#s1-printing-ipp-pr
inter">12.3.5. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="#sec-printing-LPDLPR-printer">12.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-smb-printer">12.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="#s1-printing-select-model">12.3.8. Selecting the Printer Model and Finishing</a></span></dt><dt><span class="section"><a href="#s1-printing-test-page">12.3.9. Printing a Test Page</a></span></dt><dt><span class="section"><a href="#s1-printing-edit">12.3.10. Modifying Existing Printers</a></span></dt><dt><span class="section"><a href="#s1-printing-additional-resources">12.3.11. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_NTP_Using_the_chrony_Suite">13. Configuring NTP Using the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Introduction_to_the_chrony_Suite">13.1. Intro
duction to the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-differences_between_ntpd_and_chronyd">13.1.1. Differences Between ntpd and chronyd</a></span></dt><dt><span class="section"><a href="#sect-Choosing_between_NTP_daemon">13.1.2. Choosing Between NTP Daemons</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Understanding_chrony_and-its_configuration">13.2. Understanding chrony and Its Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Understanding_chronyd">13.2.1. Understanding chronyd</a></span></dt><dt><span class="section"><a href="#sect-Understanding_chronyc">13.2.2. Understanding chronyc</a></span></dt><dt><span class="section"><a href="#sect-Understanding_the_chrony_configuration_commands">13.2.3. Understanding the chrony Configuration Commands</a></span></dt><dt><span class="section"><a href="#sect-Security_with_chronyc">13.2.4. Security with chronyc</a></span></dt></dl></dd><dt><span cl
ass="section"><a href="#sect-Using_chrony">13.3. Using chrony</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Installing_chrony">13.3.1. Installing chrony</a></span></dt><dt><span class="section"><a href="#sect-Checking_the_Status_of_chronyd">13.3.2. Checking the Status of chronyd</a></span></dt><dt><span class="section"><a href="#sect-Starting_chronyd">13.3.3. Starting chronyd</a></span></dt><dt><span class="section"><a href="#sect-Stopping_chronyd">13.3.4. Stopping chronyd</a></span></dt><dt><span class="section"><a href="#sect-Checking_if_chrony_is_synchronized">13.3.5. Checking if chrony is Synchronized</a></span></dt><dt><span class="section"><a href="#sect-Manually_Adjusting-the-System_Clock">13.3.6. Manually Adjusting the System Clock</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Setting_up_chrony_for_different_environments">13.4. Setting Up chrony for Different Environments</a></span></dt><dd><dl><dt><span class="section"><a href="
#sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">13.4.1. Setting Up chrony for a System Which is Infrequently Connected</a></span></dt><dt><span class="section"><a href="#sect-Setting_up_chrony_for_a_system_in_an_isolated_network">13.4.2. Setting Up chrony for a System in an Isolated Network</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Using_chronyc">13.5. Using chronyc</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Using_chronyc_chronyc_to_control_chronyd">13.5.1. Using chronyc to Control chronyd</a></span></dt><dt><span class="section"><a href="#sect-Using_chronyc_for_remote_administration">13.5.2. Using chronyc for Remote Administration</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-additional_resources">13.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-chrony-docs-inst">13.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-c
hrony_Online_Documentation">13.6.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_NTP_Using_ntpd">14. Configuring NTP Using ntpd</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Introduction_to_NTP">14.1. Introduction to NTP</a></span></dt><dt><span class="section"><a href="#s1-NTP_Strata">14.2. NTP Strata</a></span></dt><dt><span class="section"><a href="#s1-Understanding_NTP">14.3. Understanding NTP</a></span></dt><dt><span class="section"><a href="#s1-Understanding_the_Drift_File">14.4. Understanding the Drift File</a></span></dt><dt><span class="section"><a href="#s1-UTC_timezones_and_DST">14.5. UTC, Timezones, and DST</a></span></dt><dt><span class="section"><a href="#s1-Authentication_Options_for_NTP">14.6. Authentication Options for NTP</a></span></dt><dt><span class="section"><a href="#s1-Managing_the_Time_on_Virtual_Machines">14.7. Managing the Time on Virtual Machines</a></span></dt><dt><span
class="section"><a href="#s1-Understanding_Leap_Seconds">14.8. Understanding Leap Seconds</a></span></dt><dt><span class="section"><a href="#s1-Understanding_the_ntpd_Configuration_File">14.9. Understanding the ntpd Configuration File</a></span></dt><dt><span class="section"><a href="#s1-Understanding_the_ntpd_Sysconfig_File">14.10. Understanding the ntpd Sysconfig File</a></span></dt><dt><span class="section"><a href="#s1-Disabling_chrony">14.11. Disabling chrony</a></span></dt><dt><span class="section"><a href="#s1-Checking_if_the_NTP_Daemon_is_Installed">14.12. Checking if the NTP Daemon is Installed</a></span></dt><dt><span class="section"><a href="#s1-Installing_the_NTP_Daemon_ntpd">14.13. Installing the NTP Daemon (ntpd)</a></span></dt><dt><span class="section"><a href="#s1-Checking_the_status_of_NTP">14.14. Checking the Status of NTP</a></span></dt><dt><span class="section"><a href="#s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets">14.15. Configure the Firewa
ll to Allow Incoming NTP Packets</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Change_the_firewall_settings">14.15.1. Change the Firewall Settings</a></span></dt><dt><span class="section"><a href="#s2-Open_Ports_in_the_firewall_for_ntp_packets">14.15.2. Open Ports in the Firewall for NTP Packets</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-Configure_ntpdate_Servers">14.16. Configure ntpdate Servers</a></span></dt><dt><span class="section"><a href="#s1-Configure_NTP">14.17. Configure NTP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Configure_Access_Control_to_an_NTP_service">14.17.1. Configure Access Control to an NTP Service</a></span></dt><dt><span class="section"><a href="#s2_Configure_Rate_Limiting_Access_to_an_NTP_Service">14.17.2. Configure Rate Limiting Access to an NTP Service</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Peer_Address">14.17.3. Adding a Peer Address</a></span></dt><dt><span class="se
ction"><a href="#s2_Adding_a_Server_Address">14.17.4. Adding a Server Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Broadcast_or_Mutlticast_Server_Address">14.17.5. Adding a Broadcast or Multicast Server Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Manycast_Client_Address">14.17.6. Adding a Manycast Client Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Broadcastclient_Address">14.17.7. Adding a Broadcast Client Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_manycastserver_Address">14.17.8. Adding a Manycast Server Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_multicastclient_Address">14.17.9. Adding a Multicast Client Address</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_burst_option">14.17.10. Configuring the Burst Option</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_iburst_Option">14.17.11. Configuring t
he iburst Option</a></span></dt><dt><span class="section"><a href="#s2_Configuring_Symmetric_Authentication_Using_a_Key">14.17.12. Configuring Symmetric Authentication Using a Key</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_Poll_Interval">14.17.13. Configuring the Poll Interval</a></span></dt><dt><span class="section"><a href="#s2_Configuring_Server_Preference">14.17.14. Configuring Server Preference</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_Time-To-Live_for_NTP_Packets">14.17.15. Configuring the Time-to-Live for NTP Packets</a></span></dt><dt><span class="section"><a href="#s2_Configuring_The_Version_of_NTP_to_use">14.17.16. Configuring the NTP Version to Use</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-Configuring_the_Hardware_Clock_update">14.18. Configuring the Hardware Clock Update</a></span></dt><dt><span class="section"><a href="#s1-Configuring_Clock_Sources">14.19. Configuring Clock Sources</a><
/span></dt><dt><span class="section"><a href="#s1-ntpd_additional-resources">14.20. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ntpd-docs-inst">14.20.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-ntpd_useful-websites">14.20.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_PTP_Using_ptp4l">15. Configuring PTP Using ptp4l</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Introduction_to_PTP">15.1. Introduction to PTP</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Understanding_PTP">15.1.1. Understanding PTP</a></span></dt><dt><span class="section"><a href="#sec-Advantages_of_PTP">15.1.2. Advantages of PTP</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_PTP">15.2. Using PTP</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_for_Driver_and_Hardware_Support">15.2.1. Checking for D
river and Hardware Support</a></span></dt><dt><span class="section"><a href="#sec-Installing_PTP">15.2.2. Installing PTP</a></span></dt><dt><span class="section"><a href="#sec-Starting_ptp4l">15.2.3. Starting ptp4l</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Specifying_a_Configuration_File">15.3. Specifying a Configuration File</a></span></dt><dt><span class="section"><a href="#sec-Using_the_PTP_Management_Client">15.4. Using the PTP Management Client</a></span></dt><dt><span class="section"><a href="#sec-Synchronizing_the_Clocks">15.5. Synchronizing the Clocks</a></span></dt><dt><span class="section"><a href="#sec-Verifying_Time_Synchronization">15.6. Verifying Time Synchronization</a></span></dt><dt><span class="section"><a href="#sec-Serving_PTP_Time_with_NTP">15.7. Serving PTP Time with NTP</a></span></dt><dt><span class="section"><a href="#sec-Serving_NTP_Time_with_PTP">15.8. Serving NTP Time with PTP</a></span></dt><dt><span class="section"><a href
="#sec-Improving_Accuracy">15.9. Improving Accuracy</a></span></dt><dt><span class="section"><a href="#sec-PTP_additional_resources">15.10. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-PTP-docs-inst">15.10.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-PTP_useful-websites">15.10.2. Useful Websites</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="#part-Monitoring_and_Automation">V. 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. Viewing System Processes</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-system-processes-ps">16.1.1. Using the ps Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-system-processes-top">16.1.2. Using the top Command</a></span
></dt><dt><span class="section"><a href="#s2-sysinfo-system-processes-system_monitor">16.1.3. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-memory-usage">16.2. Viewing Memory Usage</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-memory-usage-free">16.2.1. Using the free Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-memory-usage-system_monitor">16.2.2. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-cpu">16.3. Viewing CPU Usage</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-cpu-system_monitor">16.3.1. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-filesystems">16.4. Viewing Block Devices and File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-filesystems-lsblk">16.4.1. Using the lsblk Command</a></span></dt><dt><spa
n class="section"><a href="#s2-sysinfo-filesystems-blkid">16.4.2. Using the blkid Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-partx">16.4.3. Using the partx Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-findmnt">16.4.4. Using the findmnt Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-df">16.4.5. Using the df Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-du">16.4.6. Using the du Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-system_monitor">16.4.7. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-hardware">16.5. Viewing Hardware Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-hardware-lspci">16.5.1. Using the lspci Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lsusb">16.5.2. Using
the lsusb Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lspcmcia">16.5.3. Using the lspcmcia Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lscpu">16.5.4. Using the lscpu Command</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP">16.6. Monitoring Performance with Net-SNMP</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Installing">16.6.1. Installing Net-SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Running">16.6.2. Running the Net-SNMP Daemon</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Configuring">16.6.3. Configuring Net-SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Retrieving">16.6.4. Retrieving Performance Data over SNMP</a></span></dt><dt><span class="section"><a href="#se
ct-System_Monitoring_Tools-Net-SNMP-Extending">16.6.5. Extending Net-SNMP</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-additional-resources">16.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-installed-docs">16.7.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 Configurati
on</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 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="#sect-Cron-Installing">18.1.1. Installing Cron and Anacron</a></span></dt><dt><span class="section"><a href="#sect-Cron-Running">18.1.2. Running the Crond Service</a></span></dt><dt><span class="section"><a href="#s2-configuring-anacron-jobs">18.1.3. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="#s2-configuring-cron-jobs">18.1.4. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-cron-access">18.1.5. Controlling Access to Cron</a></span></dt><dt><span class="section"><a href="#s2-black-white-listing-of-cron-jobs">18.1.6. Black and 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="#sect-At_and_Batch_Installation"
>18.2.1. Installing At and Batch</a></span></dt><dt><span class="section"><a href="#sect-Atd-Running">18.2.2. Running the At Service</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-configuring">18.2.3. Configuring an At Job</a></span></dt><dt><span class="section"><a href="#s2-autotasks-batch-configuring">18.2.4. Configuring a Batch Job</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-viewing">18.2.5. Viewing Pending Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-commandline-options">18.2.6. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-controlling-access">18.2.7. Controlling Access to At and Batch</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-autotasks-additional-resources">18.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-OProfile">19. OProfile</a></span></dt><dd><dl><dt><span class="section">
<a href="#s1-oprofile-overview-tools">19.1. Overview of Tools</a></span></dt><dt><span class="section"><a href="#s1-oprofile-configuring">19.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-kernel">19.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="#s2-oprofile-events">19.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="#s2-oprofile-starting-separate">19.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-starting">19.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="#s1-oprofile-saving-data">19.4. Saving Data</a></span></dt><dt><span class="section"><a href="#s1-oprofile-analyzing-data">19.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-reading-opreport">19.5.1. Using <code class="command">opreport</code> </a></span></dt><dt
><span class="section"><a href="#s2-oprofile-reading-opreport-single">19.5.2. Using opreport on a Single Executable</a></span></dt><dt><span class="section"><a href="#s2-oprofile-module-output">19.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opannotate">19.5.4. Using <code class="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-dev-oprofile">19.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="#s1-oprofile-example-usage">19.7. Example Usage</a></span></dt><dt><span class="section"><a href="#s1-oprofile-java-support">19.8. OProfile Support for Java</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-java-profiling">19.8.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-gui">19.9. Graphical Interface</a></span></dt><dt><span c
lass="section"><a href="#s1-oprofile-and-systemtap">19.10. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="#s1-oprofile-additional-resources">19.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-installed-docs">19.11.1. Installed Docs</a></span></dt><dt><span class="section"><a href="#s2-oprofile-useful-websites">19.11.2. Useful Websites</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="#part-Kernel_Module_and_Driver_Configuration">VI. 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">2
0.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 2 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="#s1-kernel-modules-additional-resources">21.7. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#ch-RPM">A. RPM</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-rpm-design">A.1. RPM Design Goals</a></span></dt><dt><span class="section"><a href="#s1-rpm-using">A.2. Using RP
M</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="section"><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 Sig
nature 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="#app-Revision_History">B. Revision History</a></span></dt><dt><span class="index"><a href="#idm225402575664">Index</a></span></dt></dl></div><div xml:lang="en-US" class="preface" id="idm225449337456" lang="en-US"><div class="titlepage"><div><div><h1 id="idm225449337456" class="title">Preface</h1></div></div></div><div class="para">
+ </div></div></div></div><hr /></div><div class="toc"><dl class="toc"><dt><span class="preface"><a href="#idm261754805696">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="#idm261747249120">3. Document Conventions</a></span></dt><dd><dl><dt><span class="section"><a href="#idm261713030576">3.1. Typographic Conventions</a></span></dt><dt><span class="section"><a href="#idm261786304416">3.2. Pull-quote Conventions</a></span></dt><dt><span class="section"><a href="#idm261728877104">3.3. Notes and Warnings</a></span></dt></dl></dd><dt><span class="section"><a href="#idm261712903024">4. We Need 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-Ba
sic_System_Configuration">I. Basic System Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-Opening_GUI_Applications">1. Opening Graphical Applications</a></span></dt><dd><dl><dt><span class="section"><a href="#gui-from_cli">1.1. Opening graphical applications from the command line</a></span></dt><dt><span class="section"><a href="#gui-alt_f2">1.2. Launching Applications with <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> </a></span></dt><dt><span class="section"><a href="#gui-from_menu">1.3. Launching applications from the Desktop Menu</a></span></dt><dd><dl><dt><span class="section"><a href="#gui-from_menu-gnome">1.3.1. Using GNOME menus</a></span></dt><dt><span class="section"><a href="#gui-from_menu-kde">1.3.2. Using KDE menus </a></span></dt><dt><span class="section"><a href="#idm261653475360">1.3.3. Using menus in LXDE, MATE, and XFCE</a></span></dt></dl></dd></dl></dd><dt><span class="chapte
r"><a href="#ch-System_Locale_and_Keyboard_Configuration">2. System Locale and Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Setting_the_System_Locale">2.1. Setting the System Locale</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Displaying_the_Current_Status">2.1.1. Displaying the Current Status</a></span></dt><dt><span class="section"><a href="#s2-Listing_Available_Locales">2.1.2. Listing Available Locales</a></span></dt><dt><span class="section"><a href="#s2-Setting_the_Locale">2.1.3. Setting the Locale</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-Changing_the_Keyboard_Layout">2.2. Changing the Keyboard Layout</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Displaying_the_Current_Settings">2.2.1. Displaying the Current Settings</a></span></dt><dt><span class="section"><a href="#s2-Listing_Available_Keymaps">2.2.2. Listing Available Keymaps</a></span></dt><dt><span class="section"><a hre
f="#s2-Setting_the_Keymap">2.2.3. Setting the Keymap</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Keyboard_Configuration-Resources">2.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_the_Date_and_Time">3. Configuring the Date and Time</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl">3.1. Using the timedatectl Command</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Display">3.1.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Time">3.1.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Date">3.1.3. Changing the Current Date</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone
">3.1.4. Changing the Time Zone</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-NTP">3.1.5. Synchronizing the System Clock with a Remote Server</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date">3.2. Using the date Command</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date-Display">3.2.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date-Time">3.2.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date-Date">3.2.3. Changing the Current Date</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-hwclock">3.3. Using the hwclock Command</a></span></dt><dd><dl><dt><span class="section"><a href="#sect2-displaying-time-hwclock">3.3.1. Displaying the Curre
nt Date and Time</a></span></dt><dt><span class="section"><a href="#sect3-changing-date-time-hwclock">3.3.2. Setting the Date and Time</a></span></dt><dt><span class="section"><a href="#sect4-synchronizing-date-time-hwclock">3.3.3. Synchronizing the Date and Time</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Date_and_Time-Resources">3.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Managing_Users_and_Groups">4. Managing Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-users-groups-introduction">4.1. Introduction to Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-groups-private-groups">4.1.1. User Private Groups</a></span></dt><dt><span class="section"><a href="#s2-users-groups-shadow-utilities">4.1.2. Shadow Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-configui">4.2. Managing Users in a Graphical Environment</a></sp
an></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-users-list">4.2.1. Using the Users Settings Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-tools">4.3. Using Command Line Tools</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-tools-users-add">4.3.1. Adding a New User</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-add">4.3.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="#s2-users-tools-password-aging">4.3.3. Enabling Password Aging</a></span></dt><dt><span class="section"><a href="#s2-users-tools-users-logout">4.3.4. Enabling Automatic Logouts</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-directories">4.3.5. Creating Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Users_and_Groups-Resources">4.4. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#part-Package_Ma
nagement">II. Package Management</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-yum">5. Yum</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_For_and_Updating_Packages">5.1. Checking For and Updating Packages</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_For_Updates">5.1.1. Checking For Updates</a></span></dt><dt><span class="section"><a href="#sec-Updating_Packages">5.1.2. Updating Packages</a></span></dt><dt><span class="section"><a href="#sec-Preserving_Configuration_File_Changes">5.1.3. Preserving Configuration File Changes</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Packages_and_Package_Groups">5.2. Packages and Package Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Searching_Packages">5.2.1. Searching Packages</a></span></dt><dt><span class="section"><a href="#sec-Listing_Packages">5.2.2. Listing Packages</a></span></dt><dt><span class="section"><a href="#sec-Disp
laying_Package_Information">5.2.3. Displaying Package Information</a></span></dt><dt><span class="section"><a href="#sec-Installing">5.2.4. Installing Packages</a></span></dt><dt><span class="section"><a href="#sec-Removing">5.2.5. Removing Packages</a></span></dt><dt><span class="section"><a href="#sec-Yum-Transaction_History">5.2.6. Working with Transaction History</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Yum_and_Yum_Repositories">5.3. Configuring Yum and Yum Repositories</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_main_Options">5.3.1. Setting [main] Options</a></span></dt><dt><span class="section"><a href="#sec-Setting_repository_Options">5.3.2. Setting [repository] Options</a></span></dt><dt><span class="section"><a href="#sec-Using_Yum_Variables">5.3.3. Using Yum Variables</a></span></dt><dt><span class="section"><a href="#sec-Viewing_the_Current_Configuration">5.3.4. Viewing the Current Configuration</a></s
pan></dt><dt><span class="section"><a href="#sec-Managing_Yum_Repositories">5.3.5. Adding, Enabling, and Disabling a Yum Repository</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Yum_Repository">5.3.6. Creating a Yum Repository</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Yum_Plugins">5.4. Yum Plug-ins</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">5.4.1. Enabling, Configuring, and Disabling Yum Plug-ins</a></span></dt><dt><span class="section"><a href="#sec-Installing_More_Yum_Plugins">5.4.2. Installing Additional Yum Plug-ins</a></span></dt><dt><span class="section"><a href="#sec-Plugin_Descriptions">5.4.3. Plug-in Descriptions</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Additional_Resources">5.5. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#part-Infrastructure_Services">III. Infrastructure Services</a></spa
n></dt><dd><dl><dt><span class="chapter"><a href="#ch-Services_and_Daemons">6. Services and Daemons</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-services-configuring">6.1. Configuring Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-configuration-enabling">6.1.1. Enabling the Service</a></span></dt><dt><span class="section"><a href="#s3-services-configuration-disabling">6.1.2. Disabling the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-running">6.2. Running Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-running-checking">6.2.1. Checking the Service Status</a></span></dt><dt><span class="section"><a href="#s3-services-running-running">6.2.2. Running the Service</a></span></dt><dt><span class="section"><a href="#s3-services-running-stopping">6.2.3. Stopping the Service</a></span></dt><dt><span class="section"><a href="#s3-services-running-restarting">6.2.4. Resta
rting the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-additional-resources">6.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-additional-resources-installed">6.3.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-services-additional-resources-books">6.3.2. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-OpenSSH">7. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ssh-protocol">7.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-why">7.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a href="#s2-ssh-features">7.1.2. Main Features</a></span></dt><dt><span class="section"><a href="#s2-ssh-versions">7.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="#s2-ssh-conn">7.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><sp
an class="section"><a href="#s1-ssh-configuration">7.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-configuration-configs">7.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-sshd">7.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-requiring">7.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-keypairs">7.2.4. Using Key-based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-clients">7.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-clients-ssh">7.3.1. Using the ssh Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-scp">7.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-sftp">7.3.3. Using the <code cla
ss="command">sftp</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-beyondshell">7.4. More Than a Secure Shell</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-beyondshell-x11">7.4.1. X11 Forwarding</a></span></dt><dt><span class="section"><a href="#s2-ssh-beyondshell-tcpip">7.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-openssh-additional-resources">7.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-TigerVNC">8. TigerVNC</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-vnc-server">8.1. VNC Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-vnc-installation">8.1.1. Installing VNC Server</a></span></dt><dt><span class="section"><a href="#s3-configuring-vnc-server">8.1.2. Configuring VNC Server</a></span></dt><dt><span class="section"><a href="#s4-starting-vncserver">8.1.3. Starting VNC Server</a></span></dt><dt><span c
lass="section"><a href="#terminating-vnc-session">8.1.4. Terminating a VNC Session</a></span></dt></dl></dd><dt><span class="section"><a href="#s5-vnc-viewer">8.2. VNC Viewer</a></span></dt><dd><dl><dt><span class="section"><a href="#installing-vncviewer">8.2.1. Installing VNC Viewer</a></span></dt><dt><span class="section"><a href="#s6-connecting-vnc-viewer">8.2.2. Connecting to VNC Server</a></span></dt><dt><span class="section"><a href="#s1-using_ssh">8.2.3. Connecting to VNC Server Using SSH</a></span></dt></dl></dd><dt><span class="section"><a href="#s9-additional-sources">8.3. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#part-Servers">IV. Servers</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-Web_Servers">9. Web Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-The_Apache_HTTP_Server">9.1. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-changes">9.
1.1. Notable Changes</a></span></dt><dt><span class="section"><a href="#s2-apache-version2-migrating">9.1.2. Updating the Configuration</a></span></dt><dt><span class="section"><a href="#s2-apache-running">9.1.3. Running the httpd Service</a></span></dt><dt><span class="section"><a href="#s2-apache-editing">9.1.4. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="#s2-apache-dso">9.1.5. Working with Modules</a></span></dt><dt><span class="section"><a href="#s2-apache-virtualhosts">9.1.6. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="#s2-apache-mod_ssl">9.1.7. Setting Up an SSL Server</a></span></dt><dt><span class="section"><a href="#s2-apache-resources">9.1.8. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Mail_Servers">10. Mail Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-email-protocols">10.1. Email Protocols</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-email-protocols-send">10.1.1. Mail Transport Protocols</a></span></dt><dt><span class="section"><a href="#s2-email-protocols-client">10.1.2. Mail Access Protocols</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-types">10.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-types-mta">10.2.1. Mail Transport Agent</a></span></dt><dt><span class="section"><a href="#s2-email-types-mda">10.2.2. Mail Delivery Agent</a></span></dt><dt><span class="section"><a href="#s2-email-types-mua">10.2.3. Mail User Agent</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mta">10.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-mta-postfix">10.3.1. Postfix</a></span></dt><dt><span class="section"><a href="#s2-email-mta-sendmail">10.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="#s2-email-mta-fetchmail">10.3.3. Fetchma
il</a></span></dt><dt><span class="section"><a href="#s2-email-switchmail">10.3.4. Mail Transport Agent (MTA) Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mda">10.4. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-procmail-configuration">10.4.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="#s2-email-procmail-recipes">10.4.2. Procmail Recipes</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mua">10.5. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-security">10.5.1. Securing Communication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-additional-resources">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-installed-docs">10.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-email-useful-websites">10.6.2. Useful Web
sites</a></span></dt><dt><span class="section"><a href="#s2-email-related-books">10.6.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Directory_Servers">11. Directory Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-OpenLDAP">11.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-introduction">11.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-installation">11.1.2. Installing the OpenLDAP Suite</a></span></dt><dt><span class="section"><a href="#s2-ldap-configuration">11.1.3. Configuring an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="#s2-selinux-openldap">11.1.4. SELinux Policy for Applications Using LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-running">11.1.5. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="#s2-ldap-pam">11.1.6. Configuring a System to Authenticate Using OpenLDAP<
/a></span></dt><dt><span class="section"><a href="#s2-ldap-resources">11.1.7. Additional Resources</a></span></dt><dt><span class="section"><a href="#s3-ldap-related-books">11.1.8. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-File_and_Print_Servers">12. File and Print Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Samba">12.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="#samba-rgs-overview">12.1.1. Introduction to Samba</a></span></dt><dt><span class="section"><a href="#s2-samba-daemons">12.1.2. Samba Daemons and Related Services</a></span></dt><dt><span class="section"><a href="#s2-samba-connect-share">12.1.3. Connecting to a Samba Share</a></span></dt><dt><span class="section"><a href="#s2-samba-configuring">12.1.4. Configuring a Samba Server</a></span></dt><dt><span class="section"><a href="#s2-samba-startstop">12.1.5. Starting and Stopping Samba</a></span></dt><dt><span class="section">
<a href="#s2-samba-servers">12.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">12.1.7. Samba Security Modes</a></span></dt><dt><span class="section"><a href="#s2-samba-account-info-dbs">12.1.8. Samba Account Information Databases</a></span></dt><dt><span class="section"><a href="#s2-samba-network-browsing">12.1.9. Samba Network Browsing</a></span></dt><dt><span class="section"><a href="#s2-samba-cups">12.1.10. Samba with CUPS Printing Support</a></span></dt><dt><span class="section"><a href="#s2-samba-programs">12.1.11. Samba Distribution Programs</a></span></dt><dt><span class="section"><a href="#s2-samba-resources">12.1.12. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-FTP">12.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-protocol">12.2.1. The File Transfer Protocol</a></span></dt><dt><span class="section"
><a href="#s2-ftp-servers">12.2.2. FTP Servers</a></span></dt><dt><span class="section"><a href="#s3-ftp-vsftpd-conf">12.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-start">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf">12.2.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-resources">12.2.6. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Printer_Configuration">12.3. Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Starting_Printer_Config">12.3.1. Starting the Printers Configuration Tool</a></span></dt><dt><span class="section"><a href="#sec-Setting_Printer">12.3.2. Starting Printer Setup</a></span></dt><dt><span class="section"><a href="#sec-Adding_Other_Printe
r">12.3.3. Adding a Local Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-jetdirect-printer">12.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="#s1-printing-ipp-printer">12.3.5. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="#sec-printing-LPDLPR-printer">12.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-smb-printer">12.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="#s1-printing-select-model">12.3.8. Selecting the Printer Model and Finishing</a></span></dt><dt><span class="section"><a href="#s1-printing-test-page">12.3.9. Printing a Test Page</a></span></dt><dt><span class="section"><a href="#s1-printing-edit">12.3.10. Modifying Existing Printers</a></span></dt><dt><span class="section"><a href="#s1-printing-additional-resources">12.3.11. Additional Resources</a></span></dt></dl></dd></dl></
dd><dt><span class="chapter"><a href="#ch-Configuring_NTP_Using_the_chrony_Suite">13. Configuring NTP Using the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Introduction_to_the_chrony_Suite">13.1. Introduction to the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-differences_between_ntpd_and_chronyd">13.1.1. Differences Between ntpd and chronyd</a></span></dt><dt><span class="section"><a href="#sect-Choosing_between_NTP_daemon">13.1.2. Choosing Between NTP Daemons</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Understanding_chrony_and-its_configuration">13.2. Understanding chrony and Its Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Understanding_chronyd">13.2.1. Understanding chronyd</a></span></dt><dt><span class="section"><a href="#sect-Understanding_chronyc">13.2.2. Understanding chronyc</a></span></dt><dt><span class="section"><a href="#sect-Understanding_the
_chrony_configuration_commands">13.2.3. Understanding the chrony Configuration Commands</a></span></dt><dt><span class="section"><a href="#sect-Security_with_chronyc">13.2.4. Security with chronyc</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Using_chrony">13.3. Using chrony</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Installing_chrony">13.3.1. Installing chrony</a></span></dt><dt><span class="section"><a href="#sect-Checking_the_Status_of_chronyd">13.3.2. Checking the Status of chronyd</a></span></dt><dt><span class="section"><a href="#sect-Starting_chronyd">13.3.3. Starting chronyd</a></span></dt><dt><span class="section"><a href="#sect-Stopping_chronyd">13.3.4. Stopping chronyd</a></span></dt><dt><span class="section"><a href="#sect-Checking_if_chrony_is_synchronized">13.3.5. Checking if chrony is Synchronized</a></span></dt><dt><span class="section"><a href="#sect-Manually_Adjusting-the-System_Clock">13.3.6. Manually Adjusting the
System Clock</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Setting_up_chrony_for_different_environments">13.4. Setting Up chrony for Different Environments</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">13.4.1. Setting Up chrony for a System Which is Infrequently Connected</a></span></dt><dt><span class="section"><a href="#sect-Setting_up_chrony_for_a_system_in_an_isolated_network">13.4.2. Setting Up chrony for a System in an Isolated Network</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Using_chronyc">13.5. Using chronyc</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Using_chronyc_chronyc_to_control_chronyd">13.5.1. Using chronyc to Control chronyd</a></span></dt><dt><span class="section"><a href="#sect-Using_chronyc_for_remote_administration">13.5.2. Using chronyc for Remote Administration</a></span></dt></dl></dd><dt><span class="sectio
n"><a href="#sect-additional_resources">13.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-chrony-docs-inst">13.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-chrony_Online_Documentation">13.6.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_NTP_Using_ntpd">14. Configuring NTP Using ntpd</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Introduction_to_NTP">14.1. Introduction to NTP</a></span></dt><dt><span class="section"><a href="#s1-NTP_Strata">14.2. NTP Strata</a></span></dt><dt><span class="section"><a href="#s1-Understanding_NTP">14.3. Understanding NTP</a></span></dt><dt><span class="section"><a href="#s1-Understanding_the_Drift_File">14.4. Understanding the Drift File</a></span></dt><dt><span class="section"><a href="#s1-UTC_timezones_and_DST">14.5. UTC, Timezones, and DST</a></span></dt><dt><span class="section"><a href="
#s1-Authentication_Options_for_NTP">14.6. Authentication Options for NTP</a></span></dt><dt><span class="section"><a href="#s1-Managing_the_Time_on_Virtual_Machines">14.7. Managing the Time on Virtual Machines</a></span></dt><dt><span class="section"><a href="#s1-Understanding_Leap_Seconds">14.8. Understanding Leap Seconds</a></span></dt><dt><span class="section"><a href="#s1-Understanding_the_ntpd_Configuration_File">14.9. Understanding the ntpd Configuration File</a></span></dt><dt><span class="section"><a href="#s1-Understanding_the_ntpd_Sysconfig_File">14.10. Understanding the ntpd Sysconfig File</a></span></dt><dt><span class="section"><a href="#s1-Disabling_chrony">14.11. Disabling chrony</a></span></dt><dt><span class="section"><a href="#s1-Checking_if_the_NTP_Daemon_is_Installed">14.12. Checking if the NTP Daemon is Installed</a></span></dt><dt><span class="section"><a href="#s1-Installing_the_NTP_Daemon_ntpd">14.13. Installing the NTP Daemon (ntpd)</a></span></dt><d
t><span class="section"><a href="#s1-Checking_the_status_of_NTP">14.14. Checking the Status of NTP</a></span></dt><dt><span class="section"><a href="#s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets">14.15. Configure the Firewall to Allow Incoming NTP Packets</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Change_the_firewall_settings">14.15.1. Change the Firewall Settings</a></span></dt><dt><span class="section"><a href="#s2-Open_Ports_in_the_firewall_for_ntp_packets">14.15.2. Open Ports in the Firewall for NTP Packets</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-Configure_ntpdate_Servers">14.16. Configure ntpdate Servers</a></span></dt><dt><span class="section"><a href="#s1-Configure_NTP">14.17. Configure NTP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Configure_Access_Control_to_an_NTP_service">14.17.1. Configure Access Control to an NTP Service</a></span></dt><dt><span class="section"><a href="#s2_Configure_Rate_L
imiting_Access_to_an_NTP_Service">14.17.2. Configure Rate Limiting Access to an NTP Service</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Peer_Address">14.17.3. Adding a Peer Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Server_Address">14.17.4. Adding a Server Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Broadcast_or_Mutlticast_Server_Address">14.17.5. Adding a Broadcast or Multicast Server Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Manycast_Client_Address">14.17.6. Adding a Manycast Client Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Broadcastclient_Address">14.17.7. Adding a Broadcast Client Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_manycastserver_Address">14.17.8. Adding a Manycast Server Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_multicastclient_Address">14.17.9. Adding a Multicast Client Addre
ss</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_burst_option">14.17.10. Configuring the Burst Option</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_iburst_Option">14.17.11. Configuring the iburst Option</a></span></dt><dt><span class="section"><a href="#s2_Configuring_Symmetric_Authentication_Using_a_Key">14.17.12. Configuring Symmetric Authentication Using a Key</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_Poll_Interval">14.17.13. Configuring the Poll Interval</a></span></dt><dt><span class="section"><a href="#s2_Configuring_Server_Preference">14.17.14. Configuring Server Preference</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_Time-To-Live_for_NTP_Packets">14.17.15. Configuring the Time-to-Live for NTP Packets</a></span></dt><dt><span class="section"><a href="#s2_Configuring_The_Version_of_NTP_to_use">14.17.16. Configuring the NTP Version to Use</a></span></dt></dl></dd><dt><sp
an class="section"><a href="#s1-Configuring_the_Hardware_Clock_update">14.18. Configuring the Hardware Clock Update</a></span></dt><dt><span class="section"><a href="#s1-Configuring_Clock_Sources">14.19. Configuring Clock Sources</a></span></dt><dt><span class="section"><a href="#s1-ntpd_additional-resources">14.20. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ntpd-docs-inst">14.20.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-ntpd_useful-websites">14.20.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_PTP_Using_ptp4l">15. Configuring PTP Using ptp4l</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Introduction_to_PTP">15.1. Introduction to PTP</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Understanding_PTP">15.1.1. Understanding PTP</a></span></dt><dt><span class="section"><a href="#sec-Advantages_of_PTP">15.1.2. Adv
antages of PTP</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_PTP">15.2. Using PTP</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_for_Driver_and_Hardware_Support">15.2.1. Checking for Driver and Hardware Support</a></span></dt><dt><span class="section"><a href="#sec-Installing_PTP">15.2.2. Installing PTP</a></span></dt><dt><span class="section"><a href="#sec-Starting_ptp4l">15.2.3. Starting ptp4l</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Specifying_a_Configuration_File">15.3. Specifying a Configuration File</a></span></dt><dt><span class="section"><a href="#sec-Using_the_PTP_Management_Client">15.4. Using the PTP Management Client</a></span></dt><dt><span class="section"><a href="#sec-Synchronizing_the_Clocks">15.5. Synchronizing the Clocks</a></span></dt><dt><span class="section"><a href="#sec-Verifying_Time_Synchronization">15.6. Verifying Time Synchronization</a></span></dt><dt><span class="section"><
a href="#sec-Serving_PTP_Time_with_NTP">15.7. Serving PTP Time with NTP</a></span></dt><dt><span class="section"><a href="#sec-Serving_NTP_Time_with_PTP">15.8. Serving NTP Time with PTP</a></span></dt><dt><span class="section"><a href="#sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster">15.9. Synchronize to PTP or NTP Time Using timemaster</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Starting_timemaster_as_a_Service">15.9.1. Starting timemaster as a Service</a></span></dt><dt><span class="section"><a href="#sec-Understanding_the_timemaster_Configuration_File">15.9.2. Understanding the timemaster Configuration File</a></span></dt><dt><span class="section"><a href="#sec-Configuring_timemaster_Options">15.9.3. Configuring timemaster Options</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Improving_Accuracy">15.10. Improving Accuracy</a></span></dt><dt><span class="section"><a href="#sec-PTP_additional_resources">15.11. Additional Resources</
a></span></dt><dd><dl><dt><span class="section"><a href="#sec-PTP-docs-inst">15.11.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-PTP_useful-websites">15.11.2. Useful Websites</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="#part-Monitoring_and_Automation">V. 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. Viewing System Processes</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-system-processes-ps">16.1.1. Using the ps Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-system-processes-top">16.1.2. Using the top Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-system-processes-system_monitor">16.1.3. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span cla
ss="section"><a href="#s1-sysinfo-memory-usage">16.2. Viewing Memory Usage</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-memory-usage-free">16.2.1. Using the free Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-memory-usage-system_monitor">16.2.2. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-cpu">16.3. Viewing CPU Usage</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-cpu-system_monitor">16.3.1. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-filesystems">16.4. Viewing Block Devices and File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-filesystems-lsblk">16.4.1. Using the lsblk Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-blkid">16.4.2. Using the blkid Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystem
s-partx">16.4.3. Using the partx Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-findmnt">16.4.4. Using the findmnt Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-df">16.4.5. Using the df Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-du">16.4.6. Using the du Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-system_monitor">16.4.7. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-hardware">16.5. Viewing Hardware Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-hardware-lspci">16.5.1. Using the lspci Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lsusb">16.5.2. Using the lsusb Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lspcmcia">16.5.3. Using the lspcmcia Command</a></span></dt><dt><span cla
ss="section"><a href="#s2-sysinfo-hardware-lscpu">16.5.4. Using the lscpu Command</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP">16.6. Monitoring Performance with Net-SNMP</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Installing">16.6.1. Installing Net-SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Running">16.6.2. Running the Net-SNMP Daemon</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Configuring">16.6.3. Configuring Net-SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Retrieving">16.6.4. Retrieving Performance Data over SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Extending">16.6.5. Extending Net-SNMP</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-additional-resou
rces">16.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-installed-docs">16.7.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-logfiles-locating">17.1. Locating Log Files</a></span></dt><dt><span class="section"><a href="#s1-basic_configuration_of_rsyslog">17.2. Basic Configuration of Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Filters">17.2.1. Filters</a></span></dt><dt><span class="section"><a href="#s2-Actions">17.2.2. Actions</a></span></dt><dt><span class="section"><a href="#s2-Templates">17.2.3. Templates</a></span></dt><dt><span class="section"><a href="#s2-global_directives">17.2.4. Global Directives</a></span></dt><dt><span class="section"><a href="#s2-log_rotation">17.2.5. Log Rotation</a></span></dt><dt><span class=
"section"><a href="#s2-using_the_new_configuration_format">17.2.6. Using the New Configuration Format</a></span></dt><dt><span class="section"><a href="#s2-Rulesets">17.2.7. Rulesets</a></span></dt><dt><span class="section"><a href="#s2-compatibility_with_syslogd">17.2.8. Compatibility with syslogd</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-working_with_queues_in_rsyslog">17.3. Working with Queues in Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-defining_queues">17.3.1. Defining Queues</a></span></dt><dt><span class="section"><a href="#s2-managing_queues">17.3.2. Managing Queues</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-using_rsyslog_modules">17.4. Using Rsyslog Modules</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-importing_text_files">17.4.1. Importing Text Files</a></span></dt><dt><span class="section"><a href="#s2-exporting_messages_to_a_database">17.4.2. Exporting Messages to a Database</
a></span></dt><dt><span class="section"><a href="#s2-enabling_encrypted_transport">17.4.3. Enabling Encrypted Transport</a></span></dt><dt><span class="section"><a href="#s2-using_RELP">17.4.4. Using RELP</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-interaction_of_rsyslog_and_journal">17.5. Interaction of Rsyslog and Journal</a></span></dt><dt><span class="section"><a href="#s1-structured_logging_with_rsyslog">17.6. Structured Logging with Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-importing_data_from_journal">17.6.1. Importing Data from Journal</a></span></dt><dt><span class="section"><a href="#s2-filtering_structured_messages">17.6.2. Filtering Structured Messages</a></span></dt><dt><span class="section"><a href="#s2-parsing_JSON">17.6.3. Parsing JSON</a></span></dt><dt><span class="section"><a href="#s2-storing_messages_in_the_mongodb">17.6.4. Storing Messages in the MongoDB</a></span></dt></dl></dd><dt><span class="section"><
a href="#s1-debugging_rsyslog">17.7. Debugging Rsyslog</a></span></dt><dt><span class="section"><a href="#s1-Using_the_Journal">17.8. Using the Journal</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Viewing_Log_Files">17.8.1. Viewing Log Files</a></span></dt><dt><span class="section"><a href="#s2-Access_Control">17.8.2. Access Control</a></span></dt><dt><span class="section"><a href="#s2-Using_The_Live_View">17.8.3. Using The Live View</a></span></dt><dt><span class="section"><a href="#s2-Filtering_Messages">17.8.4. Filtering Messages</a></span></dt><dt><span class="section"><a href="#s2-Enabling_Persistent_Storage">17.8.5. Enabling Persistent Storage</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-managing_log_files_in_a_graphical_environment">17.9. Managing Log Files in a Graphical Environment</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-logfiles-viewing">17.9.1. Viewing Log Files</a></span></dt><dt><span class="section"><a h
ref="#s2-logfiles-adding">17.9.2. Adding a Log File</a></span></dt><dt><span class="section"><a href="#s2-logfiles-examining">17.9.3. Monitoring Log Files</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-log-files-additional-resources">17.10. Additional Resources</a></span></dt></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="#sect-Cron-Installing">18.1.1. Installing Cron and Anacron</a></span></dt><dt><span class="section"><a href="#sect-Cron-Running">18.1.2. Running the Crond Service</a></span></dt><dt><span class="section"><a href="#s2-configuring-anacron-jobs">18.1.3. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="#s2-configuring-cron-jobs">18.1.4. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a
href="#s2-autotasks-cron-access">18.1.5. Controlling Access to Cron</a></span></dt><dt><span class="section"><a href="#s2-black-white-listing-of-cron-jobs">18.1.6. Black and 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="#sect-At_and_Batch_Installation">18.2.1. Installing At and Batch</a></span></dt><dt><span class="section"><a href="#sect-Atd-Running">18.2.2. Running the At Service</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-configuring">18.2.3. Configuring an At Job</a></span></dt><dt><span class="section"><a href="#s2-autotasks-batch-configuring">18.2.4. Configuring a Batch Job</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-viewing">18.2.5. Viewing Pending Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-commandline-options">18.2.6. Additional Command Line Options<
/a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-controlling-access">18.2.7. Controlling Access to At and Batch</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-autotasks-additional-resources">18.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-OProfile">19. OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-overview-tools">19.1. Overview of Tools</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-operf_vs_opcontrol">19.1.1. operf vs. opcontrol</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-using-operf">19.2. Using operf</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-operf-kernel">19.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="#s2-operf-events">19.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="#s2-operf-categorization">19.2.3. Categorization of Samples</a></span
></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-configuring">19.3. Configuring OProfile Using Legacy Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-kernel">19.3.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="#s2-oprofile-events">19.3.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="#s2-oprofile-starting-separate">19.3.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-starting">19.4. Starting and Stopping OProfile Using Legacy Mode</a></span></dt><dt><span class="section"><a href="#s1-oprofile-saving-data">19.5. Saving Data in Legacy Mode</a></span></dt><dt><span class="section"><a href="#s1-oprofile-analyzing-data">19.6. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-reading-opreport">19.6.1. Using <code class="command">opreport</code></a></span></dt><dt><span clas
s="section"><a href="#s2-oprofile-reading-opreport-single">19.6.2. Using opreport on a Single Executable</a></span></dt><dt><span class="section"><a href="#s2-oprofile-module-output">19.6.3. Getting More Detailed Output on the Modules</a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opannotate">19.6.4. Using <code class="command">opannotate</code></a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-dev-oprofile">19.7. Understanding the /dev/oprofile/ directory </a></span></dt><dt><span class="section"><a href="#s1-oprofile-example-usage">19.8. Example Usage</a></span></dt><dt><span class="section"><a href="#s1-oprofile-java-support">19.9. OProfile Support for Java</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-java-profiling">19.9.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-gui">19.10. Graphical Interface</a></span></dt><dt><span class="section"><a href="#s1
-oprofile-and-systemtap">19.11. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="#s1-oprofile_additional_resources">19.12. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="#part-Kernel_Module_and_Driver_Configuration">VI. Kernel, Module and Driver Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="#ch-Working_with_the_GRUB_2_Boot_Loader">20. Working with the GRUB 2 Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configuring_the_GRUB_2_Boot_Loader">20.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="#sec-Customizing_GRUB_2_Menu">20.2. Customizing GRUB 2 Menu</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Changing_the_Default_Boot_Entry">20.2.1. Changing the Default Boot Entry</a></span></dt><dt><span class="section"><a href="#sec-Editing_an_Entry">20.2.2. Editing an Entry</a></span></dt><dt><span class="section">
<a href="#sec-Adding_a_new_Entry">20.2.3. Adding a new Entry</a></span></dt><dt><span class="section"><a href="#sec-Using_only_a_Custom_Menu">20.2.4. Creating a Custom Menu</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-GRUB_2_Password_Protection">20.3. GRUB 2 Password Protection</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries">20.3.1. Setting Up Users and Password Protection, Specifying Menu Entries</a></span></dt><dt><span class="section"><a href="#sec-Password_Encryption">20.3.2. Password Encryption</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Reinstalling_GRUB_2">20.4. Reinstalling GRUB 2</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Using_the_grub2-install_Command">20.4.1. Using the grub2-install Command</a></span></dt><dt><span class="section"><a href="#sec-Resetting_and_Reinstalling_GRUB_2">20.4.2. Resetting and Reinstalling GRUB 2</a>
</span></dt></dl></dd><dt><span class="section"><a href="#sec-GRUB_2_over_Serial_Console">20.5. GRUB 2 over Serial Console</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configuring_GRUB_2">20.5.1. Configuring GRUB 2</a></span></dt><dt><span class="section"><a href="#sec-Using_screen_to_Connect_to_the_Serial_Console">20.5.2. Using screen to Connect to the Serial Console</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Terminal_Menu_Editing_During_Boot">20.6. Terminal Menu Editing During Boot</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Booting_to_Rescue_Mode">20.6.1. Booting to Rescue Mode</a></span></dt><dt><span class="section"><a href="#sec-Booting_to_Emergency_Mode">20.6.2. Booting to Emergency Mode</a></span></dt><dt><span class="section"><a href="#sec-Changing_and_Resetting_the_Root_Password">20.6.3. Changing and Resetting the Root Password</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-UEFI_Secure_Boo
t">20.7. UEFI Secure Boot</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-UEFI_Secure_Boot_Support_in_Fedora">20.7.1. UEFI Secure Boot Support in Fedora</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources">20.8. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Manually_Upgrading_the_Kernel">21. Manually Upgrading the Kernel</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kernel-packages">21.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="#s1-kernel-preparing">21.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="#s1-kernel-download">21.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="#s1-kernel-perform-upgrade">21.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="#sec-Verifying_the_Initial_RAM_Disk_Image">21.5. Verifying the I
nitial RAM Disk Image</a></span></dt><dt><span class="section"><a href="#s1-kernel-boot-loader">21.6. Verifying the Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-kernel-boot-loader-grub">21.6.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-iseries">21.6.2. Configuring the OS/400 Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-pseries">21.6.3. Configuring the YABOOT Boot Loader</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Working_with_Kernel_Modules">22. Working with Kernel Modules</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="#sec-Displaying_Information_About_a_Module">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="#sec-Loading_a_Module"
>22.3. Loading a Module</a></span></dt><dt><span class="section"><a href="#sec-Unloading_a_Module">22.4. Unloading a Module</a></span></dt><dt><span class="section"><a href="#sec-Setting_Module_Parameters">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="#sec-Persistent_Module_Loading">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="#sect-signing-kernel-modules-for-secure-boot">22.7. Signing Kernel Modules for Secure Boot</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-prerequisites">22.7.1. Prerequisites</a></span></dt><dt><span class="section"><a href="#sect-kernel-module-authentication">22.7.2. Kernel Module Authentication</a></span></dt><dt><span class="section"><a href="#sect-generating-a-public-private-x509-key-pair">22.7.3. Generating a Public and Private X.509 Key Pair</a></span></dt><dt><span class="section"><a href="#sect-enrolling-public-key-on-target-system">22.7.4. Enrolling Publi
c Key on Target System</a></span></dt><dt><span class="section"><a href="#sect-signing-kernel-module-with-the-private-key">22.7.5. Signing Kernel Module with the Private Key</a></span></dt><dt><span class="section"><a href="#sect-loading-signed-kernel-module">22.7.6. Loading Signed Kernel Module</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kernel-modules-additional-resources">22.8. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="#ch-RPM">A. RPM</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-rpm-design">A.1. RPM 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="#sec-Installing_and_Upgrading">A.2.1. Installing and Upgrading Packages</a></span></dt><dt><span class="section"><a href="#s2-rpm-uninstalling">A.2.2. Uninstalling Packages</a></span></dt><dt><span class="section"><a href="#s2-rpm-freshening">
A.2.3. Freshening Packages</a></span></dt><dt><span class="section"><a href="#s2-rpm-querying">A.2.4. Querying Packages</a></span></dt><dt><span class="section"><a href="#s2-rpm-verifying">A.2.5. Verifying Packages</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-find-verify-rpm">A.3. Finding and Verifying RPM Packages</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-rpm-finding">A.3.1. Finding RPM Packages</a></span></dt><dt><span class="section"><a href="#s1-check-rpm-sig">A.3.2. Checking Package Signatures</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-rpm-usage-examples">A.4. Common Examples of RPM Usage</a></span></dt><dt><span class="section"><a href="#s1-rpm-additional-resources">A.5. Additional Resources</a></span></dt></dl></dd><dt><span class="appendix"><a href="#app-Revision_History">B. Revision History</a></span></dt><dt><span class="index"><a href="#idm261761687520">Index</a></span></dt></dl></div><div xml:lang="en-US
" class="preface" id="idm261754805696" lang="en-US"><div class="titlepage"><div><div><h1 id="idm261754805696" class="title">Preface</h1></div></div></div><div class="para">
The <em class="citetitle">System Administrator's Guide</em> contains information on how to customize the Fedora 21 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:
@@ -42,7 +42,7 @@
</div></li><li class="listitem"><div class="para">
Working with kernel modules and upgrading the kernel
</div></li></ul></div><div class="section" id="sect-Preface-Target_Audience"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1. Target Audience</h2></div></div></div><div class="para">
- The <em class="citetitle">System Administrator's Guide</em> assumes you have a basic understanding of the Fedora operating system. If you need help with the installation of this system, refer to the <a href="http://docs.fedoraproject.org/install-guide">Fedora 21 Installation Guide</a>.
+ The <em class="citetitle">System Administrator's Guide</em> assumes you have a basic understanding of the Fedora operating system. If you need help with the installation of this system, refer to the <a href="http://docs.fedoraproject.org/install-guide">Fedora Installation Guide</a>.
</div></div><div class="section" id="sect-Preface-Book_Organization"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2. 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 class="variablelist"><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">
@@ -92,16 +92,16 @@
</div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="#part-Kernel_Module_and_Driver_Configuration">Part VI, “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 on 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.
+ <a class="xref" href="#ch-Manually_Upgrading_the_Kernel">Chapter 21, <em>Manually Upgrading the Kernel</em></a> provides important information on how to manually update a kernel package using the <code class="command">rpm</code> command instead of <code class="command">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.
+ <a class="xref" href="#ch-Working_with_Kernel_Modules">Chapter 22, <em>Working with Kernel Modules</em></a> explains how to display, query, load, and unload kernel modules and their dependencies, and how to set module parameters. Additionally, it covers specific kernel module capabilities such as using multiple Ethernet cards and using channel bonding. Read this chapter if you need to work with kernel modules.
</div></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></dl></div></div><div xml:lang="en-US" class="section" id="idm225451968192" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm225451968192">3. Document Conventions</h2></div></div></div><div class="para">
+ </div></dd></dl></div></div><div xml:lang="en-US" class="section" id="idm261747249120" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm261747249120">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" id="idm225473504768"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225473504768">3.1. Typographic Conventions</h3></div></div></div><div class="para">
+ </div><div class="section" id="idm261713030576"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm261713030576">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>
@@ -149,7 +149,7 @@
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" id="idm225425141184"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225425141184">3.2. Pull-quote Conventions</h3></div></div></div><div class="para">
+ </div></blockquote></div></div><div class="section" id="idm261786304416"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm261786304416">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:
@@ -174,7 +174,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
System.<span class="perl_Function">out</span>.<span class="perl_Function">println</span>(<span class="perl_String">"Echo.echo('Hello') = "</span> + echo.<span class="perl_Function">echo</span>(<span class="perl_String">"Hello"</span>));
}
-}</pre></div><div class="section" id="idm225457571360"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225457571360">3.3. Notes and Warnings</h3></div></div></div><div class="para">
+}</pre></div><div class="section" id="idm261728877104"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm261728877104">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.
@@ -182,7 +182,7 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
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="idm225449959504" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm225449959504">4. We Need Feedback!</h2></div></div></div><a id="idm225471189760" class="indexterm"></a><div class="para">
+ </div></div></div></div></div><div xml:lang="en-US" class="section" id="idm261712903024" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm261712903024">4. We Need Feedback!</h2></div></div></div><a id="idm261712901856" class="indexterm"></a><div class="para">
If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: <a href="https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora Documentation&component=system-administrator's-guide">https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora Documentation&component=system-administrator's-guide</a>
</div><div class="para">
If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
@@ -192,9 +192,9 @@ books_tests Desktop1 downloads images notes scripts svgs</pre><div cla
<a class="xref" href="#sect-System_Monitoring_Tools-Net-SNMP">Section 16.6, “Monitoring Performance with Net-SNMP”</a> is based on an article written by Michael Solberg.
</div><div class="para">
The authors of this book would like to thank the following people for their valuable contributions: Adam Tkáč, Andrew Fitzsimon, Andrius Benokraitis, Brian Cleary Edward Bailey, Garrett LeSage, Jeffrey Fearn, Joe Orton, Joshua Wulf, Karsten Wade, Lucy Ringland, Marcela Mašláňová, Mark Johnson, Michael Behm, Miroslav Lichvár, Radek Vokál, Rahul Kavalapara, Rahul Sundaram, Sandra Moore, Zbyšek Mráz, Jan Včelák, Peter Hutterer, T.C. Hollingsworth, and James Antill, among many others.
- </div></div></div><div class="part" id="part-Basic_System_Configuration"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part I. Basic System Configuration</h1></div></div></div><div class="partintro" id="idm225462030656"><div></div><div class="para">
+ </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="idm261747994192"><div></div><div class="para">
This part covers basic system administration tasks such as keyboard configuration, date and time configuration, managing users and groups, and gaining privileges.
- </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#ch-Opening_GUI_Applications">1. Opening Graphical Applications</a></span></dt><dd><dl><dt><span class="section"><a href="#gui-from_cli">1.1. Opening graphical applications from the command line</a></span></dt><dt><span class="section"><a href="#gui-alt_f2">1.2. Launching Applications with <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> </a></span></dt><dt><span class="section"><a href="#gui-from_menu">1.3. Launching applications from the Desktop Menu</a></span></dt><dd><dl><dt><span class="section"><a href="#gui-from_menu-gnome">1.3.1. Using GNOME menus</a></span></dt><dt><span class="section"><a href="#gui-from_menu-kde">1.3.2. Using KDE menus </a></span></dt><dt><span class="section"><a href="#idm225459881376">1.3.3. Using menus in LXDE, MATE, and XFCE</a></span></dt></dl></dd></dl></dd><dt><span class="ch
apter"><a href="#ch-System_Locale_and_Keyboard_Configuration">2. System Locale and Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Setting_the_System_Locale">2.1. Setting the System Locale</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Displaying_the_Current_Status">2.1.1. Displaying the Current Status</a></span></dt><dt><span class="section"><a href="#s2-Listing_Available_Locales">2.1.2. Listing Available Locales</a></span></dt><dt><span class="section"><a href="#s2-Setting_the_Locale">2.1.3. Setting the Locale</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-Changing_the_Keyboard_Layout">2.2. Changing the Keyboard Layout</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Displaying_the_Current_Settings">2.2.1. Displaying the Current Settings</a></span></dt><dt><span class="section"><a href="#s2-Listing_Available_Keymaps">2.2.2. Listing Available Keymaps</a></span></dt><dt><span class="section"><a
href="#s2-Setting_the_Keymap">2.2.3. Setting the Keymap</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Keyboard_Configuration-Resources">2.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_the_Date_and_Time">3. Configuring the Date and Time</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl">3.1. Using the timedatectl Command</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Display">3.1.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Time">3.1.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Date">3.1.3. Changing the Current Date</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Time_
Zone">3.1.4. Changing the Time Zone</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-NTP">3.1.5. Synchronizing the System Clock with a Remote Server</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date">3.2. Using the date Command</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date-Display">3.2.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date-Time">3.2.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date-Date">3.2.3. Changing the Current Date</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-hwclock">3.3. Using the hwclock Command</a></span></dt><dd><dl><dt><span class="section"><a href="#sect2-displaying-time-hwclock">3.3.1. Displaying the C
urrent Date and Time</a></span></dt><dt><span class="section"><a href="#sect3-changing-date-time-hwclock">3.3.2. Setting the Date and Time</a></span></dt><dt><span class="section"><a href="#sect4-synchronizing-date-time-hwclock">3.3.3. Synchronizing the Date and Time</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Date_and_Time-Resources">3.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Managing_Users_and_Groups">4. Managing Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-users-groups-introduction">4.1. Introduction to Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-groups-private-groups">4.1.1. User Private Groups</a></span></dt><dt><span class="section"><a href="#s2-users-groups-shadow-utilities">4.1.2. Shadow Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-configui">4.2. Using the User Manager Tool</a></span></dt><d
d><dl><dt><span class="section"><a href="#s2-redhat-config-users-list">4.2.1. Viewing Users and Groups</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-tools">4.3. Using Command Line Tools</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-tools-users-add">4.3.1. Adding a New User</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-add">4.3.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="#s2-users-tools-password-aging">4.3.3. Enabling Password Aging</a></span></dt><dt><span class="section"><a href="#s2-users-tools-users-logout">4.3.4. Enabling Automatic Logouts</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-directories">4.3.5. Creating Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-groups-additional-resources">4.4. Additional Resources</a></span></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" id="ch-Openin
g_GUI_Applications" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 1. Opening Graphical Applications</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#gui-from_cli">1.1. Opening graphical applications from the command line</a></span></dt><dt><span class="section"><a href="#gui-alt_f2">1.2. Launching Applications with <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> </a></span></dt><dt><span class="section"><a href="#gui-from_menu">1.3. Launching applications from the Desktop Menu</a></span></dt><dd><dl><dt><span class="section"><a href="#gui-from_menu-gnome">1.3.1. Using GNOME menus</a></span></dt><dt><span class="section"><a href="#gui-from_menu-kde">1.3.2. Using KDE menus </a></span></dt><dt><span class="section"><a href="#idm225459881376">1.3.3. Using menus in LXDE, MATE, and XFCE</a></span></dt></dl></dd></dl></div><a id="idm225459758848" class="indexterm
"></a><div class="para">
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#ch-Opening_GUI_Applications">1. Opening Graphical Applications</a></span></dt><dd><dl><dt><span class="section"><a href="#gui-from_cli">1.1. Opening graphical applications from the command line</a></span></dt><dt><span class="section"><a href="#gui-alt_f2">1.2. Launching Applications with <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> </a></span></dt><dt><span class="section"><a href="#gui-from_menu">1.3. Launching applications from the Desktop Menu</a></span></dt><dd><dl><dt><span class="section"><a href="#gui-from_menu-gnome">1.3.1. Using GNOME menus</a></span></dt><dt><span class="section"><a href="#gui-from_menu-kde">1.3.2. Using KDE menus </a></span></dt><dt><span class="section"><a href="#idm261653475360">1.3.3. Using menus in LXDE, MATE, and XFCE</a></span></dt></dl></dd></dl></dd><dt><span class="ch
apter"><a href="#ch-System_Locale_and_Keyboard_Configuration">2. System Locale and Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Setting_the_System_Locale">2.1. Setting the System Locale</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Displaying_the_Current_Status">2.1.1. Displaying the Current Status</a></span></dt><dt><span class="section"><a href="#s2-Listing_Available_Locales">2.1.2. Listing Available Locales</a></span></dt><dt><span class="section"><a href="#s2-Setting_the_Locale">2.1.3. Setting the Locale</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-Changing_the_Keyboard_Layout">2.2. Changing the Keyboard Layout</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Displaying_the_Current_Settings">2.2.1. Displaying the Current Settings</a></span></dt><dt><span class="section"><a href="#s2-Listing_Available_Keymaps">2.2.2. Listing Available Keymaps</a></span></dt><dt><span class="section"><a
href="#s2-Setting_the_Keymap">2.2.3. Setting the Keymap</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Keyboard_Configuration-Resources">2.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_the_Date_and_Time">3. Configuring the Date and Time</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl">3.1. Using the timedatectl Command</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Display">3.1.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Time">3.1.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Date">3.1.3. Changing the Current Date</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-Time_
Zone">3.1.4. Changing the Time Zone</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-timedatectl-NTP">3.1.5. Synchronizing the System Clock with a Remote Server</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date">3.2. Using the date Command</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date-Display">3.2.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date-Time">3.2.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-date-Date">3.2.3. Changing the Current Date</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Configuring_the_Date_and_Time-hwclock">3.3. Using the hwclock Command</a></span></dt><dd><dl><dt><span class="section"><a href="#sect2-displaying-time-hwclock">3.3.1. Displaying the C
urrent Date and Time</a></span></dt><dt><span class="section"><a href="#sect3-changing-date-time-hwclock">3.3.2. Setting the Date and Time</a></span></dt><dt><span class="section"><a href="#sect4-synchronizing-date-time-hwclock">3.3.3. Synchronizing the Date and Time</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Date_and_Time-Resources">3.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Managing_Users_and_Groups">4. Managing Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-users-groups-introduction">4.1. Introduction to Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-groups-private-groups">4.1.1. User Private Groups</a></span></dt><dt><span class="section"><a href="#s2-users-groups-shadow-utilities">4.1.2. Shadow Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-configui">4.2. Managing Users in a Graphical Environment</a>
</span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-users-list">4.2.1. Using the Users Settings Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-tools">4.3. Using Command Line Tools</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-tools-users-add">4.3.1. Adding a New User</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-add">4.3.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="#s2-users-tools-password-aging">4.3.3. Enabling Password Aging</a></span></dt><dt><span class="section"><a href="#s2-users-tools-users-logout">4.3.4. Enabling Automatic Logouts</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-directories">4.3.5. Creating Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Users_and_Groups-Resources">4.4. Additional Resources</a></span></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter"
id="ch-Opening_GUI_Applications" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 1. Opening Graphical Applications</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#gui-from_cli">1.1. Opening graphical applications from the command line</a></span></dt><dt><span class="section"><a href="#gui-alt_f2">1.2. Launching Applications with <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> </a></span></dt><dt><span class="section"><a href="#gui-from_menu">1.3. Launching applications from the Desktop Menu</a></span></dt><dd><dl><dt><span class="section"><a href="#gui-from_menu-gnome">1.3.1. Using GNOME menus</a></span></dt><dt><span class="section"><a href="#gui-from_menu-kde">1.3.2. Using KDE menus </a></span></dt><dt><span class="section"><a href="#idm261653475360">1.3.3. Using menus in LXDE, MATE, and XFCE</a></span></dt></dl></dd></dl></div><a id="idm261739048208" cl
ass="indexterm"></a><div class="para">
Fedora provides graphical applications in addition to command line utilities for configuring many features. This chapter describes methods for opening <code class="literal">Graphical User Interface</code>, or <em class="firstterm">GUI</em>, applications in various environments.
</div><div class="section" id="gui-from_cli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.1. Opening graphical applications from the command line</h2></div></div></div><div class="para">
Graphical applications can be launched from a terminal window or console session by simply typing the name of the application.
@@ -293,7 +293,7 @@ root 23874 0.0 0.0 109184 900 pts/21 S+ 15:35 0:00 grep --color=au
Search functionality is also available in the KDE menu system. To search for applications, open the menu and begin typing. The menu will display matching entries.
</div><div class="figure" id="fig-searchmenu_kde"><div class="figure-contents"><div class="mediaobject"><img src="images/searchmenu_KDE.png" alt="Searching with the KDE menu." /><div class="longdesc"><div class="para">
The KDE menu will search for matching applications if you type into the search box. For example, typing <code class="literal">browser</code> will display installed browsers and other matching entries.
- </div></div></div></div><h6>Figure 1.9. Searching with the KDE menu. </h6></div><br class="figure-break" /></div><div class="section" id="idm225459881376"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225459881376">1.3.3. Using menus in LXDE, MATE, and XFCE</h3></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 1.9. Searching with the KDE menu. </h6></div><br class="figure-break" /></div><div class="section" id="idm261653475360"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm261653475360">1.3.3. Using menus in LXDE, MATE, and XFCE</h3></div></div></div><div class="para">
Menus in LXDE, MATE, and XFCE have a varied appearance but a very similar structure. They categorize applications, and the contents of a category are displayed by hovering the cursor over the entry. Applications are launched by clicking on an entry.
</div><div class="figure" id="fig-menu_lxde"><div class="figure-contents"><div class="mediaobject"><img src="images/menu_LXDE.png" alt="The LXDE menu" /><div class="longdesc"><div class="para">
LXDE Menu
@@ -301,10 +301,10 @@ root 23874 0.0 0.0 109184 900 pts/21 S+ 15:35 0:00 grep --color=au
MATE menu
</div></div></div></div><h6>Figure 1.11. MATE menu </h6></div><br class="figure-break" /><div class="figure" id="fig-menu_xfce"><div class="figure-contents"><div class="mediaobject"><img src="images/menu_XFCE.png" alt="XFCE Menu" /><div class="longdesc"><div class="para">
XFCE Menu
- </div></div></div></div><h6>Figure 1.12. XFCE Menu </h6></div><br class="figure-break" /></div></div></div><div xml:lang="en-US" class="chapter" id="ch-System_Locale_and_Keyboard_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. System Locale and Keyboard Configuration</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-Setting_the_System_Locale">2.1. Setting the System Locale</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Displaying_the_Current_Status">2.1.1. Displaying the Current Status</a></span></dt><dt><span class="section"><a href="#s2-Listing_Available_Locales">2.1.2. Listing Available Locales</a></span></dt><dt><span class="section"><a href="#s2-Setting_the_Locale">2.1.3. Setting the Locale</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-Changing_the_Keyboard_Layout">2.2. Changing the Keyboard Layout</a></span></dt><dd><dl><dt><span class="sect
ion"><a href="#s2-Displaying_the_Current_Settings">2.2.1. Displaying the Current Settings</a></span></dt><dt><span class="section"><a href="#s2-Listing_Available_Keymaps">2.2.2. Listing Available Keymaps</a></span></dt><dt><span class="section"><a href="#s2-Setting_the_Keymap">2.2.3. Setting the Keymap</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Keyboard_Configuration-Resources">2.3. Additional Resources</a></span></dt></dl></div><a id="idm225474109648" class="indexterm"></a><div class="para">
+ </div></div></div></div><h6>Figure 1.12. XFCE Menu </h6></div><br class="figure-break" /></div></div></div><div xml:lang="en-US" class="chapter" id="ch-System_Locale_and_Keyboard_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. System Locale and Keyboard Configuration</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-Setting_the_System_Locale">2.1. Setting the System Locale</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Displaying_the_Current_Status">2.1.1. Displaying the Current Status</a></span></dt><dt><span class="section"><a href="#s2-Listing_Available_Locales">2.1.2. Listing Available Locales</a></span></dt><dt><span class="section"><a href="#s2-Setting_the_Locale">2.1.3. Setting the Locale</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-Changing_the_Keyboard_Layout">2.2. Changing the Keyboard Layout</a></span></dt><dd><dl><dt><span class="sect
ion"><a href="#s2-Displaying_the_Current_Settings">2.2.1. Displaying the Current Settings</a></span></dt><dt><span class="section"><a href="#s2-Listing_Available_Keymaps">2.2.2. Listing Available Keymaps</a></span></dt><dt><span class="section"><a href="#s2-Setting_the_Keymap">2.2.3. Setting the Keymap</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Keyboard_Configuration-Resources">2.3. Additional Resources</a></span></dt></dl></div><a id="idm261761779040" class="indexterm"></a><div class="para">
The <span class="emphasis"><em>system locale</em></span> specifies the language settings of system services and user interfaces. The <span class="emphasis"><em>keyboard layout</em></span> settings control the layout used on the text console and graphical user interfaces.
</div><div class="para">
- These settings can be made by modifying the <code class="filename">/etc/locale.conf</code> configuration file or by using the <span class="application"><strong>localectl</strong></span> utility. Also, you can use the graphical user interface to perform the task; for a description of this method, see <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/">Red Hat Enterprise Linux 7 Installation Guide</a>.
+ These settings can be made by modifying the <code class="filename">/etc/locale.conf</code> configuration file or by using the <span class="application"><strong>localectl</strong></span> utility. Also, you can use the graphical user interface to perform the task; for a description of this method, see <a href="http://docs.fedoraproject.org/install-guide">Fedora Installation Guide</a>.
</div><div class="section" id="s1-Setting_the_System_Locale"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.1. Setting the System Locale</h2></div></div></div><div class="para">
System-wide locale settings are stored in the <code class="filename">/etc/locale.conf</code> file, which is read at early boot by the <code class="systemitem">systemd</code> daemon. The locale settings configured in <code class="filename">/etc/locale.conf</code> are inherited by every service or user, unless individual programs or individual users override them.
</div><div class="para">
@@ -373,7 +373,7 @@ en_BW.utf8
Replace <em class="replaceable"><code>locale</code></em> with the locale name, found with the <code class="command">localectl</code> <code class="option">list-locales</code> command. The above syntax can also be used to configure parameters from <a class="xref" href="#tab-locale_options">Table 2.1, “Options configurable in /etc/locale.conf”</a>.
</div><div class="example"><h6>Example 2.3. Changing the Default Locale</h6><div class="example-contents"><div class="para">
For example, if you want to set British English as your default locale, first find the name of this locale by using <code class="option">list-locales</code>. Then, as <code class="systemitem">root</code>, type the command in the following form:
- </div><pre class="synopsis">~]# <code class="command">localectl</code> <code class="option">set-locale</code> <code class="option">LANG</code>=<code class="literal">en_GB.utf8</code></pre></div></div><br class="example-break" /></div></div><div class="section" id="s1-Changing_the_Keyboard_Layout"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Changing the Keyboard Layout</h2></div></div></div><a id="idm225477297552" class="indexterm"></a><a id="idm225477295952" class="indexterm"></a><div class="para">
+ </div><pre class="synopsis">~]# <code class="command">localectl</code> <code class="option">set-locale</code> <code class="option">LANG</code>=<code class="literal">en_GB.utf8</code></pre></div></div><br class="example-break" /></div></div><div class="section" id="s1-Changing_the_Keyboard_Layout"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Changing the Keyboard Layout</h2></div></div></div><a id="idm261739524224" class="indexterm"></a><a id="idm261739522624" class="indexterm"></a><div class="para">
The keyboard layout settings enable the user to control the layout used on the text console and graphical user interfaces.
</div><div class="section" id="s2-Displaying_the_Current_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.1. Displaying the Current Settings</h3></div></div></div><div class="para">
As mentioned before, you can check your current keyboard layout configuration with the following command:
@@ -421,7 +421,7 @@ sunt5-us-cz
</div><pre class="synopsis"><code class="command">localectl</code> <code class="option">set-x11-keymap</code> <em class="replaceable"><code>map</code></em> <em class="replaceable"><code>model</code></em> <em class="replaceable"><code>variant</code></em> <em class="replaceable"><code>options</code></em></pre><div class="para">
Replace <em class="replaceable"><code>model</code></em> with the keyboard model name, <em class="replaceable"><code>variant</code></em> and <em class="replaceable"><code>options</code></em> with keyboard variant and option components, which can be used to enhance the keyboard behavior. These options are not set by default. For more information on X11 Model, X11 Variant, and X11 Options see the <code class="systemitem">kbd(4)</code> man page.
</div></div></div><div class="section" id="sect-Keyboard_Configuration-Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.3. Additional Resources</h2></div></div></div><div class="para">
- For more information on how to configure the keyboard layout on Red Hat Enterprise Linux, see the resources listed below:
+ For more information on how to configure the keyboard layout on Fedora, see the resources listed below:
</div><h3 id="brid-Keyboard_Configuration-Resources-Installed">Installed Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="systemitem">localectl</code>(1) — The manual page for the <code class="command">localectl</code> command line utility documents how to use this tool to configure the system locale and keyboard layout.
</div></li><li class="listitem"><div class="para">
@@ -479,7 +479,7 @@ NTP synchronized: no
Note that changing the date without specifying the current time results in setting the time to 00:00:00.
</div><div class="example" id="exam-Configuring_the_Date_and_Time-timedatectl-Date"><h6>Example 3.3. Changing the Current Date</h6><div class="example-contents"><div class="para">
To change the current date to 2 June 2013 and keep the current time (11:26 p.m.), run the following command as <code class="systemitem">root</code>:
- </div><pre class="screen">~]# <code class="command">timedatectl set-time 2013-06-02 23:26:00</code></pre></div></div><br class="example-break" /></div><div class="section" id="sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.1.4. Changing the Time Zone</h3></div></div></div><div class="para">
+ </div><pre class="screen">~]# <code class="command">timedatectl set-time "2013-06-02 23:26:00"</code></pre></div></div><br class="example-break" /></div><div class="section" id="sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.1.4. Changing the Time Zone</h3></div></div></div><div class="para">
To list all available time zones, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">timedatectl</code> <code class="option">list-timezones</code></pre><div class="para">
To change the currently used time zone, type as <code class="systemitem">root</code>:
@@ -640,21 +640,23 @@ Tue 15 Apr 2014 04:23:46 PM CEST -0.329272 seconds</pre><div class="para">
<code class="systemitem">hwclock</code>(8) — The manual page for the <code class="command">hwclock</code> command provides a complete list of supported command line options.
</div></li></ul></div><h3 id="brid-Date_and_Time-Resources-Also">See Also</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a class="xref" href="#ch-System_Locale_and_Keyboard_Configuration">Chapter 2, <em>System Locale and Keyboard Configuration</em></a> documents how to configure the keyboard layout.
- </div></li></ul></div></div></div><div xml:lang="en-US" class="chapter" id="ch-Managing_Users_and_Groups" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 4. Managing Users and Groups</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-users-groups-introduction">4.1. Introduction to Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-groups-private-groups">4.1.1. User Private Groups</a></span></dt><dt><span class="section"><a href="#s2-users-groups-shadow-utilities">4.1.2. Shadow Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-configui">4.2. Using the User Manager Tool</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-users-list">4.2.1. Viewing Users and Groups</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-tools">4.3. Using Command Line Tools</a></span></dt><dd><dl><dt><span class="section"><
a href="#s2-users-tools-users-add">4.3.1. Adding a New User</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-add">4.3.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="#s2-users-tools-password-aging">4.3.3. Enabling Password Aging</a></span></dt><dt><span class="section"><a href="#s2-users-tools-users-logout">4.3.4. Enabling Automatic Logouts</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-directories">4.3.5. Creating Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-groups-additional-resources">4.4. Additional Resources</a></span></dt></dl></div><a id="idm225442176592" class="indexterm"></a><a id="idm225438128736" class="indexterm"></a><a id="idm225476423504" class="indexterm"></a><a id="idm225481337984" class="indexterm"></a><div class="para">
- The control of users and groups is a core element of Fedora system administration. This chapter explains how to add, manage, and delete users and groups in the graphical user interface and on the command line, and covers advanced topics, such as enabling password aging or creating group directories.
+ </div></li></ul></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 4. Managing Users and Groups</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-users-groups-introduction">4.1. Introduction to Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-users-groups-private-groups">4.1.1. User Private Groups</a></span></dt><dt><span class="section"><a href="#s2-users-groups-shadow-utilities">4.1.2. Shadow Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-configui">4.2. Managing Users in a Graphical Environment</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-redhat-config-users-list">4.2.1. Using the Users Settings Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-users-tools">4.3. Using Command Line Tools</a></span></dt><dd><dl><dt><spa
n class="section"><a href="#s2-users-tools-users-add">4.3.1. Adding a New User</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-add">4.3.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="#s2-users-tools-password-aging">4.3.3. Enabling Password Aging</a></span></dt><dt><span class="section"><a href="#s2-users-tools-users-logout">4.3.4. Enabling Automatic Logouts</a></span></dt><dt><span class="section"><a href="#s2-users-tools-groups-directories">4.3.5. Creating Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Users_and_Groups-Resources">4.4. Additional Resources</a></span></dt></dl></div><a id="idm261744144416" class="indexterm"></a><a id="idm261784957904" class="indexterm"></a><a id="idm261759483376" class="indexterm"></a><a id="idm261714415616" class="indexterm"></a><div class="para">
+ The control of users and groups is a core element of Fedora system administration. This chapter explains how to add, manage, and delete users and groups in the graphical user interface and on the command line, and covers advanced topics, such as creating group directories.
</div><div class="section" id="s1-users-groups-introduction"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.1. Introduction to Users and Groups</h2></div></div></div><div class="para">
- While users can be either people (meaning accounts tied to physical users) or accounts which exist for specific applications to use, groups are logical expressions of organization, tying users together for a common purpose. Users within a group can read, write, or execute files owned by that group.
+ While users can be either people (meaning accounts tied to physical users) or accounts which exist for specific applications to use, groups are logical expressions of organization, tying users together for a common purpose. Users within a group share the same permissions to read, write, or execute files owned by that group.
</div><div class="para">
Each user is associated with a unique numerical identification number called a <em class="firstterm">user ID</em> (<acronym class="acronym">UID</acronym>). Likewise, each group is associated with a <em class="firstterm">group ID</em> (<acronym class="acronym">GID</acronym>). 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 <code class="systemitem">root</code>, and access permissions can be changed by both the <code class="systemitem">root</code> user and file owner.
</div><div class="para">
- Additionally, Fedora supports <em class="firstterm">access control lists</em> (<acronym class="acronym">ACLs</acronym>) for files and directories which allow permissions for specific users outside of the owner to be set. For more information about this feature, see the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/ch-acls.html"><em class="citetitle">Access Control Lists</em></a> chapter of the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/index.html"><em class="citetitle">Storage Administration Guide</em></a>.
- </div><div class="section" id="s2-users-groups-private-groups"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.1.1. User Private Groups</h3></div></div></div><a id="idm225450767184" class="indexterm"></a><a id="idm225450765744" class="indexterm"></a><a id="idm225461891808" class="indexterm"></a><a id="idm225461889728" class="indexterm"></a><div class="para">
+ Additionally, Fedora supports <em class="firstterm">access control lists</em> (<acronym class="acronym">ACLs</acronym>) for files and directories which allow permissions for specific users outside of the owner to be set. For more information about this feature, see the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Storage_Administration_Guide/ch-acls.html"><em class="citetitle">Access Control Lists</em></a> chapter of the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Storage_Administration_Guide/index.html"><em class="citetitle">Storage Administration Guide</em></a>.
+ </div><div class="section" id="s2-users-groups-private-groups"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.1.1. User Private Groups</h3></div></div></div><a id="idm261756154336" class="indexterm"></a><a id="idm261726720528" class="indexterm"></a><a id="idm261726719088" 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 user private group 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 user private group.
</div><div class="para">
User private groups 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 <span class="quote">“<span class="quote">group protection</span>”</span> is not necessary since every user has their own private group.
- </div></div><div class="section" id="s2-users-groups-shadow-utilities"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.1.2. Shadow Passwords</h3></div></div></div><a id="idm225457159152" class="indexterm"></a><a id="idm225444500272" class="indexterm"></a><div class="para">
+ The setting which determines what permissions are applied to a newly created file or directory is called a <em class="firstterm">umask</em> and is configured in the <code class="filename">/etc/bashrc</code> file. Traditionally on UNIX-based systems, the <code class="command">umask</code> is set to <code class="command">022</code>, which allows only the user who created the file or directory to make modifications. Under this scheme, all other users, <span class="emphasis"><em>including members of the creator's group</em></span>, are not allowed to make any modifications. However, under the UPG scheme, this <span class="quote">“<span class="quote">group protection</span>”</span> is not necessary since every user has their own private group.
+ </div><div class="para">
+ A list of all groups is stored in the <code class="filename">/etc/group</code> configuration file.
+ </div></div><div class="section" id="s2-users-groups-shadow-utilities"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.1.2. Shadow Passwords</h3></div></div></div><a id="idm261758952048" class="indexterm"></a><a id="idm261758950608" class="indexterm"></a><div class="para">
In environments with multiple users, it is very important to use <em class="firstterm">shadow passwords</em> provided by the <span class="package">shadow-utils</span> package to enhance the security of system authentication files. For this reason, the installation program enables shadow passwords by default.
</div><div class="para">
The following is a list of the advantages shadow passwords have over the traditional way of storing passwords on UNIX-based systems:
@@ -665,28 +667,36 @@ Tue 15 Apr 2014 04:23:46 PM CEST -0.329272 seconds</pre><div class="para">
</div></li><li class="listitem"><div class="para">
Shadow passwords allow 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 <span class="package">shadow-utils</span> package work properly whether or not shadow passwords are enabled. However, since password aging information is stored exclusively in the <code class="filename">/etc/shadow</code> file, any commands which create or modify password aging information do not work. The following is a list of utilities and commands that do not work without first enabling shadow passwords:
+ Most utilities provided by the <span class="package">shadow-utils</span> package work properly whether or not shadow passwords are enabled. However, since password aging information is stored exclusively in the <code class="filename">/etc/shadow</code> file, some utilities and commands do not work without first enabling shadow passwords:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- The <code class="command">chage</code> utility.
+ The <code class="command">chage</code> utility for setting password-aging parameters. For details, see the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/chap-Hardening_Your_System_with_Tools_and_Services.html#sec-Password_Security">Password Security</a> section in the <em class="citetitle">Fedora 21 Security Guide</em>.
</div></li><li class="listitem"><div class="para">
- The <code class="command">gpasswd</code> utility.
+ The <code class="command">gpasswd</code> utility for administrating the <code class="filename">/etc/group</code> file.
</div></li><li class="listitem"><div class="para">
- The <code class="command">usermod</code> command with the <code class="option">-e</code> or <code class="option">-f</code> option.
+ The <code class="command">usermod</code> command with the <code class="option">-e, --expiredate</code> or <code class="option">-f, --inactive</code> option.
</div></li><li class="listitem"><div class="para">
- The <code class="command">useradd</code> command with the <code class="option">-e</code> or <code class="option">-f</code> option.
- </div></li></ul></div></div></div><div class="section" id="s1-users-configui"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Using the User Manager Tool</h2></div></div></div><a id="idm225467984768" class="indexterm"></a><a id="idm225447252416" class="indexterm"></a><a id="idm225447250976" class="indexterm"></a><a id="idm225449329056" class="indexterm"></a><a id="idm225449327616" class="indexterm"></a><a id="idm225460514880" class="indexterm"></a><div class="para">
- The <span class="application"><strong>User</strong></span> utility allows you to view, modify, add, and delete local users in the graphical user interface.
- </div><div class="section" id="s2-redhat-config-users-list"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.2.1. Viewing Users and Groups</h3></div></div></div><div class="para">
- Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">Users</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Users</strong></span> utility appears. The <span class="keycap"><strong>Super</strong></span> key appears in a variety of guises, depending on the keyboard and other hardware, but often as either the Windows or Command key, and typically to the left of the Spacebar.
+ The <code class="command">useradd</code> command with the <code class="option">-e, --expiredate</code> or <code class="option">-f, --inactive</code> option.
+ </div></li></ul></div></div></div><div class="section" id="s1-users-configui"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Managing Users in a Graphical Environment</h2></div></div></div><a id="idm261690878144" class="indexterm"></a><a id="idm261758554720" class="indexterm"></a><a id="idm261758553280" class="indexterm"></a><a id="idm261758010144" class="indexterm"></a><a id="idm261758008704" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Users</strong></span> utility allows you to view, modify, add, and delete local users in the graphical user interface.
+ </div><div class="section" id="s2-redhat-config-users-list"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.2.1. Using the Users Settings Tool</h3></div></div></div><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">Users</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Users</strong></span> settings tool appears. The <span class="keycap"><strong>Super</strong></span> key appears in a variety of guises, depending on the keyboard and other hardware, but often as either the Windows or Command key, and typically to the left of the Spacebar.
</div><div class="para">
- To make changes to the user accounts first select the <span class="guibutton"><strong>Unlock</strong></span> button and authenticate yourself as indicated by the dialog box that appears. Note that unless you have superuser privileges, the application will prompt you to authenticate as <code class="systemitem">root</code>. To add and remove users select the <span class="guibutton"><strong>+</strong></span> and <span class="guibutton"><strong>-</strong></span> button respectively. To edit a users language setting, select the language and a drop-down menu appears.
- </div></div></div><div class="section" id="s1-users-tools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. Using Command Line Tools</h2></div></div></div><a id="idm225457358464" class="indexterm"></a><a id="idm225458672544" class="indexterm"></a><a id="idm225468955840" class="indexterm"></a><a id="idm225468953760" class="indexterm"></a><div class="para">
- The easiest way to manage users and groups on Fedora is to use the <span class="application"><strong>User Manager</strong></span> application as described in <a class="xref" href="#s1-users-configui">Section 4.2, “Using the User Manager Tool”</a>. However, if you prefer command line tools or do not have the X Window System installed, you can use command line utilities that are listed in <a class="xref" href="#table-users-tools">Table 4.1, “Command line utilities for managing users and groups”</a>.
+ To make changes to the user accounts, first select the <span class="guibutton"><strong>Unlock</strong></span> button and authenticate yourself as indicated by the dialog box that appears. Note that unless you have superuser privileges, the application will prompt you to authenticate as <code class="systemitem">root</code>. To add and remove users, select the <span class="guibutton"><strong>+</strong></span> and <span class="guibutton"><strong>-</strong></span> button respectively. To add a user to the administrative group <code class="systemitem">wheel</code>, change the <span class="guimenu"><strong>Account Type</strong></span> from <code class="literal">Standard</code> to <code class="literal">Administrator</code>. To edit a user's language setting, select the language and a drop-down menu appears.
+ </div><div class="figure" id="fig-managing-users"><div class="figure-contents"><div class="mediaobject" id="mediaobj-managing-users"><img src="images/managing_users.png" alt="The Users Settings Tool" /><div class="longdesc"><div class="para">
+ The <span class="application"><strong>Users</strong></span> settings tool
+ </div></div></div></div><h6>Figure 4.1. The Users Settings Tool</h6></div><br class="figure-break" /><div class="para">
+ When a new user is created, the account is disabled until a password is set. The <span class="guimenu"><strong>Add User</strong></span> menu contains the options to set a password by the administrator immediately, or to allow the user to choose a password at the first login.
+ </div></div></div><div class="section" id="s1-users-tools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.3. Using Command Line Tools</h2></div></div></div><a id="idm261713058272" class="indexterm"></a><a id="idm261754166384" class="indexterm"></a><a id="idm261785583504" class="indexterm"></a><div class="para">
+ Apart from the <span class="application"><strong>Users</strong></span> settings tool described in <a class="xref" href="#s1-users-configui">Section 4.2, “Managing Users in a Graphical Environment”</a>, which is designed for basic managing of users, you can use command line tools for managing users and groups that are listed in <a class="xref" href="#table-users-tools">Table 4.1, “Command line utilities for managing users and groups”</a>.
</div><div class="table" id="table-users-tools"><h6>Table 4.1. Command line utilities for managing users and groups</h6><div class="table-contents"><table summary="Command line utilities for managing users and groups" border="1"><colgroup><col width="35%" class="utilities" /><col width="65%" class="description" /></colgroup><thead><tr><th class="">
Utilities
</th><th class="">
Description
</th></tr></thead><tbody><tr><td class="">
+ <code class="command">id</code>
+ </td><td class="">
+ Displays user and group IDs.
+ </td></tr><tr><td class="">
<code class="command">useradd</code>, <code class="command">usermod</code>, <code class="command">userdel</code>
</td><td class="">
Standard utilities for adding, modifying, and deleting user accounts.
@@ -706,15 +716,19 @@ Tue 15 Apr 2014 04:23:46 PM CEST -0.329272 seconds</pre><div class="para">
<code class="command">pwconv</code>, <code class="command">pwunconv</code>
</td><td class="">
Utilities that can be used for the conversion of passwords to shadow passwords, or back from shadow passwords to standard passwords.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="s2-users-tools-users-add"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.1. Adding a New User</h3></div></div></div><a id="idm225461203296" class="indexterm"></a><a id="idm225357047776" class="indexterm"></a><a id="idm225357046336" class="indexterm"></a><div class="para">
- To add a new user to the system, typing the following at a shell prompt as <code class="systemitem">root</code>:
+ </td></tr><tr><td class="">
+ <code class="command">grpconv</code>, <code class="command">grpunconv</code>
+ </td><td class="">
+ Similar to the previous, these utilities can be used for conversion of shadowed information for group accounts.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="s2-users-tools-users-add"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.1. Adding a New User</h3></div></div></div><a id="idm261715016816" class="indexterm"></a><a id="idm261715015088" class="indexterm"></a><a id="idm261752310912" class="indexterm"></a><div class="para">
+ To add a new user to the system, type the following at a shell prompt as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">useradd</code> [<span class="optional"><em class="replaceable"><code>options</code></em></span>] <em class="replaceable"><code>username</code></em></pre><div class="para">
- …where <em class="replaceable"><code>options</code></em> are command line options as described in <a class="xref" href="#table-useradd-options">Table 4.2, “useradd command line options”</a>.
- </div><a id="idm225500704768" class="indexterm"></a><div class="para">
+ …where <em class="replaceable"><code>options</code></em> are command-line options as described in <a class="xref" href="#table-useradd-options">Table 4.2, “Common useradd command-line options”</a>.
+ </div><a id="idm261716158256" class="indexterm"></a><div class="para">
By default, the <code class="command">useradd</code> command creates a locked user account. To unlock the account, run the following command as <code class="systemitem">root</code> to assign a password:
</div><pre class="synopsis"><code class="command">passwd</code> <em class="replaceable"><code>username</code></em></pre><div class="para">
- Optionally, you can set password aging policy. See <a class="xref" href="#s2-users-tools-password-aging">Section 4.3.3, “Enabling Password Aging”</a> for information on how to enable password aging.
- </div><div class="table" id="table-useradd-options"><h6>Table 4.2. useradd command line options</h6><div class="table-contents"><table summary="useradd command line options" border="1"><colgroup><col width="30%" class="option" /><col width="70%" class="description" /></colgroup><thead><tr><th class="">
+ Optionally, you can set a password aging policy. See <a class="xref" href="#s2-users-tools-password-aging">Section 4.3.3, “Enabling Password Aging”</a> for information on how to enable password aging.
+ </div><div class="table" id="table-useradd-options"><h6>Table 4.2. Common useradd command-line options</h6><div class="table-contents"><table summary="Common useradd command-line options" border="1"><colgroup><col width="30%" class="option" /><col width="70%" class="description" /></colgroup><thead><tr><th class="">
Option
</th><th class="">
Description
@@ -733,15 +747,15 @@ Tue 15 Apr 2014 04:23:46 PM CEST -0.329272 seconds</pre><div class="para">
</td></tr><tr><td class="">
<code class="option">-f</code> <em class="replaceable"><code>days</code></em>
</td><td class="">
- Number of days after the password expires until the account is disabled. If <code class="literal">0</code> is specified, the account is disabled immediately after the password expires. If <code class="literal">-1</code> is specified, the account is not be disabled after the password expires.
+ Number of days after the password expires until the account is disabled. If <code class="literal">0</code> is specified, the account is disabled immediately after the password expires. If <code class="literal">-1</code> is specified, the account is not disabled after the password expires.
</td></tr><tr><td class="">
<code class="option">-g</code> <em class="replaceable"><code>group_name</code></em>
</td><td class="">
- Group name or group number for the user's default group. The group must exist prior to being specified here.
+ Group name or group number for the user's default (primary) group. The group must exist prior to being specified here.
</td></tr><tr><td class="">
<code class="option">-G</code> <em class="replaceable"><code>group_list</code></em>
</td><td class="">
- List of additional (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.
+ List of additional (supplementary, other than default) group names or group numbers, separated by commas, of which the user is a member. The groups must exist prior to being specified here.
</td></tr><tr><td class="">
<code class="option">-m</code>
</td><td class="">
@@ -770,7 +784,9 @@ Tue 15 Apr 2014 04:23:46 PM CEST -0.329272 seconds</pre><div class="para">
<code class="option">-u</code> <em class="replaceable"><code>uid</code></em>
</td><td class="">
User ID for the user, which must be unique and greater than 999.
- </td></tr></tbody></table></div></div><br class="table-break" /><h4 id="bh-users-tools-users-add-explanation"> Explaining the Process </h4><div class="para">
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The command-line options associated with the <code class="command">usermod</code> command are essentially the same. Note that if you want to add a user to another supplementary group, you need to use the <code class="option">-a, --append</code> option with the <code class="option">-G</code> option. Otherwise the list of supplementary groups for the user will be overwritten by those specified with the <code class="command">usermod -G</code> command.
+ </div><h4 id="bh-users-tools-users-add-explanation"> Explaining the Process </h4><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>:
@@ -813,7 +829,7 @@ Tue 15 Apr 2014 04:23:46 PM CEST -0.329272 seconds</pre><div class="para">
</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>.
+ The GID matches the one listed for <code class="systemitem">juan</code>'s primary group in <code class="filename">/etc/passwd</code>.
</div></li></ul></div></li><li class="step"><div class="para">
A new line for a group named <code class="systemitem">juan</code> is created in <code class="filename">/etc/gshadow</code>:
</div><pre class="programlisting">juan:!::</pre><div class="para">
@@ -826,27 +842,25 @@ Tue 15 Apr 2014 04:23:46 PM CEST -0.329272 seconds</pre><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">
+ </div><pre class="screen">~]# <code class="command">ls -ld /home/juan</code>
+drwx------. 4 juan juan 4096 Mar 3 18:23 /home/juan</pre><div class="para">
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. The contents of <code class="filename">/etc/skel/</code> may vary depending on installed applications.
+ The files within the <code class="filename">/etc/skel/</code> directory (which contain default user settings) are copied into the new <code class="filename">/home/juan/</code> directory. The contents of <code class="filename">/etc/skel/</code> may vary depending on installed applications:
</div><pre class="screen">~]# <code class="command">ls -la /home/juan</code>
-total 28
+total 24
drwx------. 4 juan juan 4096 Mar 3 18:23 .
drwxr-xr-x. 5 root root 4096 Mar 3 18:23 ..
-rw-r--r--. 1 juan juan 18 Jul 09 08:43 .bash_logout
-rw-r--r--. 1 juan juan 176 Jul 09 08:43 .bash_profile
-rw-r--r--. 1 juan juan 124 Jul 09 08:43 .bashrc
-drwxr-xr-x. 4 juan juan 4096 Jul 09 08:43 .mozilla
--rw-r--r--. 1 juan juan 658 Jul 09 08:43 .zshrc</pre></li></ol></div><div class="para">
+drwxr-xr-x. 4 juan juan 4096 Jul 09 08:43 .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 class="section" id="s2-users-tools-groups-add"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.2. Adding a New Group</h3></div></div></div><a id="idm225475021680" class="indexterm"></a><a id="idm225477553680" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-users-tools-groups-add"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.2. Adding a New Group</h3></div></div></div><a id="idm261756048416" class="indexterm"></a><a id="idm261745807136" class="indexterm"></a><div class="para">
To add a new group to the system, type the following at a shell prompt as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">groupadd</code> [<span class="optional"><em class="replaceable"><code>options</code></em></span>] <em class="replaceable"><code>group_name</code></em></pre><div class="para">
- …where <em class="replaceable"><code>options</code></em> are command line options as described in <a class="xref" href="#table-groupadd-options">Table 4.3, “groupadd command line options”</a>.
- </div><div class="table" id="table-groupadd-options"><h6>Table 4.3. groupadd command line options</h6><div class="table-contents"><table summary="groupadd command line options" border="1"><colgroup><col width="30%" class="option" /><col width="70%" class="description" /></colgroup><thead><tr><th class="">
+ …where <em class="replaceable"><code>options</code></em> are command-line options as described in <a class="xref" href="#table-groupadd-options">Table 4.3, “Common groupadd command-line options”</a>.
+ </div><div class="table" id="table-groupadd-options"><h6>Table 4.3. Common groupadd command-line options</h6><div class="table-contents"><table summary="Common groupadd command-line options" border="1"><colgroup><col width="30%" class="option" /><col width="70%" class="description" /></colgroup><thead><tr><th class="">
Option
</th><th class="">
Description
@@ -874,11 +888,11 @@ drwxr-xr-x. 4 juan juan 4096 Jul 09 08:43 .mozilla
<code class="option">-r</code>
</td><td class="">
Create a system group with a GID less than 1000.
- </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="s2-users-tools-password-aging"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.3. Enabling Password Aging</h3></div></div></div><a id="idm225467591872" class="indexterm"></a><a id="idm225468068288" class="indexterm"></a><a id="idm225468066848" class="indexterm"></a><a id="idm225468065920" class="indexterm"></a><a id="idm225464306784" class="indexterm"></a><div class="para">
- For security reasons, it is advisable to require users to change their passwords periodically. This can either 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> application, or by using the <code class="command">chage</code> command.
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="s2-users-tools-password-aging"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.3. Enabling Password Aging</h3></div></div></div><a id="idm261756300880" class="indexterm"></a><a id="idm261745189520" class="indexterm"></a><a id="idm261745188080" class="indexterm"></a><a id="idm261745187152" class="indexterm"></a><a id="idm261745993920" class="indexterm"></a><div class="para">
+ For security reasons, it is advisable to require users to change their passwords periodically. This can be done by using the <code class="command">chage</code> command.
</div><div class="important"><div class="admonition_header"><h2>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="#s2-users-groups-shadow-utilities">Section 4.1.2, “Shadow Passwords”</a>.
- </div></div></div><a id="idm225446669744" class="indexterm"></a><div class="para">
+ </div></div></div><a id="idm261737121312" class="indexterm"></a><div class="para">
To configure password expiration for a user from a shell prompt, run the following command as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">chage</code> [<span class="optional"><em class="replaceable"><code>options</code></em></span>] <em class="replaceable"><code>username</code></em></pre><div class="para">
…where <em class="replaceable"><code>options</code></em> are command line options as described in <a class="xref" href="#table-chage-options">Table 4.4, “chage command line options”</a>. When the <code class="command">chage</code> command is followed directly by a username (that is, when no command line options are specified), it displays the current password aging values and allows you to change them interactively.
@@ -960,8 +974,8 @@ autodetach off</pre><div class="para">
This way, a password will be required to unlock the session.
</div></li></ol></div><div class="para">
The changes take effect the next time a user logs in to the system.
- </div></div><div class="section" id="s2-users-tools-groups-directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.5. Creating Group Directories</h3></div></div></div><a id="idm225493033136" class="indexterm"></a><a id="idm225493031696" 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><div class="section" id="s2-users-tools-groups-directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.5. Creating Group Directories</h3></div></div></div><a id="idm261752899808" class="indexterm"></a><a id="idm261754921408" class="indexterm"></a><div class="para">
+ System administrators usually like to create a group for each major project and assign people to the group when they need to access that project's files. With this traditional scheme, file management is difficult; when someone creates a file, it is associated with the primary group to which they belong. When a single person works on multiple projects, it becomes difficult to associate the right files with the right group. However, with the UPG scheme, groups are automatically assigned to files created within a directory with the <em class="firstterm">setgid</em> bit set. The setgid bit makes managing group projects that share a common directory very simple because any files a user creates within the directory are owned by the group that owns the directory.
</div><div class="para">
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">
@@ -971,14 +985,16 @@ autodetach off</pre><div class="para">
</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-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.4. Additional Resources</h2></div></div></div><a id="idm225469288640" class="indexterm"></a><a id="idm225461851856" class="indexterm"></a><div class="para">
+ Allow users in the group to create files within the directory and set the setgid bit:
+ </div><pre class="screen"><code class="command">chmod 2775 /opt/myproject</code></pre><div class="para">
+ 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 -ld /opt/myproject</code>
+drwxrwsr-x. 3 root myproject 4096 Mar 3 18:31 /opt/myproject
+</pre></li><li class="step"><div class="para">
+ Add users to the <code class="systemitem">myproject</code> group:
+ </div><pre class="screen"><code class="command">usermod -aG myproject <em class="replaceable"><code>username</code></em></code></pre></li></ol></div></div></div><div class="section" id="sect-Users_and_Groups-Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.4. Additional Resources</h2></div></div></div><a id="idm261733381632" class="indexterm"></a><a id="idm261733380192" class="indexterm"></a><div class="para">
For more information on how to manage users and groups on Fedora, see the resources listed below.
- </div><h3 id="sect-Users_and_Groups-Resources-Installed">Installed Documentation</h3><a id="idm225506785872" class="indexterm"></a><a id="idm225506783952" class="indexterm"></a><div class="para">
+ </div><h3 id="sect-Users_and_Groups-Resources-Installed">Installed Documentation</h3><a id="idm261718051792" class="indexterm"></a><a id="idm261714522400" class="indexterm"></a><div class="para">
For information about various utilities for managing users and groups, see the following manual pages:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="systemitem">useradd</code>(8) — The manual page for the <code class="command">useradd</code> command documents how to use it to create new users.
@@ -999,9 +1015,9 @@ drwxrwsr-x. 3 root myproject 4096 Mar 3 18:31 myproject</pre></div></div><div c
</div></li><li class="listitem"><div class="para">
<code class="systemitem">pwck</code>(8) — The manual page for the <code class="command">pwck</code> command documents how to use it to verify the integrity of the <code class="filename">/etc/passwd</code> and <code class="filename">/etc/shadow</code> files.
</div></li><li class="listitem"><div class="para">
- <code class="systemitem">pwconv</code>(8) — The manual page for the <code class="command">pwconv</code> command documents how to use it to convert standard passwords to shadow passwords.
+ <code class="systemitem">pwconv</code>(8) — The manual page for the <code class="command">pwconv</code>, <code class="command">pwunconv</code>, <code class="command">grpconv</code>, and <code class="command">grpunconv</code> commands documents how to convert shadowed information for passwords and groups.
</div></li><li class="listitem"><div class="para">
- <code class="systemitem">pwunconv</code>(8) — The manual page for the <code class="command">pwunconv</code> command documents how to use it to convert shadow passwords to standard passwords.
+ <code class="systemitem">id</code>(1) — The manual page for the <code class="command">id</code> command documents how to display user and group IDs.
</div></li></ul></div><div class="para">
For information about related configuration files, see:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
@@ -1010,19 +1026,19 @@ drwxrwsr-x. 3 root myproject 4096 Mar 3 18:31 myproject</pre></div></div><div c
<code class="systemitem">passwd</code>(5) — The manual page for the <code class="filename">/etc/passwd</code> file documents how to use this file to define user information.
</div></li><li class="listitem"><div class="para">
<code class="systemitem">shadow</code>(5) — The manual page for the <code class="filename">/etc/shadow</code> file documents how to use this file to set passwords and account expiration information for the system.
- </div></li></ul></div></div></div></div><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="idm225465138208"><div></div><div class="para">
+ </div></li></ul></div></div></div></div><div class="part" id="part-Package_Management"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part II. Package Management</h1></div></div></div><div class="partintro" id="idm261787231824"><div></div><div class="para">
All software on a Fedora system is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages on Fedora using <span class="application"><strong>Yum</strong></span>.
</div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#ch-yum">5. Yum</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_For_and_Updating_Packages">5.1. Checking For and Updating Packages</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_For_Updates">5.1.1. Checking For Updates</a></span></dt><dt><span class="section"><a href="#sec-Updating_Packages">5.1.2. Updating Packages</a></span></dt><dt><span class="section"><a href="#sec-Preserving_Configuration_File_Changes">5.1.3. Preserving Configuration File Changes</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Packages_and_Package_Groups">5.2. Packages and Package Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Searching_Packages">5.2.1. Searching Packages</a></span></dt><dt><span class="section"><a href="#sec-Listing_Packages">5.2.2. Listing Packages</a></span></dt><dt><span class="
section"><a href="#sec-Displaying_Package_Information">5.2.3. Displaying Package Information</a></span></dt><dt><span class="section"><a href="#sec-Installing">5.2.4. Installing Packages</a></span></dt><dt><span class="section"><a href="#sec-Removing">5.2.5. Removing Packages</a></span></dt><dt><span class="section"><a href="#sec-Yum-Transaction_History">5.2.6. Working with Transaction History</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Yum_and_Yum_Repositories">5.3. Configuring Yum and Yum Repositories</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_main_Options">5.3.1. Setting [main] Options</a></span></dt><dt><span class="section"><a href="#sec-Setting_repository_Options">5.3.2. Setting [repository] Options</a></span></dt><dt><span class="section"><a href="#sec-Using_Yum_Variables">5.3.3. Using Yum Variables</a></span></dt><dt><span class="section"><a href="#sec-Viewing_the_Current_Configuration">5.3.4. Viewing the C
urrent Configuration</a></span></dt><dt><span class="section"><a href="#sec-Managing_Yum_Repositories">5.3.5. Adding, Enabling, and Disabling a Yum Repository</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Yum_Repository">5.3.6. Creating a Yum Repository</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Yum_Plugins">5.4. Yum Plug-ins</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">5.4.1. Enabling, Configuring, and Disabling Yum Plug-ins</a></span></dt><dt><span class="section"><a href="#sec-Installing_More_Yum_Plugins">5.4.2. Installing Additional Yum Plug-ins</a></span></dt><dt><span class="section"><a href="#sec-Plugin_Descriptions">5.4.3. Plug-in Descriptions</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Additional_Resources">5.5. Additional Resources</a></span></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" id="ch-yum" lang="en-US"><di
v class="titlepage"><div><div><h2 class="title">Chapter 5. Yum</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sec-Checking_For_and_Updating_Packages">5.1. Checking For and Updating Packages</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_For_Updates">5.1.1. Checking For Updates</a></span></dt><dt><span class="section"><a href="#sec-Updating_Packages">5.1.2. Updating Packages</a></span></dt><dt><span class="section"><a href="#sec-Preserving_Configuration_File_Changes">5.1.3. Preserving Configuration File Changes</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Packages_and_Package_Groups">5.2. Packages and Package Groups</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Searching_Packages">5.2.1. Searching Packages</a></span></dt><dt><span class="section"><a href="#sec-Listing_Packages">5.2.2. Listing Packages</a></span></dt><dt><span class="section"><a href="#sec-Displaying_Pac
kage_Information">5.2.3. Displaying Package Information</a></span></dt><dt><span class="section"><a href="#sec-Installing">5.2.4. Installing Packages</a></span></dt><dt><span class="section"><a href="#sec-Removing">5.2.5. Removing Packages</a></span></dt><dt><span class="section"><a href="#sec-Yum-Transaction_History">5.2.6. Working with Transaction History</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Configuring_Yum_and_Yum_Repositories">5.3. Configuring Yum and Yum Repositories</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_main_Options">5.3.1. Setting [main] Options</a></span></dt><dt><span class="section"><a href="#sec-Setting_repository_Options">5.3.2. Setting [repository] Options</a></span></dt><dt><span class="section"><a href="#sec-Using_Yum_Variables">5.3.3. Using Yum Variables</a></span></dt><dt><span class="section"><a href="#sec-Viewing_the_Current_Configuration">5.3.4. Viewing the Current Configuration</a></span></dt><
dt><span class="section"><a href="#sec-Managing_Yum_Repositories">5.3.5. Adding, Enabling, and Disabling a Yum Repository</a></span></dt><dt><span class="section"><a href="#sec-Creating_a_Yum_Repository">5.3.6. Creating a Yum Repository</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Yum_Plugins">5.4. Yum Plug-ins</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">5.4.1. Enabling, Configuring, and Disabling Yum Plug-ins</a></span></dt><dt><span class="section"><a href="#sec-Installing_More_Yum_Plugins">5.4.2. Installing Additional Yum Plug-ins</a></span></dt><dt><span class="section"><a href="#sec-Plugin_Descriptions">5.4.3. Plug-in Descriptions</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Additional_Resources">5.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. Yum 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. Yum can be configured with new, additional repositories, or <em class="firstterm">package sources</em>, and also provides many plug-ins which enhance and extend its capabilities. Yum is able to perform many of the same tasks that <span class="application"><strong>RPM</strong></span> can; additionally, many of the command line options are similar. Yum 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">
- Yum 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, Yum will refuse to install any packages not GPG-signed with the correct key for that repository. This means that you can trust that the <span class="application"><strong>RPM</strong></span> packages you download and install on your system are from a trusted source, such as The Fedora Project, and were not modified during transfer. See <a class="xref" href="#sec-Configuring_Yum_and_Yum_Repositories">Section 5.3, “Configuring Yum and Yum Repositories”</a> for details on enabling signature-checking with Yum, or <a class="xref" href="#s1-check-rpm-sig">Section A.3, “Checking a Package's Signature”</a> for information on working with and verifying GPG-signed <span class="application"><stro
ng>RPM</strong></span> packages in general.
+ Yum 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, Yum will refuse to install any packages not GPG-signed with the correct key for that repository. This means that you can trust that the <span class="application"><strong>RPM</strong></span> packages you download and install on your system are from a trusted source, such as The Fedora Project, and were not modified during transfer. See <a class="xref" href="#sec-Configuring_Yum_and_Yum_Repositories">Section 5.3, “Configuring Yum and Yum Repositories”</a> for details on enabling signature-checking with Yum, or <a class="xref" href="#s1-check-rpm-sig">Section A.3.2, “Checking Package Signatures”</a> for information on working with and verifying GPG-signed <span class="application"><stron
g>RPM</strong></span> packages in general.
</div></div></div><div class="para">
Yum 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 Yum is a worthwhile investment because it is often the fastest way to perform system administration tasks, and it provides capabilities beyond those provided by the <span class="application"><strong>PackageKit</strong></span> graphical package management tools.
</div><div class="note" id="note-Note_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">5.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">5.1.1. Checking For Updates</h3></div></div></div><a id="idm225468219440" class="indexterm"></a><div class="para">
+ </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">5.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">5.1.1. Checking For Updates</h3></div></div></div><a id="idm261755626176" class="indexterm"></a><div class="para">
To see which installed packages on your system have updates available, use the following command:
</div><pre class="synopsis"><code class="command">yum</code> <code class="option">check-update</code></pre><div class="para">
For example:
@@ -1055,9 +1071,9 @@ yum.noarch 3.2.29-5.fc15 fedora</pre><
<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 kernel package), Yum 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">kernel-firmware</span>, <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">5.1.2. Updating Packages</h3></div></div></div><a id="idm225449381120" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="sec-Updating_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.1.2. Updating Packages</h3></div></div></div><a id="idm261650627072" class="indexterm"></a><div class="para">
You can choose to update a single package, multiple packages, or all packages at once. If any dependencies of the package (or packages) you update have updates available themselves, then they are updated too.
- </div><h4 id="bh-Updating_a_Single_Package"> Updating a Single Package </h4><a id="idm225448704560" class="indexterm"></a><div class="para">
+ </div><h4 id="bh-Updating_a_Single_Package"> Updating a Single Package </h4><a id="idm261723357664" class="indexterm"></a><div class="para">
To update a single package, run the following command as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">yum</code> <code class="option">update</code> <em class="replaceable"><code>package_name</code></em></pre><div class="para">
For example, to update the <span class="package">udev</span> package, type:
@@ -1098,14 +1114,14 @@ Is this ok [y/N]:</pre><div class="para">
</div></li></ol></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). See <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 id="bh-Updating_All_Packages_and_Their_Dependencies"> Updating All Packages and Their Dependencies </h4><a id="idm225402990224" class="indexterm"></a><div class="para">
+ When using <span class="application"><strong>RPM</strong></span>, on the other hand, it is important to use the <code class="command">rpm -i kernel</code> command (which installs a new kernel) instead of <code class="command">rpm -u kernel</code> (which <span class="emphasis"><em>replaces</em></span> the current kernel). See <a class="xref" href="#sec-Installing_and_Upgrading">Section A.2.1, “Installing and Upgrading Packages”</a> for more information on installing/updating kernels with <span class="application"><strong>RPM</strong></span>.
+ </div></div></div><h4 id="bh-Updating_All_Packages_and_Their_Dependencies"> Updating All Packages and Their Dependencies </h4><a id="idm261778821984" class="indexterm"></a><div class="para">
To update all packages and their dependencies, simply enter <code class="command">yum update</code> (without any arguments):
- </div><pre class="screen"><code class="command">yum update</code></pre><h4 id="bh-Updating_Security-Related_Packages"> Updating Security-Related Packages </h4><a id="idm225463670816" class="indexterm"></a><a id="idm225463669408" class="indexterm"></a><a id="idm225478801744" class="indexterm"></a><div class="para">
+ </div><pre class="screen"><code class="command">yum update</code></pre><h4 id="bh-Updating_Security-Related_Packages"> Updating Security-Related Packages </h4><a id="idm261756083104" class="indexterm"></a><a id="idm261725078480" class="indexterm"></a><a id="idm261725077104" class="indexterm"></a><div class="para">
Discovering which packages have security updates available and then updating those packages quickly and easily is important. Yum provides the plug-in for this purpose. The <span class="application"><strong>security</strong></span> plug-in extends the <code class="command">yum</code> command with a set of highly-useful security-centric commands, subcommands and options. See <a class="xref" href="#sec-Plugin_Descriptions">Section 5.4.3, “Plug-in 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">5.1.3. Preserving Configuration File Changes</h3></div></div></div><a id="idm225500352576" 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 Yum uses to perform changes to the system, provides a mechanism for ensuring their integrity. See <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">5.2. Packages and Package Groups</h2></div></div></div><a id="idm225449588672" class="indexterm"></a><a id="idm225462887216" class="indexterm"></a><div class="section" id="sec-Searching_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.1. Searching Packages</h3></div></div></div><a id="idm225435992272" class="indexterm"></a><a id="idm225435990384" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="sec-Preserving_Configuration_File_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.1.3. Preserving Configuration File Changes</h3></div></div></div><a id="idm261724826896" 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 Yum uses to perform changes to the system, provides a mechanism for ensuring their integrity. See <a class="xref" href="#sec-Installing_and_Upgrading">Section A.2.1, “Installing and Upgrading Packages”</a> for details on how to manage changes to configuration files across package upgrades.
+ </div></div></div><div class="section" id="sec-Packages_and_Package_Groups"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.2. Packages and Package Groups</h2></div></div></div><a id="idm261732261072" class="indexterm"></a><a id="idm261732259664" class="indexterm"></a><div class="section" id="sec-Searching_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.1. Searching Packages</h3></div></div></div><a id="idm261740693680" class="indexterm"></a><a id="idm261749932240" class="indexterm"></a><div class="para">
You can search all <acronym class="acronym">RPM</acronym> package names, descriptions and summaries by using the following command:
</div><pre class="synopsis"><code class="command">yum</code> <code class="option">search</code> <em class="replaceable"><code>term</code></em>…</pre><div class="para">
This command displays the list of matches for each term. For example, to list all packages that match <span class="quote">“<span class="quote">meld</span>”</span> or <span class="quote">“<span class="quote">kompare</span>”</span>, type:
@@ -1118,13 +1134,13 @@ python-meld3.x86_64 : HTML/XML templating system for Python
============================= N/S Matched: kompare =============================
komparator.x86_64 : Kompare and merge two folders
- Name and summary matches only, use "search all" for everything.</pre><a id="idm225464948880" class="indexterm"></a><a id="idm225464946992" class="indexterm"></a><div class="para">
+ Name and summary matches only, use "search all" for everything.</pre><a id="idm261782495824" class="indexterm"></a><a id="idm261781729104" class="indexterm"></a><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">5.2.2. Listing Packages</h3></div></div></div><a id="idm225457196944" class="indexterm"></a><a id="idm225471583888" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="sec-Listing_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.2. Listing Packages</h3></div></div></div><a id="idm261750517680" class="indexterm"></a><a id="idm261750515792" 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 Yum'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="idm225437737872" class="indexterm"></a><a id="idm225437735984" class="indexterm"></a><div class="para">
+ </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="idm261725161488" class="indexterm"></a><a id="idm261691073744" 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
@@ -1147,8 +1163,8 @@ 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="idm225464341120" class="indexterm"></a>
- <a id="idm225462512912" class="indexterm"></a>
+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="idm261729439408" class="indexterm"></a>
+ <a id="idm261729437520" 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 5.2. Listing all installed and available packages</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum list all</code>
@@ -1164,8 +1180,8 @@ 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="idm225416314752" class="indexterm"></a>
- <a id="idm225436211872" class="indexterm"></a>
+<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="idm261721711840" class="indexterm"></a>
+ <a id="idm261721709952" 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 5.3. Listing installed packages using a double-quoted glob expression</h6><div class="example-contents"><div class="para">
@@ -1173,8 +1189,8 @@ NetworkManager-openconnect.x86_64 0.8.1-9.git20110419.fc15 @fedora
</div><pre class="screen">~]# <code class="command">yum list installed "krb?-*"</code>
Loaded plugins: langpacks, presto, refresh-packagekit
Installed Packages
-krb5-libs.x86_64 1.9-7.fc15 @fedora</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225407391056" class="indexterm"></a>
- <a id="idm225458855712" class="indexterm"></a>
+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="idm261725675840" class="indexterm"></a>
+ <a id="idm261725673952" 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 5.4. Listing available packages using a single glob expression with escaped wildcard characters</h6><div class="example-contents"><div class="para">
@@ -1194,8 +1210,8 @@ 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="idm225474658720" class="indexterm"></a>
- <a id="idm225474656832" class="indexterm"></a>
+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="idm261758095936" class="indexterm"></a>
+ <a id="idm261758094048" 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 5.5. Listing all package groups</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum grouplist</code>
@@ -1207,8 +1223,8 @@ Installed Groups:
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="idm225439154784" class="indexterm"></a>
- <a id="idm225446931008" class="indexterm"></a>
+<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="idm261760845904" class="indexterm"></a>
+ <a id="idm261760844016" 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 5.6. Listing enabled repositories</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum repolist</code>
@@ -1216,7 +1232,7 @@ 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">5.2.3. Displaying Package Information</h3></div></div></div><a id="idm225501736160" class="indexterm"></a><a id="idm225503116976" class="indexterm"></a><div class="para">
+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">5.2.3. Displaying Package Information</h3></div></div></div><a id="idm261747920272" class="indexterm"></a><a id="idm261726789008" class="indexterm"></a><div class="para">
To display information about one or more packages (glob expressions are valid here as well), use the following command:
</div><pre class="synopsis"><code class="command">yum</code> <code class="option">info</code> <em class="replaceable"><code>package_name</code></em>…</pre><div class="para">
For example, to display information about the <span class="package">abrt</span> package, type:
@@ -1235,7 +1251,7 @@ URL : https://fedorahosted.org/abrt/
License : GPLv2+
Description : abrt is a tool to help users to detect defects in applications and
: to create a bug report with all informations needed by maintainer
- : to fix it. It uses plugin system to extend its functionality.</pre><a id="idm225477462512" class="indexterm"></a><a id="idm225477460592" class="indexterm"></a><div class="para">
+ : to fix it. It uses plugin system to extend its functionality.</pre><a id="idm261712886656" class="indexterm"></a><a id="idm261735318224" class="indexterm"></a><div class="para">
The <code class="command">yum info <em class="replaceable"><code>package_name</code></em></code> command is similar to the <code class="command">rpm -q --info <em class="replaceable"><code>package_name</code></em></code> command, but provides as additional information the ID of the Yum repository the RPM package is found in (look for the <code class="computeroutput">From repo:</code> line in the output).
</div><div class="para">
You can also query the Yum database for alternative and useful information about a package by using the following command:
@@ -1253,7 +1269,7 @@ yum-3.2.29-4.fc15.noarch
reason = user
releasever = $releasever</pre><div class="para">
For more information on the <code class="command">yumdb</code> command, refer to the <span class="bold bold"><strong>yumdb</strong></span>(8) manual page.
- </div></div><div class="section" id="sec-Installing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.4. Installing Packages</h3></div></div></div><a id="idm225462462320" class="indexterm"></a><a id="idm225446975072" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="sec-Installing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.4. Installing Packages</h3></div></div></div><a id="idm261737945968" class="indexterm"></a><a id="idm261737944528" class="indexterm"></a><div class="para">
Yum allows you to install both a single package and multiple packages, as well as a package group of your choice.
</div><h4 id="bh-Installing_Individual_packages"> Installing Individual Packages </h4><div class="para">
To install a single package and all of its non-installed dependencies, enter a command in the following form:
@@ -1277,7 +1293,7 @@ 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 id="bh-Installing_a_Package_Group"> Installing a Package Group </h4><a id="idm225438693104" class="indexterm"></a><a id="idm225438691696" class="indexterm"></a><div class="para">
+ </div></div></div><h4 id="bh-Installing_a_Package_Group"> Installing a Package Group </h4><a id="idm261756437568" class="indexterm"></a><a id="idm261740665072" 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
@@ -1304,9 +1320,9 @@ Done</pre><div class="para">
For example, the following are alternative but equivalent ways of installing the <code class="literal">KDE Desktop</code> group:
</div><pre class="screen">~]# <code class="command">yum groupinstall "KDE Desktop"</code>
~]# <code class="command">yum groupinstall kde-desktop</code>
-~]# <code class="command">yum install @kde-desktop</code></pre></div><div class="section" id="sec-Removing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.5. Removing Packages</h3></div></div></div><a id="idm225435536480" class="indexterm"></a><a id="idm225435535072" class="indexterm"></a><div class="para">
+~]# <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">5.2.5. Removing Packages</h3></div></div></div><a id="idm261715477488" class="indexterm"></a><a id="idm261715476080" class="indexterm"></a><div class="para">
Similarly to package installation, Yum allows you to uninstall (remove in <span class="application"><strong>RPM</strong></span> and Yum terminology) both individual packages and a package group.
- </div><h4 id="bh-Removing_Individual_Packages"> Removing Individual Packages </h4><a id="idm225480995136" class="indexterm"></a><a id="idm225462615344" class="indexterm"></a><div class="para">
+ </div><h4 id="bh-Removing_Individual_Packages"> Removing Individual Packages </h4><a id="idm261681498480" class="indexterm"></a><a id="idm261757207328" class="indexterm"></a><div class="para">
To uninstall a particular package, as well as any packages that depend on it, run the following command as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">yum</code> <code class="option">remove</code> <em class="replaceable"><code>package_name</code></em>…</pre><div class="para">
As when you install multiple packages, you can remove several at once by adding more package names to the command. For example, to remove <span class="package">totem</span>, <span class="package">rhythmbox</span>, and <span class="package">sound-juicer</span>, type the following at a shell prompt:
@@ -1321,14 +1337,14 @@ Done</pre><div class="para">
</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">
- Yum 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.
+ Yum 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.2, “Uninstalling Packages”</a> in the <span class="application"><strong>RPM</strong></span> chapter.
</div></div></div><h4 id="bh-Removing_a_Package_Group"> Removing a Package Group </h4><div class="para">
You can remove a package group using syntax congruent with the <code class="command">install</code> syntax:
</div><pre class="synopsis"><code class="command">yum</code> <code class="option">groupremove</code> <em class="replaceable"><code>group</code></em></pre><pre class="synopsis"><code class="command">yum</code> <code class="option">remove</code> @<em class="replaceable"><code>group</code></em></pre><div class="para">
The following are alternative but equivalent ways of removing the <code class="literal">KDE Desktop</code> group:
</div><pre class="screen">~]# <code class="command">yum groupremove "KDE Desktop"</code>
~]# <code class="command">yum groupremove kde-desktop</code>
-~]# <code class="command">yum remove @kde-desktop</code></pre><div class="important" id="important-Package_Group_Removal"><div class="admonition_header"><h2>Intelligent package group removal</h2></div><div class="admonition"><a id="idm225473554544" class="indexterm"></a><a id="idm225453689184" class="indexterm"></a><div class="para">
+~]# <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="idm261785467536" class="indexterm"></a><a id="idm261756358928" 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 5.3.1, “Setting [main] Options”</a>.
</div></div></div></div><div class="section" id="sec-Yum-Transaction_History"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.6. Working with Transaction History</h3></div></div></div><div class="para">
The <code class="command">yum history</code> command allows users to review information about a timeline of Yum transactions, the dates and times on when they occurred, the number of packages affected, whether transactions succeeded or were aborted, and if the RPM database was changed between transactions. Additionally, this command can be used to undo or redo certain transactions.
@@ -1542,7 +1558,7 @@ history addon-info</pre><div class="para">
Yum stores the transaction history in a single SQLite database file. To start new transaction history, run the following command as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">yum</code> <code class="option">history</code> <code class="option">new</code></pre><div class="para">
This will create a new, empty database file in the <code class="filename">/var/lib/yum/history/</code> directory. The old transaction history will be kept, but will not be accessible as long as a newer database file is present in the directory.
- </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">5.3. Configuring Yum and Yum Repositories</h2></div></div></div><a id="idm225460406480" class="indexterm"></a><a id="idm225454496896" class="indexterm"></a><div class="para">
+ </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">5.3. Configuring Yum and Yum Repositories</h2></div></div></div><a id="idm261746030416" class="indexterm"></a><a id="idm261746029008" class="indexterm"></a><div class="para">
The configuration file for <code class="command">yum</code> and related utilities is located at <code class="filename">/etc/yum.conf</code>. This file contains one mandatory <code class="literal">[main]</code> section, which allows you to set Yum options that have global effect, and may also contain one or more <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> sections, which allow you to set repository-specific options. However, 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. The values you define in the <code class="literal">[main]</code> section of the <code class="filename">/etc/yum.conf</code> file may override values set in individual <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> sections.
</div><div class="para">
This section shows you how to:
@@ -1556,7 +1572,7 @@ history addon-info</pre><div class="para">
add, enable, and disable Yum repositories on the command line; and,
</div></li><li class="listitem"><div class="para">
set up your own custom Yum repository.
- </div></li></ul></div><div class="section" id="sec-Setting_main_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.3.1. Setting [main] Options</h3></div></div></div><a id="idm225455940176" class="indexterm"></a><div class="para">
+ </div></li></ul></div><div class="section" id="sec-Setting_main_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.3.1. Setting [main] Options</h3></div></div></div><a id="idm261632539312" 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, and while some of the key-value pairs in this section affect how <code class="command">yum</code> operates, others affect how Yum treats repositories. You can add many additional options under the <code class="literal">[main]</code> section heading in <code class="filename">/etc/yum.conf</code>.
</div><div class="para">
A sample <code class="filename">/etc/yum.conf</code> configuration file can look like this:
@@ -1605,7 +1621,7 @@ installonly_limit=3
</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="option">gpgcheck=<em class="replaceable"><code>value</code></em></code> for individual repositories instead; that is, you can enable GPG-checking on one repository while disabling it on another. Setting <code class="option">gpgcheck=<em class="replaceable"><code>value</code></em></code> for an individual repository in its corresponding <code class="filename">.repo</code> file overrides the default if it is present in <code class="filename">/etc/yum.conf</code>.
</div><div class="para">
- For more information on GPG signature-checking, refer to <a class="xref" href="#s1-check-rpm-sig">Section A.3, “Checking a Package's Signature”</a>.
+ For more information on GPG signature-checking, refer to <a class="xref" href="#s1-check-rpm-sig">Section A.3.2, “Checking Package Signatures”</a>.
</div></dd><dt class="varlistentry"><span class="term"><code class="option">groupremove_leaf_only</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
…where <em class="replaceable"><code>value</code></em> is one of:
</div><div class="para">
@@ -1658,7 +1674,7 @@ installonly_limit=3
…where <em class="replaceable"><code>value</code></em> is an integer <code class="literal">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="literal">0</code> makes <code class="command">yum</code> retry forever. The default value is <code class="literal">10</code>.
</div></dd></dl></div><div class="para">
For a complete list of available <code class="literal">[main]</code> options, refer to the <code class="literal">[main] OPTIONS</code> section of the <span class="bold bold"><strong>yum.conf</strong></span>(5) manual page.
- </div></div><div class="section" id="sec-Setting_repository_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.3.2. Setting [repository] Options</h3></div></div></div><a id="idm225416229088" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="sec-Setting_repository_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.3.2. Setting [repository] Options</h3></div></div></div><a id="idm261708793728" class="indexterm"></a><div class="para">
The <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> sections, where <em class="replaceable"><code>repository</code></em> is a unique repository ID such as <code class="literal">my_personal_repo</code> (spaces are not permitted), allow you to define individual Yum repositories.
</div><div class="para">
The following is a bare-minimum example of the form a <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> section takes:
@@ -1694,7 +1710,7 @@ baseurl=<em class="replaceable"><code>repository_url</code></em></pre><div class
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. For a complete list, refer to the <code class="literal">[repository] OPTIONS</code> section of the <span class="bold bold"><strong>yum.conf</strong></span>(5) manual page.
- </div></div><div class="section" id="sec-Using_Yum_Variables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.3.3. Using Yum Variables</h3></div></div></div><a id="idm225469331040" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="sec-Using_Yum_Variables"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.3.3. Using Yum Variables</h3></div></div></div><a id="idm261690738800" 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 Yum 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 class="variablelist"><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. Yum 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.
@@ -1727,7 +1743,7 @@ assumeyes = False
bandwith = 0
bugtracker_url = https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%206&component=yum
cache = 0
-<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em></pre></div><div class="section" id="sec-Managing_Yum_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.3.5. Adding, Enabling, and Disabling a Yum Repository</h3></div></div></div><a id="idm225438608208" class="indexterm"></a><div class="para">
+<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em></pre></div><div class="section" id="sec-Managing_Yum_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.3.5. Adding, Enabling, and Disabling a Yum Repository</h3></div></div></div><a id="idm261738206528" class="indexterm"></a><div class="para">
<a class="xref" href="#sec-Setting_repository_Options">Section 5.3.2, “Setting [repository] Options”</a> described various options you can use to define a Yum repository. This section explains how to add, enable, and disable a repository by using the <code class="command">yum-config-manager</code> command.
</div><h4 id="bh-Managing_Yum_Repositories-Adding"> Adding a Yum Repository </h4><div class="para">
To define a new repository, you can either add a <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> section to the <code class="filename">/etc/yum.conf</code> file, or to a <code class="filename">.repo</code> file in the <code class="filename">/etc/yum.repos.d/</code> directory. All files with the <code class="filename">.repo</code> file extension in this directory are read by <code class="command">yum</code>, and best practice is to define your repositories here instead of in <code class="filename">/etc/yum.conf</code>.
@@ -1765,7 +1781,7 @@ cachedir = /var/cache/yum/x86_64/6Server/example
…where <em class="replaceable"><code>repository</code></em> is the unique repository ID (use <code class="command">yum repolist all</code> to list available repository IDs). Similarly to <code class="command">yum-config-manager --enable</code>, you can use a glob expression to disable all matching repositories at the same time:
</div><pre class="synopsis"><code class="command">yum-config-manager</code> <code class="option">--disable</code> <em class="replaceable"><code>glob_expression</code></em>…</pre><div class="para">
When successful, the <code class="command">yum-config-manager --disable</code> command displays the current configuration.
- </div></div><div class="section" id="sec-Creating_a_Yum_Repository"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.3.6. Creating a Yum Repository</h3></div></div></div><a id="idm225475119824" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="sec-Creating_a_Yum_Repository"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.3.6. Creating a Yum Repository</h3></div></div></div><a id="idm261751717984" class="indexterm"></a><div class="para">
To set up a Yum 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:
@@ -1775,13 +1791,13 @@ cachedir = /var/cache/yum/x86_64/6Server/example
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 creates the necessary metadata for your Yum repository, as well as the <span class="application"><strong>sqlite</strong></span> database for speeding up <code class="command">yum</code> operations.
- </div></div></div><div class="section" id="sec-Yum_Plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.4. Yum Plug-ins</h2></div></div></div><a id="idm225436457568" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="sec-Yum_Plugins"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.4. Yum Plug-ins</h2></div></div></div><a id="idm261726019856" class="indexterm"></a><div class="para">
Yum provides plug-ins that extend and enhance its operations. Certain plug-ins are installed by default. Yum always informs you which plug-ins, if any, are loaded and active whenever you call any <code class="command">yum</code> command. For example:
</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 plug-in names which follow <code class="command">Loaded plugins</code> are the names you can provide to the <code class="option">--disableplugin=<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">5.4.1. Enabling, Configuring, and Disabling Yum Plug-ins</h3></div></div></div><a id="idm225476916928" class="indexterm"></a><a id="idm225476915488" class="indexterm"></a><a id="idm225461612848" class="indexterm"></a><div class="para">
+ </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">5.4.1. Enabling, Configuring, and Disabling Yum Plug-ins</h3></div></div></div><a id="idm261747208928" class="indexterm"></a><a id="idm261750605968" class="indexterm"></a><a id="idm261750604528" class="indexterm"></a><div class="para">
To enable Yum plug-ins, 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="literal">1</code>:
</div><pre class="programlisting">plugins=1</pre><div class="para">
You can disable all plug-ins by changing this line to <code class="command">plugins=0</code>.
@@ -1804,7 +1820,7 @@ enabled=1</pre><div class="para">
Yum plug-ins 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> plug-in is named <code class="filename">yum-presto</code>, for example. You can install a Yum plug-in in the same way you install other packages. For instance, to install the <span class="application"><strong>security</strong></span> plug-in, 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">5.4.3. Plug-in Descriptions</h3></div></div></div><div class="para">
The following list provides descriptions of a few useful Yum plug-ins:
- </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225481207520" class="indexterm"></a>
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261732537792" class="indexterm"></a>
<span class="application"><strong>fs-snapshot</strong></span> (<span class="package">yum-plugin-fs-snapshot</span>) </span></dt><dd><div class="para">
The <span class="application"><strong>fs-snapshot</strong></span> plug-in extends Yum to create a snapshot of a file system before proceeding with a transaction such as a system update or package removal. When a user decides that the changes made by the transaction are unwanted, this mechanism allows the user to roll back to the changes that are stored in a snapshot.
</div><div class="para">
@@ -1895,20 +1911,20 @@ enabled=1</pre><div class="para">
<code class="option">lvcreate_size_args</code>=<em class="replaceable"><code>value</code></em>
</td><td class="">
Allows you to specify the size of a logical volume snapshot. The <em class="replaceable"><code>value</code></em> must be the <code class="option">-l</code> or <code class="option">-L</code> command line option for the <span class="application"><strong>lvcreate</strong></span> utility followed by a valid argument (for example, <code class="literal">-l 80%ORIGIN</code>).
- </td></tr></tbody></table></div></div><br class="table-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225470743104" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261721065824" 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> plug-in adds support to Yum 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> plug-in 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="idm225468322880" class="indexterm"></a>
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261745310320" 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> plug-in 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> plug-in is installed by default.
- </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225452465744" class="indexterm"></a>
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261748928784" 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">
See the <span class="bold bold"><strong>rhnplugin</strong></span>(8) manual page for more information about the plug-in.
- </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225459687904" class="indexterm"></a>
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261723179952" 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 Yum provides the <span class="application"><strong>security</strong></span> plug-in, which extends <code class="command">yum</code> with a set of highly-useful security-related commands, subcommands and options.
</div><div class="para">
@@ -1938,17 +1954,17 @@ NetworkManager-glib.x86_64 1:0.8.999-2.git20110509.fc15 updates
...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">
See the <span class="bold bold"><strong>yum-security</strong></span>(8) manual page for usage details and further explanation of the enhancements the <span class="application"><strong>security</strong></span> plug-in 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">5.5. Additional Resources</h2></div></div></div><a id="idm225468319168" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a href="http://yum.baseurl.org/wiki/Guides">http://yum.baseurl.org/wiki/Guides</a> </span></dt><dd><div class="para">
+ </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">5.5. Additional Resources</h2></div></div></div><a id="idm261725123568" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a href="http://yum.baseurl.org/wiki/Guides">http://yum.baseurl.org/wiki/Guides</a> </span></dt><dd><div class="para">
The <code class="literal">Yum Guides</code> section of the Yum wiki contains more documentation.
- </div></dd></dl></div></div></div></div><div class="part" id="part-Infrastructure_Services"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part III. Infrastructure Services</h1></div></div></div><div class="partintro" id="idm225440985120"><div></div><div class="para">
+ </div></dd></dl></div></div></div></div><div class="part" id="part-Infrastructure_Services"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part III. Infrastructure Services</h1></div></div></div><div class="partintro" id="idm261722278080"><div></div><div class="para">
This part provides information on how to configure services and daemons, configure authentication, and enable remote logins.
- </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#ch-Services_and_Daemons">6. Services and Daemons</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-services-configuring">6.1. Configuring Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-configuration-enabling">6.1.1. Enabling the Service</a></span></dt><dt><span class="section"><a href="#s3-services-configuration-disabling">6.1.2. Disabling the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-running">6.2. Running Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-running-checking">6.2.1. Checking the Service Status</a></span></dt><dt><span class="section"><a href="#s3-services-running-running">6.2.2. Running the Service</a></span></dt><dt><span class="section"><a href="#s3-services-running-stopping">6.2.3. Stopping the Service</a></span></dt><dt><span cl
ass="section"><a href="#s3-services-running-restarting">6.2.4. Restarting the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-additional-resources">6.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-additional-resources-installed">6.3.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-services-additional-resources-books">6.3.2. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-OpenSSH">7. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ssh-protocol">7.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-why">7.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a href="#s2-ssh-features">7.1.2. Main Features</a></span></dt><dt><span class="section"><a href="#s2-ssh-versions">7.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="#s2-ssh-conn">7.1.4.
Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-configuration">7.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-configuration-configs">7.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-sshd">7.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-requiring">7.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-keypairs">7.2.4. Using Key-based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-clients">7.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-clients-ssh">7.3.1. Using the ssh Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-scp">7.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class
="section"><a href="#s2-ssh-clients-sftp">7.3.3. Using the <code class="command">sftp</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-beyondshell">7.4. More Than a Secure Shell</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-beyondshell-x11">7.4.1. X11 Forwarding</a></span></dt><dt><span class="section"><a href="#s2-ssh-beyondshell-tcpip">7.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-openssh-additional-resources">7.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-TigerVNC">8. TigerVNC</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-vnc-server">8.1. VNC Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-vnc-installation">8.1.1. Installing VNC Server</a></span></dt><dt><span class="section"><a href="#s3-configuring-vnc-server">8.1.2. Configuring VNC Server</a></span></dt><dt><span class="section"><a href="#s4-start
ing-vncserver">8.1.3. Starting VNC Server</a></span></dt><dt><span class="section"><a href="#terminating-vnc-session">8.1.4. Terminating a VNC session</a></span></dt></dl></dd><dt><span class="section"><a href="#s5-vnc-viewer">8.2. VNC Viewer</a></span></dt><dd><dl><dt><span class="section"><a href="#installing-vncviewer">8.2.1. Installing VNC Viewer</a></span></dt><dt><span class="section"><a href="#s6-connecting-vnc-viewer">8.2.2. Connecting to VNC Server</a></span></dt><dt><span class="section"><a href="#s1-using_ssh">8.2.3. Connecting to VNC Server using SSH</a></span></dt></dl></dd><dt><span class="section"><a href="#s9-additional-sources">8.3. Additional Resources</a></span></dt></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 6. Services and Daemons</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-services-
configuring">6.1. Configuring Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-configuration-enabling">6.1.1. Enabling the Service</a></span></dt><dt><span class="section"><a href="#s3-services-configuration-disabling">6.1.2. Disabling the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-running">6.2. Running Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-running-checking">6.2.1. Checking the Service Status</a></span></dt><dt><span class="section"><a href="#s3-services-running-running">6.2.2. Running the Service</a></span></dt><dt><span class="section"><a href="#s3-services-running-stopping">6.2.3. Stopping the Service</a></span></dt><dt><span class="section"><a href="#s3-services-running-restarting">6.2.4. Restarting the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-additional-resources">6.3. Additional Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-services-additional-resources-installed">6.3.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-services-additional-resources-books">6.3.2. Related Books</a></span></dt></dl></dd></dl></div><a id="idm225462609616" class="indexterm"></a><div class="para">
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#ch-Services_and_Daemons">6. Services and Daemons</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-services-configuring">6.1. Configuring Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-configuration-enabling">6.1.1. Enabling the Service</a></span></dt><dt><span class="section"><a href="#s3-services-configuration-disabling">6.1.2. Disabling the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-running">6.2. Running Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-running-checking">6.2.1. Checking the Service Status</a></span></dt><dt><span class="section"><a href="#s3-services-running-running">6.2.2. Running the Service</a></span></dt><dt><span class="section"><a href="#s3-services-running-stopping">6.2.3. Stopping the Service</a></span></dt><dt><span cl
ass="section"><a href="#s3-services-running-restarting">6.2.4. Restarting the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-additional-resources">6.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-services-additional-resources-installed">6.3.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-services-additional-resources-books">6.3.2. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-OpenSSH">7. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-ssh-protocol">7.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-why">7.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a href="#s2-ssh-features">7.1.2. Main Features</a></span></dt><dt><span class="section"><a href="#s2-ssh-versions">7.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="#s2-ssh-conn">7.1.4.
Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-configuration">7.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-configuration-configs">7.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-sshd">7.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-requiring">7.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-keypairs">7.2.4. Using Key-based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-clients">7.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-clients-ssh">7.3.1. Using the ssh Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-scp">7.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class
="section"><a href="#s2-ssh-clients-sftp">7.3.3. Using the <code class="command">sftp</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-beyondshell">7.4. More Than a Secure Shell</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-beyondshell-x11">7.4.1. X11 Forwarding</a></span></dt><dt><span class="section"><a href="#s2-ssh-beyondshell-tcpip">7.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-openssh-additional-resources">7.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-TigerVNC">8. TigerVNC</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-vnc-server">8.1. VNC Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-vnc-installation">8.1.1. Installing VNC Server</a></span></dt><dt><span class="section"><a href="#s3-configuring-vnc-server">8.1.2. Configuring VNC Server</a></span></dt><dt><span class="section"><a href="#s4-start
ing-vncserver">8.1.3. Starting VNC Server</a></span></dt><dt><span class="section"><a href="#terminating-vnc-session">8.1.4. Terminating a VNC Session</a></span></dt></dl></dd><dt><span class="section"><a href="#s5-vnc-viewer">8.2. VNC Viewer</a></span></dt><dd><dl><dt><span class="section"><a href="#installing-vncviewer">8.2.1. Installing VNC Viewer</a></span></dt><dt><span class="section"><a href="#s6-connecting-vnc-viewer">8.2.2. Connecting to VNC Server</a></span></dt><dt><span class="section"><a href="#s1-using_ssh">8.2.3. Connecting to VNC Server Using SSH</a></span></dt></dl></dd><dt><span class="section"><a href="#s9-additional-sources">8.3. Additional Resources</a></span></dt></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 6. Services and Daemons</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-services-
configuring">6.1. Configuring Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-configuration-enabling">6.1.1. Enabling the Service</a></span></dt><dt><span class="section"><a href="#s3-services-configuration-disabling">6.1.2. Disabling the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-running">6.2. Running Services</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-services-running-checking">6.2.1. Checking the Service Status</a></span></dt><dt><span class="section"><a href="#s3-services-running-running">6.2.2. Running the Service</a></span></dt><dt><span class="section"><a href="#s3-services-running-stopping">6.2.3. Stopping the Service</a></span></dt><dt><span class="section"><a href="#s3-services-running-restarting">6.2.4. Restarting the Service</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-services-additional-resources">6.3. Additional Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#s2-services-additional-resources-installed">6.3.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-services-additional-resources-books">6.3.2. Related Books</a></span></dt></dl></dd></dl></div><a id="idm261755339520" 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. For more information, refer to the Fedora 21 <em class="citetitle">Security Guide</em>.
- </div></div></div><div class="section" id="s1-services-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. Configuring Services</h2></div></div></div><a id="idm225415014800" class="indexterm"></a><a id="idm225473811584" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s1-services-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. Configuring Services</h2></div></div></div><a id="idm261695916496" class="indexterm"></a><a id="idm261729269296" 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.
@@ -1966,7 +1982,7 @@ NetworkManager-glib.x86_64 1:0.8.999-2.git20110509.fc15 updates
The next time you boot the system, the service will <span class="emphasis"><em>not</em></span> be started. For information on how to stop the service immediately, refer to <a class="xref" href="#s3-services-running-stopping">Section 6.2.3, “Stopping the Service”</a>.
</div><div class="example" id="exam-services-configuration-disabling"><h6>Example 6.2. Disabling the telnet service</h6><div class="example-contents"><div class="para">
In order to secure the system, users are advised to disable insecure connection protocols such as Telnet. You can make sure that the <code class="systemitem">telnet</code> service is disabled by running the following command as <code class="systemitem">root</code>:
- </div><pre class="screen">~]# <code class="command">systemctl disable telnet.service</code></pre></div></div><br class="example-break" /></div></div><div class="section" id="s1-services-running"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.2. Running Services</h2></div></div></div><a id="idm225507119328" class="indexterm"></a><a id="idm225462949904" class="indexterm"></a><div class="para">
+ </div><pre class="screen">~]# <code class="command">systemctl disable telnet.service</code></pre></div></div><br class="example-break" /></div></div><div class="section" id="s1-services-running"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.2. Running Services</h2></div></div></div><a id="idm261725707520" class="indexterm"></a><a id="idm261758407904" 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.
@@ -2041,13 +2057,13 @@ atd.service loaded active running Job spooling tools
<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">6.3.2. Related Books</h3></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <em class="citetitle">Fedora 21 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-OpenSSH" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 7. OpenSSH</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-ssh-protocol">7.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-why">7.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a href="#s2-ssh-features">7.1.2. Main Features</a></span></dt><dt><span class="section"><a href="#s2-ssh-versions">7.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="#s2-ssh-conn">7.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-configuration">7.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-configuration-configs">7.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="#s2-ssh-configu
ration-sshd">7.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-requiring">7.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-keypairs">7.2.4. Using Key-based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-clients">7.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-clients-ssh">7.3.1. Using the ssh Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-scp">7.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-sftp">7.3.3. Using the <code class="command">sftp</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-beyondshell">7.4. More Than a Secure Shell</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-beyondshell-x11">7.4.1. X11 Forwarding</a></span></d
t><dt><span class="section"><a href="#s2-ssh-beyondshell-tcpip">7.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-openssh-additional-resources">7.5. Additional Resources</a></span></dt></dl></div><a id="idm225451468752" class="indexterm"></a><div class="para">
+ </div></dd></dl></div></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 7. OpenSSH</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-ssh-protocol">7.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-why">7.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a href="#s2-ssh-features">7.1.2. Main Features</a></span></dt><dt><span class="section"><a href="#s2-ssh-versions">7.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="#s2-ssh-conn">7.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-configuration">7.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-configuration-configs">7.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="#s2-ssh-configu
ration-sshd">7.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-requiring">7.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="#s2-ssh-configuration-keypairs">7.2.4. Using Key-based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-clients">7.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-clients-ssh">7.3.1. Using the ssh Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-scp">7.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="#s2-ssh-clients-sftp">7.3.3. Using the <code class="command">sftp</code> Utility</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-ssh-beyondshell">7.4. More Than a Secure Shell</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ssh-beyondshell-x11">7.4.1. X11 Forwarding</a></span></d
t><dt><span class="section"><a href="#s2-ssh-beyondshell-tcpip">7.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-openssh-additional-resources">7.5. Additional Resources</a></span></dt></dl></div><a id="idm261727699840" 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 in to 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 in to 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 in to 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, the OpenSSH packages require the OpenSSL package <span class="package">openssl-libs</span>, which installs several important cryptographic libraries, enabling OpenSSH to provide encrypted communications.
- </div><div class="section" id="s1-ssh-protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.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">7.1.1. Why Use SSH?</h3></div></div></div><a id="idm225507123312" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s1-ssh-protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.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">7.1.1. Why Use SSH?</h3></div></div></div><a id="idm261738039408" 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 class="variablelist"><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.
@@ -2059,7 +2075,7 @@ atd.service loaded active running Job spooling tools
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">7.1.2. Main Features</h3></div></div></div><a id="idm225425154912" class="indexterm"></a><a id="idm225425153472" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-ssh-features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.1.2. Main Features</h3></div></div></div><a id="idm261761530080" class="indexterm"></a><a id="idm261721315328" class="indexterm"></a><div class="para">
The SSH protocol provides the following safeguards:
</div><div class="variablelist"><dl class="variablelist"><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.
@@ -2077,11 +2093,11 @@ atd.service loaded active running Job spooling tools
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">7.1.3. Protocol Versions</h3></div></div></div><a id="idm225446594128" class="indexterm"></a><a id="idm225451406480" class="indexterm"></a><div class="para">
+ </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">7.1.3. Protocol Versions</h3></div></div></div><a id="idm261709201296" class="indexterm"></a><a id="idm261709199856" 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">7.1.4. Event Sequence of an SSH Connection</h3></div></div></div><a id="idm225405875952" class="indexterm"></a><div class="para">
+ </div></div></div></div><div class="section" id="s2-ssh-conn"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.1.4. Event Sequence of an SSH Connection</h3></div></div></div><a id="idm261714497952" 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.
@@ -2091,7 +2107,7 @@ atd.service loaded active running Job spooling tools
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">7.1.4.1. Transport Layer</h4></div></div></div><a id="idm225469556896" class="indexterm"></a><div class="para">
+ </div></li></ol></div><div class="section" id="s2-ssh-protocol-conn-transport"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.1.4.1. Transport Layer</h4></div></div></div><a id="idm261750974112" 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:
@@ -2113,12 +2129,12 @@ atd.service loaded active running Job spooling tools
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">7.1.4.2. Authentication</h4></div></div></div><a id="idm225479128816" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-ssh-protocol-authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.1.4.2. Authentication</h4></div></div></div><a id="idm261761617200" 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">7.1.4.3. Channels</h4></div></div></div><a id="idm225439540160" 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><a href="#ftn.idm225425309232" class="footnote"><sup class="footnote" id="idm225425309232">[1]</sup></a>. Each of these channels handles communication for different terminal sessions and for forwarded X11 sessions.
+ </div></div><div class="section" id="s2-ssh-protocol-connection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.1.4.3. Channels</h4></div></div></div><a id="idm261720896976" 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><a href="#ftn.idm261722794592" class="footnote"><sup class="footnote" id="idm261722794592">[1]</sup></a>. 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">
@@ -2127,9 +2143,9 @@ atd.service loaded active running Job spooling tools
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">7.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">7.2.1. Configuration Files</h3></div></div></div><a id="idm225435530304" class="indexterm"></a><div class="para">
+ </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">7.2.1. Configuration Files</h3></div></div></div><a id="idm261750712176" 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="idm225435816880" class="indexterm"></a><a id="idm225436343184" class="indexterm"></a><div class="para">
+ </div><a id="idm261745878016" class="indexterm"></a><a id="idm261745876128" class="indexterm"></a><div class="para">
System-wide SSH configuration information is stored in the <code class="filename">/etc/ssh/</code> directory as described in <a class="xref" href="#table-ssh-configuration-configs-system">Table 7.1, “System-wide configuration files”</a>. User-specific SSH configuration information is stored in <code class="filename">~/.ssh/</code> within the user's home directory as described in <a class="xref" href="#table-ssh-configuration-configs-user">Table 7.2, “User-specific configuration files”</a>.
</div><div class="table" id="table-ssh-configuration-configs-system"><h6>Table 7.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 class="">
File
@@ -2217,11 +2233,11 @@ atd.service loaded active running Job spooling tools
Contains host keys of SSH servers accessed by the user. This file is very important for ensuring that the SSH client is connecting to the correct SSH server.
</td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
For information concerning various directives that can be used in the SSH configuration files, see the <code class="filename">ssh_config</code>(5) and <code class="filename">sshd_config</code>(5) manual pages.
- </div></div><div class="section" id="s2-ssh-configuration-sshd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.2. Starting an OpenSSH Server</h3></div></div></div><a id="idm225448642848" 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">
+ </div></div><div class="section" id="s2-ssh-configuration-sshd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.2. Starting an OpenSSH Server</h3></div></div></div><a id="idm261758551248" 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> package installed. See <a class="xref" href="#sec-Installing">Section 5.2.4, “Installing Packages”</a> for more information on how to install new packages in Fedora.
- </div></div></div><a id="idm225503766096" class="indexterm"></a><div class="para">
+ </div></div></div><a id="idm261746613856" class="indexterm"></a><div class="para">
To start the <code class="command">sshd</code> daemon in the current session, type the following at a shell prompt as <code class="systemitem">root</code>:
- </div><pre class="screen">~]# <code class="command">systemctl start sshd.service</code></pre><a id="idm225478199872" class="indexterm"></a><div class="para">
+ </div><pre class="screen">~]# <code class="command">systemctl start sshd.service</code></pre><a id="idm261757362848" class="indexterm"></a><div class="para">
To stop the running <code class="command">sshd</code> daemon in the current session, use the following command as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">systemctl stop sshd.service</code></pre><div class="para">
If you want the daemon to start automatically at the boot time, type as <code class="systemitem">root</code>:
@@ -2237,7 +2253,7 @@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.</pre><div class="para">
To prevent this, you can backup the relevant files from the <code class="filename">/etc/ssh/</code> directory (see <a class="xref" href="#table-ssh-configuration-configs-system">Table 7.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">7.2.3. Requiring SSH for Remote Connections</h3></div></div></div><a id="idm225372435536" class="indexterm"></a><a id="idm225448634384" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-ssh-configuration-requiring"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.3. Requiring SSH for Remote Connections</h3></div></div></div><a id="idm261757461536" class="indexterm"></a><a id="idm261757460096" 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">
These services are not installed by default in Fedora. If required, to make sure these services are not running, type the following commands at a shell prompt:
@@ -2251,7 +2267,7 @@ It is also possible that the RSA host key has just been changed.</pre><div class
<code class="command">systemctl disable rlogin.service</code>
<code class="command">systemctl disable vsftpd.service</code></pre><div class="para">
See <a class="xref" href="#ch-Services_and_Daemons">Chapter 6, <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">7.2.4. Using Key-based Authentication</h3></div></div></div><a id="idm225471409376" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-ssh-configuration-keypairs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.2.4. Using Key-based Authentication</h3></div></div></div><a id="idm261734415264" class="indexterm"></a><div class="para">
To improve the system security even further, generate SSH key pairs and then enforce key-based authentication by disabling password authentication. To do so, open the <code class="filename">/etc/ssh/sshd_config</code> configuration file in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>, and change the <code class="option">PasswordAuthentication</code> option as follows:
</div><pre class="screen">PasswordAuthentication no</pre><div class="para">
If you are working on a system other than a new default installation, check that <code class="command">PubkeyAuthentication no</code> has <span class="bold bold"><strong>not</strong></span> been set. If connected remotely, not using console or out-of-band access, testing the key-based log in process before disabling password authentication is advised.
@@ -2263,9 +2279,9 @@ It is also possible that the RSA host key has just been changed.</pre><div class
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 pairs, backup the <code class="filename">~/.ssh/</code> directory. After reinstalling, copy it back to your home directory. This process can be done for all users on your system, including <code class="systemitem">root</code>.
- </div></div></div><div class="section" id="s3-ssh-configuration-keypairs-generating"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.2.4.1. Generating Key Pairs</h4></div></div></div><a id="idm225471551712" class="indexterm"></a><a id="idm225461446800" class="indexterm"></a><div class="para">
+ </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">7.2.4.1. Generating Key Pairs</h4></div></div></div><a id="idm261732277456" class="indexterm"></a><a id="idm261732276016" 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="idm225474914304" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ </div><a id="idm261727539648" 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.
@@ -2296,9 +2312,9 @@ The key's randomart image is:
~]$ ls -ld ~/.ssh/
drwx------. 2 USER USER 54 Nov 25 16:56 /home/USER/.ssh/</pre></li><li class="step"><div class="para">
To copy the public key to a remote machine, issue a command in the following format: <pre class="synopsis"> <code class="command">ssh-copy-id <em class="replaceable"><code>user at hostname</code></em></code></pre> This will copy all <code class="filename">~/.ssh/id*.pub</code> public keys. Alternatively, specify the public keys file name as follows: <pre class="synopsis"><code class="command">ssh-copy-id -i <code class="filename">~/.ssh/id_rsa.pub</code> <em class="replaceable"><code>user at hostname</code></em></code></pre> This will copy the content of <code class="filename">~/.ssh/id_rsa.pub</code> into the <code class="filename">~/.ssh/authorized_keys</code> file on the machine to which you want to connect. If the file already exists, the keys are appended to its end.
- </div></li></ol></div><a id="idm225448653648" class="indexterm"></a><a id="idm225448652208" class="indexterm"></a><div class="para">
+ </div></li></ol></div><a id="idm261716488912" class="indexterm"></a><a id="idm261756568576" class="indexterm"></a><div class="para">
To generate an ECDSA key pair for version 2 of the SSH protocol, follow these steps:
- </div><a id="idm225458858288" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ </div><a id="idm261717138704" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step"><div class="para">
Generate an ECDSA key pair by typing the following at a shell prompt:
</div><pre class="screen">~]$ <code class="command">ssh-keygen -t ecdsa</code>
Generating public/private ecdsa key pair.
@@ -2311,7 +2327,7 @@ Enter file in which to save the key (/home/USER/.ssh/id_ecdsa):</pre></li><li cl
</div><pre class="screen">Your identification has been saved in /home/USER/.ssh/id_ecdsa.
Your public key has been saved in /home/USER/.ssh/id_ecdsa.pub.
The key fingerprint is:
-fd:1d:ca:10:52:96:21:43:7e:bd:4c:fc:5b:35:6b:63 USER at my-server
+fd:1d:ca:10:52:96:21:43:7e:bd:4c:fc:5b:35:6b:63 USER at penguin.example.com
The key's randomart image is:
+--[ECDSA 256]---+
| .+ +o |
@@ -2333,14 +2349,14 @@ drwx------. 2 USER USER 54 Nov 25 16:56 /home/USER/.ssh/</pre></li><li class="st
See <a class="xref" href="#s3-ssh-configuration-keypairs-agent">Section 7.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">7.2.4.2. Configuring ssh-agent</h4></div></div></div><a id="idm225470585184" class="indexterm"></a><a id="idm225470583584" class="indexterm"></a><div class="para">
+ </div></div></div></div><div class="section" id="s3-ssh-configuration-keypairs-agent"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.2.4.2. Configuring ssh-agent</h4></div></div></div><a id="idm261751905360" class="indexterm"></a><a id="idm261756019168" 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/USER/.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">7.3. OpenSSH Clients</h2></div></div></div><a id="idm225460456224" 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">
+ </div></div></div></div><div class="section" id="s1-ssh-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.3. OpenSSH Clients</h2></div></div></div><a id="idm261779445936" 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> package installed. See <a class="xref" href="#sec-Installing">Section 5.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">7.3.1. Using the ssh Utility</h3></div></div></div><a id="idm225463824048" class="indexterm"></a><a id="idm225463822448" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s2-ssh-clients-ssh"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.1. Using the ssh Utility</h3></div></div></div><a id="idm261758668768" class="indexterm"></a><a id="idm261749832880" class="indexterm"></a><div class="para">
The <code class="command">ssh</code> utility allows you to log in to a remote machine and execute commands there. It is a secure replacement for the <code class="command">rlogin</code>, <code class="command">rsh</code>, and <code class="command">telnet</code> programs.
</div><div class="para">
Similarly to the <code class="command">telnet</code> command, log in to a remote machine by using the following command:
@@ -2380,7 +2396,7 @@ Original contents retained as /home/USER/.ssh/known_hosts.old</pre>
USER at penguin.example.com's password:
Fedora release 20 (Heisenbug)</pre><div class="para">
After you enter the correct password, the user name will be displayed, and you will return to your local shell prompt.
- </div></div><div class="section" id="s2-ssh-clients-scp"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.2. Using the <code class="command">scp</code> Utility</h3></div></div></div><a id="idm225458059248" class="indexterm"></a><a id="idm225438337440" class="indexterm"></a><a id="idm225438335360" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-ssh-clients-scp"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.2. Using the <code class="command">scp</code> Utility</h3></div></div></div><a id="idm261753551888" class="indexterm"></a><a id="idm261753550288" class="indexterm"></a><a id="idm261724816864" 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:
@@ -2400,7 +2416,7 @@ taglist.vim 100% 144KB 144.5KB/s 00:00</pre
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 USER at penguin.example.com:.vimrc .vimrc</code>
USER at penguin.example.com's password:
-.vimrc 100% 2233 2.2KB/s 00:00</pre></div><div class="section" id="s2-ssh-clients-sftp"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.3. Using the <code class="command">sftp</code> Utility</h3></div></div></div><a id="idm225449052320" class="indexterm"></a><a id="idm225449050720" class="indexterm"></a><div class="para">
+.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">7.3.3. Using the <code class="command">sftp</code> Utility</h3></div></div></div><a id="idm261738513344" class="indexterm"></a><a id="idm261754508016" 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:
@@ -2443,7 +2459,7 @@ sftp></pre><div class="para">
For a complete list of available commands, see the <code class="filename">sftp</code>(1) manual page.
</div></div></div><div class="section" id="s1-ssh-beyondshell"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.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">7.4.1. X11 Forwarding</h3></div></div></div><a id="idm225467983392" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-ssh-beyondshell-x11"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.4.1. X11 Forwarding</h3></div></div></div><a id="idm261745033024" 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">USER</code> as a user name, type:
@@ -2454,7 +2470,7 @@ USER at penguin.example.com's password:</pre><div class="para">
X11 forwarding can be very useful. For example, X11 forwarding can be used to create a secure, interactive session of the <span class="application"><strong>Print Settings</strong></span> utility. To do this, connect to the server using <span class="application"><strong>ssh</strong></span> and type:
</div><pre class="screen">~]$ <code class="command">system-config-printer &</code></pre><div class="para">
The <span class="application"><strong>Print Settings</strong></span> tool will appear, allowing the remote user to safely configure printing on the remote system.
- </div></div><div class="section" id="s2-ssh-beyondshell-tcpip"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.4.2. Port Forwarding</h3></div></div></div><a id="idm225470013440" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-ssh-beyondshell-tcpip"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.4.2. Port Forwarding</h3></div></div></div><a id="idm261728171520" 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.
@@ -2476,7 +2492,7 @@ USER at penguin.example.com's password:</pre><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">7.5. Additional Resources</h2></div></div></div><a id="idm225476506096" class="indexterm"></a><a id="idm225476504656" class="indexterm"></a><div class="para">
+ </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">7.5. Additional Resources</h2></div></div></div><a id="idm261783079296" class="indexterm"></a><a id="idm261783077856" class="indexterm"></a><div class="para">
For more information on how to configure or connect to an OpenSSH server on Fedora, see the resources listed below.
</div><h3 id="bh-OpenSSH-Resources-Installed">Installed Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="systemitem">sshd</code>(8) — The manual page for the <code class="systemitem">sshd</code> daemon documents available command line options and provides a complete list of supported configuration files and directories.
@@ -2496,25 +2512,27 @@ USER at penguin.example.com's password:</pre><div class="para">
<a href="http://www.openssh.com/">OpenSSH Home Page</a> — The OpenSSH home page containing further documentation, frequently asked questions, links to the mailing lists, bug reports, and other useful resources.
</div></li><li class="listitem"><div class="para">
<a href="http://www.openssl.org/">OpenSSL Home Page</a> — The OpenSSL home page containing further documentation, frequently asked questions, links to the mailing lists, and other useful resources.
- </div></li></ul></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div id="ftn.idm225425309232" class="footnote"><div class="para"><a href="#idm225425309232" class="para"><sup class="para">[1] </sup></a>
+ </div></li></ul></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div id="ftn.idm261722794592" class="footnote"><div class="para"><a href="#idm261722794592" class="para"><sup class="para">[1] </sup></a>
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 xml:lang="en-US" class="chapter" id="ch-TigerVNC" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 8. TigerVNC</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-vnc-server">8.1. VNC Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-vnc-installation">8.1.1. Installing VNC Server</a></span></dt><dt><span class="section"><a href="#s3-configuring-vnc-server">8.1.2. Configuring VNC Server</a></span></dt><dt><span class="section"><a href="#s4-starting-vncserver">8.1.3. Starting VNC Server</a></span></dt><dt><span class="section"><a href="#terminating-vnc-session">8.1.4. Terminating a VNC session</a></span></dt></dl></dd><dt><span class="section"><a href="#s5-vnc-viewer">8.2. VNC Viewer</a></span></dt><dd><dl><dt><span class="section"><a href="#installing-vncviewer">8.2.1. Installing VNC Viewer</a></span></dt><dt><span class="section"><a href="#s6-connecting-vnc
-viewer">8.2.2. Connecting to VNC Server</a></span></dt><dt><span class="section"><a href="#s1-using_ssh">8.2.3. Connecting to VNC Server using SSH</a></span></dt></dl></dd><dt><span class="section"><a href="#s9-additional-sources">8.3. Additional Resources</a></span></dt></dl></div><div class="para">
+ </div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-TigerVNC" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 8. TigerVNC</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-vnc-server">8.1. VNC Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-vnc-installation">8.1.1. Installing VNC Server</a></span></dt><dt><span class="section"><a href="#s3-configuring-vnc-server">8.1.2. Configuring VNC Server</a></span></dt><dt><span class="section"><a href="#s4-starting-vncserver">8.1.3. Starting VNC Server</a></span></dt><dt><span class="section"><a href="#terminating-vnc-session">8.1.4. Terminating a VNC Session</a></span></dt></dl></dd><dt><span class="section"><a href="#s5-vnc-viewer">8.2. VNC Viewer</a></span></dt><dd><dl><dt><span class="section"><a href="#installing-vncviewer">8.2.1. Installing VNC Viewer</a></span></dt><dt><span class="section"><a href="#s6-connecting-vnc
-viewer">8.2.2. Connecting to VNC Server</a></span></dt><dt><span class="section"><a href="#s1-using_ssh">8.2.3. Connecting to VNC Server Using SSH</a></span></dt></dl></dd><dt><span class="section"><a href="#s9-additional-sources">8.3. Additional Resources</a></span></dt></dl></div><div class="para">
<code class="systemitem">TigerVNC</code> (Tiger Virtual Network Computing) is a system for graphical desktop sharing which allows you to remotely control other computers.
</div><div class="para">
<code class="systemitem">TigerVNC</code> works on the client-server network: a <span class="bold bold"><strong>server</strong></span> shares its output (<code class="systemitem">vncserver</code>) and a <span class="bold bold"><strong>client</strong></span> (<code class="systemitem">vncviewer</code>) connects to the server.
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
Unlike in previous Red Hat Enterprise Linux distributions, <code class="systemitem">TigerVNC</code> in Red Hat Enterprise Linux 7 uses the <code class="systemitem">systemd</code> system management daemon for its configuration. The <code class="filename">/etc/sysconfig/vncserver</code> configuration file has been replaced by <code class="filename">/etc/systemd/system/vncserver at .service</code>.
</div></div></div><div class="section" id="s1-vnc-server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.1. VNC Server</h2></div></div></div><div class="para">
- <code class="systemitem">vncserver</code> is a utility which starts a VNC (Virtual Network Computing) desktop. It runs Xvnc with appropriate options and starts a window manager on the VNC desktop. <code class="systemitem">vncserver</code> allows users to run separate sessions in parallel on a machine which can then be accessed by any number of clients from anywhere.
+ <code class="systemitem">vncserver</code> is a utility which starts a VNC (Virtual Network Computing) desktop. It runs <span class="application"><strong>Xvnc</strong></span> with appropriate options and starts a window manager on the VNC desktop. <code class="systemitem">vncserver</code> allows users to run separate sessions in parallel on a machine which can then be accessed by any number of clients from anywhere.
</div><div class="section" id="s2-vnc-installation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.1. Installing VNC Server</h3></div></div></div><div class="para">
- To install the TigerVNC server, issue the following command as <code class="systemitem">root</code>:
+ To install the <span class="application"><strong>TigerVNC</strong></span> server, issue the following command as <code class="systemitem">root</code>:
<pre class="screen"><code class="command"><code class="computeroutput">~]# </code><strong class="userinput"><code>yum install tigervnc-server</code></strong></code></pre>
</div></div><div class="section" id="s3-configuring-vnc-server"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.2. Configuring VNC Server</h3></div></div></div><div class="procedure" id="configuring-vncserver"><h6>Procedure 8.1. Configuring the first VNC connection</h6><ol class="1"><li class="step"><div class="para">
A configuration file named <code class="filename">/etc/systemd/system/vncserver at .service</code> is required. To create this file, copy the <code class="filename">/lib/systemd/system/vncserver at .service</code> file as <code class="systemitem">root</code>:
</div><pre class="screen">
<code class="computeroutput">~]# </code><strong class="userinput"><code>cp /lib/systemd/system/vncserver at .service /etc/systemd/system/vncserver at .service</code></strong>
-</pre></li><li class="step"><div class="para">
+</pre><div class="para">
+ There is no need to include the display number in the file name because <code class="systemitem">systemd</code> automatically creates the appropriately named instance in memory on demand, replacing <code class="literal">'%i'</code> in the service file by the display number. For a single user it is not necessary to rename the file. For multiple users, a uniquely named service file for each user is required, for example, by adding the user name to the file name in some way. See <a class="xref" href="#configuring-vncserver-2users">Section 8.1.2.1, “Configuring VNC Server for Two Users”</a> for details.
+ </div></li><li class="step"><div class="para">
Edit <code class="filename">/etc/systemd/system/vncserver at .service</code>, replacing <em class="replaceable"><code>USER</code></em> with the actual user name. Leave the remaining lines of the file unmodified. The <code class="option">-geometry</code> argument specifies the size of the VNC desktop to be created; by default, it is set to <code class="literal">1024x768</code>.
</div><pre class="screen">
ExecStart=/sbin/runuser -l <em class="replaceable"><code>USER</code></em> -c "/usr/bin/vncserver %i -geometry 1280x1024"
@@ -2533,7 +2551,9 @@ Password:
Verify:
</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
The stored password is not encrypted; anyone who has access to the password file can find the plain-text password.
- </div></div></div></li></ol></div><div class="section" id="configuring-vncserver-2users"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">8.1.2.1. Configuring VNC Server for Two Users</h4></div></div></div><div class="para">
+ </div></div></div></li></ol></div><div class="para">
+ Proceed to <a class="xref" href="#s4-starting-vncserver">Section 8.1.3, “Starting VNC Server”</a>.
+ </div><div class="section" id="configuring-vncserver-2users"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">8.1.2.1. Configuring VNC Server for Two Users</h4></div></div></div><div class="para">
If you want to configure more than one user on the same machine, create different template-type service files, one for each user.
</div><div class="procedure"><ol class="1"><li class="step"><div class="para">
Create two service files, for example <code class="filename">vncserver-<em class="replaceable"><code>USER_1</code></em>@.service</code> and <code class="filename">vncserver-<em class="replaceable"><code>USER_2</code></em>@.service</code>. In both these files substitute <em class="replaceable"><code>USER</code></em> with the correct user name.
@@ -2549,18 +2569,18 @@ Verify:
Password:
Verify:
</pre></li></ol></div></div></div><div class="section" id="s4-starting-vncserver"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.3. Starting VNC Server</h3></div></div></div><div class="para">
- To start or enable the service, specify the display number directly in the command. The file configured above works as a template, in which <code class="literal">%i</code> is substituted with the display number by <code class="systemitem">systemd</code>. With a valid number, execute the following command:
+ To start or enable the service, specify the display number directly in the command. The file configured above in <a class="xref" href="#configuring-vncserver">Procedure 8.1, “Configuring the first VNC connection”</a> works as a template, in which <code class="literal">%i</code> is substituted with the display number by <code class="systemitem">systemd</code>. With a valid display number, execute the following command:
</div><pre class="screen">
<code class="command"><code class="computeroutput">~]# </code>systemctl start vncserver@:<em class="replaceable"><code>display_number</code></em>.service</code></pre><div class="para">
You can also enable the service to start automatically at system start. Then, when you log in, <code class="systemitem">vncserver</code> is automatically started. As <code class="systemitem">root</code>, issue a command as follows:
</div><pre class="screen">
<code class="command"><code class="computeroutput">~]# </code>systemctl enable vncserver@:<em class="replaceable"><code>display_number</code></em>.service</code></pre><div class="para">
- At this point, other users are able to use the <code class="systemitem">vncviewer</code> program to connect to the VNC server using the display number and password defined.
- </div><div class="section" id="starting-vncserver-2displays"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">8.1.3.1. Configuring VNC Server for two users and two different displays</h4></div></div></div><div class="para">
+ At this point, other users are able to use a VNC viewer program to connect to the VNC server using the display number and password defined. Provided a graphical desktop is installed, an instance of that desktop will be displayed. It will not be the same instance as that currently displayed on the target machine.
+ </div><div class="section" id="starting-vncserver-2displays"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">8.1.3.1. Configuring VNC Server for Two Users and Two Different Displays</h4></div></div></div><div class="para">
For the two configured VNC servers, vncserver-USER_1 at .service and vncserver-USER_2 at .service, you can enable different display numbers. For example, the following commands will cause a VNC server for USER_1 to start on display 3, and a VNC server for USER_2 to start on display 5:
</div><pre class="screen">
<code class="command"><code class="computeroutput">~]# </code>systemctl start vncserver-USER_1@:3.service</code>
-<code class="command"><code class="computeroutput">~]# </code>systemctl start vncserver-USER_2@:5.service</code></pre></div></div><div class="section" id="terminating-vnc-session"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.4. Terminating a VNC session</h3></div></div></div><div class="para">
+<code class="command"><code class="computeroutput">~]# </code>systemctl start vncserver-USER_2@:5.service</code></pre></div></div><div class="section" id="terminating-vnc-session"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.4. Terminating a VNC Session</h3></div></div></div><div class="para">
Similarly to enabling the <code class="systemitem">vncserver</code> service, you can disable the automatic start of the service at system start:
</div><pre class="screen">
<code class="command"><code class="computeroutput">~]# </code><strong class="userinput"><code>systemctl disable vncserver@:<em class="replaceable"><code>display_number</code></em>.service</code></strong></code></pre><div class="para">
@@ -2569,12 +2589,12 @@ Verify:
<code class="command"><code class="computeroutput">~]# </code><strong class="userinput"><code>systemctl stop vncserver@:<em class="replaceable"><code>display_number</code></em>.service</code></strong></code></pre></div></div><div class="section" id="s5-vnc-viewer"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.2. VNC Viewer</h2></div></div></div><div class="para">
<code class="systemitem">vncviewer</code> is the program which shows the shared graphical user interfaces and controls the server.
</div><div class="para">
- For operating the <code class="systemitem">vncviewer</code>, there is a pop-up menu containing entries which perform various actions such as switching in and out of full-screen mode or quitting the viewer. Alternatively, you can operate <code class="systemitem">vncviewer</code> through the terminal; there is a list of parameters <code class="systemitem">vncviewer</code> can be used with which you obtain by typing <code class="command">vncviewer -h</code> on the command line.
+ For operating the <code class="systemitem">vncviewer</code>, there is a pop-up menu containing entries which perform various actions such as switching in and out of full-screen mode or quitting the viewer. Alternatively, you can operate <code class="systemitem">vncviewer</code> through the terminal. Enter <code class="command">vncviewer -h</code> on the command line to list <code class="systemitem">vncviewer</code>'s parameters.
</div><div class="section" id="installing-vncviewer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.2.1. Installing VNC Viewer</h3></div></div></div><div class="para">
- To install the TigerVNC client, referred to as <span class="application"><strong>vncviewer</strong></span>, issue the following command as <code class="systemitem">root</code>: <pre class="synopsis"><code class="command"><code class="computeroutput">~]# </code><strong class="userinput"><code>yum install tigervnc</code></strong></code></pre>
+ To install the <span class="application"><strong>TigerVNC</strong></span> client, <code class="command">vncviewer</code>>, issue the following command as <code class="systemitem">root</code>: <pre class="synopsis"><code class="command"><code class="computeroutput">~]# </code><strong class="userinput"><code>yum install tigervnc</code></strong></code></pre>
</div></div><div class="section" id="s6-connecting-vnc-viewer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.2.2. Connecting to VNC Server</h3></div></div></div><div class="para">
- Once the VNC server is configured, you can connect to it from any VNC viewer. In order to do so, issue the <code class="command">vncviewer</code> command in the following format: <pre class="synopsis">vncviewer <em class="replaceable"><code>IP_address</code></em>:<em class="replaceable"><code>port_number</code></em></pre>
- </div><div class="example" id="connecting-to-vncserver"><h6>Example 8.1. One Client Connecting to vncserver</h6><div class="example-contents"><div class="para">
+ Once the VNC server is configured, you can connect to it from any VNC viewer. In order to do so, issue the <code class="command">vncviewer</code> command in the following format: <pre class="synopsis">vncviewer <em class="replaceable"><code>address</code></em>:<em class="replaceable"><code>port_number</code></em></pre> Where <em class="replaceable"><code>address</code></em> is an <code class="systemitem">IP</code> or host name.
+ </div><div class="example" id="connecting-to-vncserver"><h6>Example 8.1. One Client Connecting to VNC Server</h6><div class="example-contents"><div class="para">
With the <code class="systemitem">IP</code> address <code class="systemitem">192.168.0.4</code> and display number <span class="emphasis"><em>3</em></span> the command looks as follows:
</div><pre class="programlisting">
<code class="command"><code class="computeroutput">~]$ </code><strong class="userinput"><code>vncviewer 192.168.0.4:3</code></strong></code></pre></div></div><br class="example-break" /><div class="section" id="sec-Configuring_the_Firewall_for_VNC"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">8.2.2.1. Configuring the Firewall for VNC</h4></div></div></div><div class="para">
@@ -2605,7 +2625,7 @@ public (default, active)
rich rules:
rule family="ipv4" source address="192.168.122.116" service name="vnc-server" accept</pre>
</div></li></ol></div><div class="para">
- To open a specific port or range of ports make use of the <code class="option">--list-ports</code> option to the <code class="command">firewall-cmd</code> command Line tool. For example, VNC display <code class="literal">4</code> requires port <code class="literal">5904</code> to be opened for <code class="systemitem">TCP</code> traffic.
+ To open a specific port or range of ports make use of the <code class="option">--add-port</code> option to the <code class="command">firewall-cmd</code> command Line tool. For example, VNC display <code class="literal">4</code> requires port <code class="literal">5904</code> to be opened for <code class="systemitem">TCP</code> traffic.
</div><div class="procedure" id="proc-Opening-Ports_in_firewalld"><h6>Procedure 8.3. Opening Ports in firewalld</h6><ol class="1"><li class="step"><div class="para">
To open a port for <code class="systemitem">TCP</code> traffic in the public zone, issue a command as <code class="systemitem">root</code> as follows:
<pre class="screen">~]# <code class="command">firewall-cmd --zone=public --add-port=5904/tcp</code>
@@ -2618,19 +2638,19 @@ success</pre>
A port can be removed using the <code class="command">firewall-cmd --zone=<em class="replaceable"><code>zone</code></em> --remove-port=<em class="replaceable"><code>number/protocol</code></em></code> command.
</div><div class="para">
For more information on opening and closing ports in <code class="systemitem">firewalld</code>, see the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/">Red Hat Enterprise Linux 7 Security Guide</a>.
- </div></div></div><div class="section" id="s1-using_ssh"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.2.3. Connecting to VNC Server using SSH</h3></div></div></div><div class="para">
+ </div></div></div><div class="section" id="s1-using_ssh"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.2.3. Connecting to VNC Server Using SSH</h3></div></div></div><div class="para">
<acronym class="acronym">VNC</acronym> is a clear text network protocol with no security against possible attacks on the communication. To make the communication secure, you can encrypt your server-client connection by using the <code class="option">-via</code> option. This will create an <code class="systemitem">SSH</code> tunnel between the VNC server and the client.
</div><div class="para">
- The format of the command to encrypt a VNC server-client connection looks as follows:
+ The format of the command to encrypt a VNC server-client connection is as follows:
</div><pre class="screen">
-<code class="command"><code class="computeroutput">~]$ </code><strong class="userinput"><code>vncviewer -via <em class="replaceable"><code>user</code></em>@<em class="replaceable"><code>host</code></em>:<em class="replaceable"><code>display_number</code></em></code></strong></code></pre><div class="example" id="using-via"><h6>Example 8.2. Using the -via option</h6><div class="example-contents"><div class="procedure"><ol class="1"><li class="step"><div class="para">
+<code class="command"><code class="computeroutput">~]$ </code><strong class="userinput"><code>vncviewer -via <em class="replaceable"><code>user</code></em>@<em class="replaceable"><code>host</code></em>:<em class="replaceable"><code>display_number</code></em></code></strong></code></pre><div class="example" id="using-via"><h6>Example 8.2. Using the -via Option</h6><div class="example-contents"><div class="procedure"><ol class="1"><li class="step"><div class="para">
To connect to a VNC server using <code class="systemitem">SSH</code>, enter a command as follows:
</div><pre class="programlisting">
<code class="command"><code class="computeroutput">~]$ </code><strong class="userinput"><code>vncviewer -via USER_2 at 192.168.2.101:3</code></strong></code></pre></li><li class="step"><div class="para">
When you are prompted to, type the password, and confirm by pressing <span class="keycap"><strong>Enter</strong></span>.
</div></li><li class="step"><div class="para">
A window with a remote desktop appears on your screen.
- </div></li></ol></div></div></div><br class="example-break" /><h4 id="bh-Restricting_VNC_access">Restricting VNC access</h4><div class="para">
+ </div></li></ol></div></div></div><br class="example-break" /><h4 id="bh-Restricting_VNC_access">Restricting VNC Access</h4><div class="para">
If you prefer only encrypted connections, you can prevent unencrypted connections altogether by using the <code class="option">-localhost</code> option in the <code class="systemitem">systemd.service</code> file, the ExecStart line:
</div><pre class="screen">ExecStart=/sbin/runuser -l <em class="replaceable"><code>user</code></em> -c "/usr/bin/vncserver -localhost %i"</pre><div class="para">
This will stop <code class="systemitem">vncserver</code> from accepting connections from anything but the local host and port-forwarded connections sent using <code class="systemitem">SSH</code> as a result of the <code class="option">-via</code> option.
@@ -2644,15 +2664,15 @@ success</pre>
<code class="filename">vncviewer(1)</code> — The <acronym class="acronym">VNC</acronym> viewer manual pages.
</div></li><li class="listitem"><div class="para">
<code class="filename">vncpasswd(1)</code> — The <acronym class="acronym">VNC</acronym> password manual pages.
- </div></li></ul></div></div></div></div><div class="part" id="part-Servers"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part IV. Servers</h1></div></div></div><div class="partintro" id="idm225456787600"><div></div><div class="para">
+ </div></li></ul></div></div></div></div><div class="part" id="part-Servers"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part IV. Servers</h1></div></div></div><div class="partintro" id="idm261747130416"><div></div><div class="para">
This part discusses various topics related to servers such as how to set up a web server or share files and directories over a network.
- </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#ch-Web_Servers">9. Web Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-The_Apache_HTTP_Server">9.1. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-changes">9.1.1. Notable Changes</a></span></dt><dt><span class="section"><a href="#s2-apache-version2-migrating">9.1.2. Updating the Configuration</a></span></dt><dt><span class="section"><a href="#s2-apache-running">9.1.3. Running the httpd Service</a></span></dt><dt><span class="section"><a href="#s2-apache-editing">9.1.4. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="#s2-apache-dso">9.1.5. Working with Modules</a></span></dt><dt><span class="section"><a href="#s2-apache-virtualhosts">9.1.6. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="#s2-apache-mod_ssl">9.1.7. Setting Up an SSL S
erver</a></span></dt><dt><span class="section"><a href="#s2-apache-resources">9.1.8. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Mail_Servers">10. Mail Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-email-protocols">10.1. Email Protocols</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-protocols-send">10.1.1. Mail Transport Protocols</a></span></dt><dt><span class="section"><a href="#s2-email-protocols-client">10.1.2. Mail Access Protocols</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-types">10.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-types-mta">10.2.1. Mail Transport Agent</a></span></dt><dt><span class="section"><a href="#s2-email-types-mda">10.2.2. Mail Delivery Agent</a></span></dt><dt><span class="section"><a href="#s2-email-types-mua">10.2.3. Mail User Agent</a></span></dt></dl></dd><dt><span cl
ass="section"><a href="#s1-email-mta">10.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-mta-postfix">10.3.1. Postfix</a></span></dt><dt><span class="section"><a href="#s2-email-mta-sendmail">10.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="#s2-email-mta-fetchmail">10.3.3. Fetchmail</a></span></dt><dt><span class="section"><a href="#s2-email-switchmail">10.3.4. Mail Transport Agent (MTA) Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mda">10.4. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-procmail-configuration">10.4.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="#s2-email-procmail-recipes">10.4.2. Procmail Recipes</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mua">10.5. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-security">10.5.1. Securing
Communication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-additional-resources">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-installed-docs">10.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-email-useful-websites">10.6.2. Useful Websites</a></span></dt><dt><span class="section"><a href="#s2-email-related-books">10.6.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Directory_Servers">11. Directory Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-OpenLDAP">11.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-introduction">11.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-installation">11.1.2. Installing the OpenLDAP Suite</a></span></dt><dt><span class="section"><a href="#s2-ldap-configuration">11.1.3. Configuring an OpenLDAP Server</a></s
pan></dt><dt><span class="section"><a href="#s2-ldap-running">11.1.4. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="#s2-ldap-pam">11.1.5. Configuring a System to Authenticate Using OpenLDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-resources">11.1.6. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-File_and_Print_Servers">12. File and Print Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Samba">12.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="#samba-rgs-overview">12.1.1. Introduction to Samba</a></span></dt><dt><span class="section"><a href="#s2-samba-daemons">12.1.2. Samba Daemons and Related Services</a></span></dt><dt><span class="section"><a href="#s2-samba-connect-share">12.1.3. Connecting to a Samba Share</a></span></dt><dt><span class="section"><a href="#s2-samba-configuring">12.1.4. Configuring a Samba Server</a></span></dt><dt><spa
n class="section"><a href="#s2-samba-startstop">12.1.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="#s2-samba-servers">12.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">12.1.7. Samba Security Modes</a></span></dt><dt><span class="section"><a href="#s2-samba-account-info-dbs">12.1.8. Samba Account Information Databases</a></span></dt><dt><span class="section"><a href="#s2-samba-network-browsing">12.1.9. Samba Network Browsing</a></span></dt><dt><span class="section"><a href="#s2-samba-cups">12.1.10. Samba with CUPS Printing Support</a></span></dt><dt><span class="section"><a href="#s2-samba-programs">12.1.11. Samba Distribution Programs</a></span></dt><dt><span class="section"><a href="#s2-samba-resources">12.1.12. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-FTP">12.2. FTP</a></span></dt><dd><dl><dt
><span class="section"><a href="#s2-ftp-protocol">12.2.1. The File Transfer Protocol</a></span></dt><dt><span class="section"><a href="#s2-ftp-servers">12.2.2. FTP Servers</a></span></dt><dt><span class="section"><a href="#s3-ftp-vsftpd-conf">12.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-start">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf">12.2.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-resources">12.2.6. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Printer_Configuration">12.3. Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Starting_Printer_Config">12.3.1. Starting the Printer Configuration Tool</a></span></dt><dt><span class="section"><a href="#se
c-Setting_Printer">12.3.2. Starting Printer Setup</a></span></dt><dt><span class="section"><a href="#sec-Adding_Other_Printer">12.3.3. Adding a Local Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-jetdirect-printer">12.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="#s1-printing-ipp-printer">12.3.5. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="#sec-printing-LPDLPR-printer">12.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-smb-printer">12.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="#s1-printing-select-model">12.3.8. Selecting the Printer Model and Finishing</a></span></dt><dt><span class="section"><a href="#s1-printing-test-page">12.3.9. Printing a Test Page</a></span></dt><dt><span class="section"><a href="#s1-printing-edit">12.3.10. Modifying Existing Printers</a></span></dt><dt><spa
n class="section"><a href="#s1-printing-additional-resources">12.3.11. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_NTP_Using_the_chrony_Suite">13. Configuring NTP Using the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Introduction_to_the_chrony_Suite">13.1. Introduction to the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-differences_between_ntpd_and_chronyd">13.1.1. Differences Between ntpd and chronyd</a></span></dt><dt><span class="section"><a href="#sect-Choosing_between_NTP_daemon">13.1.2. Choosing Between NTP Daemons</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Understanding_chrony_and-its_configuration">13.2. Understanding chrony and Its Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Understanding_chronyd">13.2.1. Understanding chronyd</a></span></dt><dt><span class="section"><a href="#sect-Un
derstanding_chronyc">13.2.2. Understanding chronyc</a></span></dt><dt><span class="section"><a href="#sect-Understanding_the_chrony_configuration_commands">13.2.3. Understanding the chrony Configuration Commands</a></span></dt><dt><span class="section"><a href="#sect-Security_with_chronyc">13.2.4. Security with chronyc</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Using_chrony">13.3. Using chrony</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Installing_chrony">13.3.1. Installing chrony</a></span></dt><dt><span class="section"><a href="#sect-Checking_the_Status_of_chronyd">13.3.2. Checking the Status of chronyd</a></span></dt><dt><span class="section"><a href="#sect-Starting_chronyd">13.3.3. Starting chronyd</a></span></dt><dt><span class="section"><a href="#sect-Stopping_chronyd">13.3.4. Stopping chronyd</a></span></dt><dt><span class="section"><a href="#sect-Checking_if_chrony_is_synchronized">13.3.5. Checking if chrony is Synchronized<
/a></span></dt><dt><span class="section"><a href="#sect-Manually_Adjusting-the-System_Clock">13.3.6. Manually Adjusting the System Clock</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Setting_up_chrony_for_different_environments">13.4. Setting Up chrony for Different Environments</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">13.4.1. Setting Up chrony for a System Which is Infrequently Connected</a></span></dt><dt><span class="section"><a href="#sect-Setting_up_chrony_for_a_system_in_an_isolated_network">13.4.2. Setting Up chrony for a System in an Isolated Network</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Using_chronyc">13.5. Using chronyc</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Using_chronyc_chronyc_to_control_chronyd">13.5.1. Using chronyc to Control chronyd</a></span></dt><dt><span class="section"><a href="#sect-Using_chronyc
_for_remote_administration">13.5.2. Using chronyc for Remote Administration</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-additional_resources">13.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-chrony-docs-inst">13.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-chrony_Online_Documentation">13.6.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_NTP_Using_ntpd">14. Configuring NTP Using ntpd</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Introduction_to_NTP">14.1. Introduction to NTP</a></span></dt><dt><span class="section"><a href="#s1-NTP_Strata">14.2. NTP Strata</a></span></dt><dt><span class="section"><a href="#s1-Understanding_NTP">14.3. Understanding NTP</a></span></dt><dt><span class="section"><a href="#s1-Understanding_the_Drift_File">14.4. Understanding the Drift File</a></span></dt><dt><span class="s
ection"><a href="#s1-UTC_timezones_and_DST">14.5. UTC, Timezones, and DST</a></span></dt><dt><span class="section"><a href="#s1-Authentication_Options_for_NTP">14.6. Authentication Options for NTP</a></span></dt><dt><span class="section"><a href="#s1-Managing_the_Time_on_Virtual_Machines">14.7. Managing the Time on Virtual Machines</a></span></dt><dt><span class="section"><a href="#s1-Understanding_Leap_Seconds">14.8. Understanding Leap Seconds</a></span></dt><dt><span class="section"><a href="#s1-Understanding_the_ntpd_Configuration_File">14.9. Understanding the ntpd Configuration File</a></span></dt><dt><span class="section"><a href="#s1-Understanding_the_ntpd_Sysconfig_File">14.10. Understanding the ntpd Sysconfig File</a></span></dt><dt><span class="section"><a href="#s1-Disabling_chrony">14.11. Disabling chrony</a></span></dt><dt><span class="section"><a href="#s1-Checking_if_the_NTP_Daemon_is_Installed">14.12. Checking if the NTP Daemon is Installed</a></span></dt><dt>
<span class="section"><a href="#s1-Installing_the_NTP_Daemon_ntpd">14.13. Installing the NTP Daemon (ntpd)</a></span></dt><dt><span class="section"><a href="#s1-Checking_the_status_of_NTP">14.14. Checking the Status of NTP</a></span></dt><dt><span class="section"><a href="#s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets">14.15. Configure the Firewall to Allow Incoming NTP Packets</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Change_the_firewall_settings">14.15.1. Change the Firewall Settings</a></span></dt><dt><span class="section"><a href="#s2-Open_Ports_in_the_firewall_for_ntp_packets">14.15.2. Open Ports in the Firewall for NTP Packets</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-Configure_ntpdate_Servers">14.16. Configure ntpdate Servers</a></span></dt><dt><span class="section"><a href="#s1-Configure_NTP">14.17. Configure NTP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Configure_Access_Control_to_an_NTP_service
">14.17.1. Configure Access Control to an NTP Service</a></span></dt><dt><span class="section"><a href="#s2_Configure_Rate_Limiting_Access_to_an_NTP_Service">14.17.2. Configure Rate Limiting Access to an NTP Service</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Peer_Address">14.17.3. Adding a Peer Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Server_Address">14.17.4. Adding a Server Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Broadcast_or_Mutlticast_Server_Address">14.17.5. Adding a Broadcast or Multicast Server Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Manycast_Client_Address">14.17.6. Adding a Manycast Client Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Broadcastclient_Address">14.17.7. Adding a Broadcast Client Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_manycastserver_Address">14.17.8. Adding a Manycast Server Address</a><
/span></dt><dt><span class="section"><a href="#s2_Adding_a_multicastclient_Address">14.17.9. Adding a Multicast Client Address</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_burst_option">14.17.10. Configuring the Burst Option</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_iburst_Option">14.17.11. Configuring the iburst Option</a></span></dt><dt><span class="section"><a href="#s2_Configuring_Symmetric_Authentication_Using_a_Key">14.17.12. Configuring Symmetric Authentication Using a Key</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_Poll_Interval">14.17.13. Configuring the Poll Interval</a></span></dt><dt><span class="section"><a href="#s2_Configuring_Server_Preference">14.17.14. Configuring Server Preference</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_Time-To-Live_for_NTP_Packets">14.17.15. Configuring the Time-to-Live for NTP Packets</a></span></dt><dt><span class="section"><a hr
ef="#s2_Configuring_The_Version_of_NTP_to_use">14.17.16. Configuring the NTP Version to Use</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-Configuring_the_Hardware_Clock_update">14.18. Configuring the Hardware Clock Update</a></span></dt><dt><span class="section"><a href="#s1-Configuring_Clock_Sources">14.19. Configuring Clock Sources</a></span></dt><dt><span class="section"><a href="#s1-ntpd_additional-resources">14.20. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ntpd-docs-inst">14.20.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-ntpd_useful-websites">14.20.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_PTP_Using_ptp4l">15. Configuring PTP Using ptp4l</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Introduction_to_PTP">15.1. Introduction to PTP</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Unders
tanding_PTP">15.1.1. Understanding PTP</a></span></dt><dt><span class="section"><a href="#sec-Advantages_of_PTP">15.1.2. Advantages of PTP</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_PTP">15.2. Using PTP</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_for_Driver_and_Hardware_Support">15.2.1. Checking for Driver and Hardware Support</a></span></dt><dt><span class="section"><a href="#sec-Installing_PTP">15.2.2. Installing PTP</a></span></dt><dt><span class="section"><a href="#sec-Starting_ptp4l">15.2.3. Starting ptp4l</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Specifying_a_Configuration_File">15.3. Specifying a Configuration File</a></span></dt><dt><span class="section"><a href="#sec-Using_the_PTP_Management_Client">15.4. Using the PTP Management Client</a></span></dt><dt><span class="section"><a href="#sec-Synchronizing_the_Clocks">15.5. Synchronizing the Clocks</a></span></dt><dt><span class="section"><
a href="#sec-Verifying_Time_Synchronization">15.6. Verifying Time Synchronization</a></span></dt><dt><span class="section"><a href="#sec-Serving_PTP_Time_with_NTP">15.7. Serving PTP Time with NTP</a></span></dt><dt><span class="section"><a href="#sec-Serving_NTP_Time_with_PTP">15.8. Serving NTP Time with PTP</a></span></dt><dt><span class="section"><a href="#sec-Improving_Accuracy">15.9. Improving Accuracy</a></span></dt><dt><span class="section"><a href="#sec-PTP_additional_resources">15.10. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-PTP-docs-inst">15.10.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-PTP_useful-websites">15.10.2. Useful Websites</a></span></dt></dl></dd></dl></dd></dl></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 9. Web Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt>
<span class="section"><a href="#s1-The_Apache_HTTP_Server">9.1. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-changes">9.1.1. Notable Changes</a></span></dt><dt><span class="section"><a href="#s2-apache-version2-migrating">9.1.2. Updating the Configuration</a></span></dt><dt><span class="section"><a href="#s2-apache-running">9.1.3. Running the httpd Service</a></span></dt><dt><span class="section"><a href="#s2-apache-editing">9.1.4. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="#s2-apache-dso">9.1.5. Working with Modules</a></span></dt><dt><span class="section"><a href="#s2-apache-virtualhosts">9.1.6. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="#s2-apache-mod_ssl">9.1.7. Setting Up an SSL Server</a></span></dt><dt><span class="section"><a href="#s2-apache-resources">9.1.8. Additional Resources</a></span></dt></dl></dd></dl></div><a id="idm225467569536" class="inde
xterm"></a><a id="idm225437570992" class="indexterm"></a><div class="para">
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="#ch-Web_Servers">9. Web Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-The_Apache_HTTP_Server">9.1. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-changes">9.1.1. Notable Changes</a></span></dt><dt><span class="section"><a href="#s2-apache-version2-migrating">9.1.2. Updating the Configuration</a></span></dt><dt><span class="section"><a href="#s2-apache-running">9.1.3. Running the httpd Service</a></span></dt><dt><span class="section"><a href="#s2-apache-editing">9.1.4. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="#s2-apache-dso">9.1.5. Working with Modules</a></span></dt><dt><span class="section"><a href="#s2-apache-virtualhosts">9.1.6. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="#s2-apache-mod_ssl">9.1.7. Setting Up an SSL S
erver</a></span></dt><dt><span class="section"><a href="#s2-apache-resources">9.1.8. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Mail_Servers">10. Mail Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-email-protocols">10.1. Email Protocols</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-protocols-send">10.1.1. Mail Transport Protocols</a></span></dt><dt><span class="section"><a href="#s2-email-protocols-client">10.1.2. Mail Access Protocols</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-types">10.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-types-mta">10.2.1. Mail Transport Agent</a></span></dt><dt><span class="section"><a href="#s2-email-types-mda">10.2.2. Mail Delivery Agent</a></span></dt><dt><span class="section"><a href="#s2-email-types-mua">10.2.3. Mail User Agent</a></span></dt></dl></dd><dt><span cl
ass="section"><a href="#s1-email-mta">10.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-mta-postfix">10.3.1. Postfix</a></span></dt><dt><span class="section"><a href="#s2-email-mta-sendmail">10.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="#s2-email-mta-fetchmail">10.3.3. Fetchmail</a></span></dt><dt><span class="section"><a href="#s2-email-switchmail">10.3.4. Mail Transport Agent (MTA) Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mda">10.4. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-procmail-configuration">10.4.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="#s2-email-procmail-recipes">10.4.2. Procmail Recipes</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mua">10.5. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-security">10.5.1. Securing
Communication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-additional-resources">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-installed-docs">10.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-email-useful-websites">10.6.2. Useful Websites</a></span></dt><dt><span class="section"><a href="#s2-email-related-books">10.6.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Directory_Servers">11. Directory Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-OpenLDAP">11.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-introduction">11.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-installation">11.1.2. Installing the OpenLDAP Suite</a></span></dt><dt><span class="section"><a href="#s2-ldap-configuration">11.1.3. Configuring an OpenLDAP Server</a></s
pan></dt><dt><span class="section"><a href="#s2-selinux-openldap">11.1.4. SELinux Policy for Applications Using LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-running">11.1.5. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="#s2-ldap-pam">11.1.6. Configuring a System to Authenticate Using OpenLDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-resources">11.1.7. Additional Resources</a></span></dt><dt><span class="section"><a href="#s3-ldap-related-books">11.1.8. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-File_and_Print_Servers">12. File and Print Servers</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Samba">12.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="#samba-rgs-overview">12.1.1. Introduction to Samba</a></span></dt><dt><span class="section"><a href="#s2-samba-daemons">12.1.2. Samba Daemons and Related Services</a></span></dt><dt><spa
n class="section"><a href="#s2-samba-connect-share">12.1.3. Connecting to a Samba Share</a></span></dt><dt><span class="section"><a href="#s2-samba-configuring">12.1.4. Configuring a Samba Server</a></span></dt><dt><span class="section"><a href="#s2-samba-startstop">12.1.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="#s2-samba-servers">12.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">12.1.7. Samba Security Modes</a></span></dt><dt><span class="section"><a href="#s2-samba-account-info-dbs">12.1.8. Samba Account Information Databases</a></span></dt><dt><span class="section"><a href="#s2-samba-network-browsing">12.1.9. Samba Network Browsing</a></span></dt><dt><span class="section"><a href="#s2-samba-cups">12.1.10. Samba with CUPS Printing Support</a></span></dt><dt><span class="section"><a href="#s2-samba-programs">12.1.11. Samba Distribut
ion Programs</a></span></dt><dt><span class="section"><a href="#s2-samba-resources">12.1.12. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-FTP">12.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-protocol">12.2.1. The File Transfer Protocol</a></span></dt><dt><span class="section"><a href="#s2-ftp-servers">12.2.2. FTP Servers</a></span></dt><dt><span class="section"><a href="#s3-ftp-vsftpd-conf">12.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-start">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf">12.2.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-resources">12.2.6. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Printer_Configuration
">12.3. Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Starting_Printer_Config">12.3.1. Starting the Printers Configuration Tool</a></span></dt><dt><span class="section"><a href="#sec-Setting_Printer">12.3.2. Starting Printer Setup</a></span></dt><dt><span class="section"><a href="#sec-Adding_Other_Printer">12.3.3. Adding a Local Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-jetdirect-printer">12.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="#s1-printing-ipp-printer">12.3.5. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="#sec-printing-LPDLPR-printer">12.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-smb-printer">12.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="#s1-printing-select-model">12.3.8. Selecting the Printer Model and Finishing</a></span></
dt><dt><span class="section"><a href="#s1-printing-test-page">12.3.9. Printing a Test Page</a></span></dt><dt><span class="section"><a href="#s1-printing-edit">12.3.10. Modifying Existing Printers</a></span></dt><dt><span class="section"><a href="#s1-printing-additional-resources">12.3.11. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_NTP_Using_the_chrony_Suite">13. Configuring NTP Using the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Introduction_to_the_chrony_Suite">13.1. Introduction to the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-differences_between_ntpd_and_chronyd">13.1.1. Differences Between ntpd and chronyd</a></span></dt><dt><span class="section"><a href="#sect-Choosing_between_NTP_daemon">13.1.2. Choosing Between NTP Daemons</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Understanding_chrony_and-its_configuration">13.2
. Understanding chrony and Its Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Understanding_chronyd">13.2.1. Understanding chronyd</a></span></dt><dt><span class="section"><a href="#sect-Understanding_chronyc">13.2.2. Understanding chronyc</a></span></dt><dt><span class="section"><a href="#sect-Understanding_the_chrony_configuration_commands">13.2.3. Understanding the chrony Configuration Commands</a></span></dt><dt><span class="section"><a href="#sect-Security_with_chronyc">13.2.4. Security with chronyc</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Using_chrony">13.3. Using chrony</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Installing_chrony">13.3.1. Installing chrony</a></span></dt><dt><span class="section"><a href="#sect-Checking_the_Status_of_chronyd">13.3.2. Checking the Status of chronyd</a></span></dt><dt><span class="section"><a href="#sect-Starting_chronyd">13.3.3. Starting chronyd</a></span></dt
><dt><span class="section"><a href="#sect-Stopping_chronyd">13.3.4. Stopping chronyd</a></span></dt><dt><span class="section"><a href="#sect-Checking_if_chrony_is_synchronized">13.3.5. Checking if chrony is Synchronized</a></span></dt><dt><span class="section"><a href="#sect-Manually_Adjusting-the-System_Clock">13.3.6. Manually Adjusting the System Clock</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Setting_up_chrony_for_different_environments">13.4. Setting Up chrony for Different Environments</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">13.4.1. Setting Up chrony for a System Which is Infrequently Connected</a></span></dt><dt><span class="section"><a href="#sect-Setting_up_chrony_for_a_system_in_an_isolated_network">13.4.2. Setting Up chrony for a System in an Isolated Network</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-Using_chronyc">13.5. Using chro
nyc</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-Using_chronyc_chronyc_to_control_chronyd">13.5.1. Using chronyc to Control chronyd</a></span></dt><dt><span class="section"><a href="#sect-Using_chronyc_for_remote_administration">13.5.2. Using chronyc for Remote Administration</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-additional_resources">13.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-chrony-docs-inst">13.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-chrony_Online_Documentation">13.6.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_NTP_Using_ntpd">14. Configuring NTP Using ntpd</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-Introduction_to_NTP">14.1. Introduction to NTP</a></span></dt><dt><span class="section"><a href="#s1-NTP_Strata">14.2. NTP Strata</a></span></dt><dt><span clas
s="section"><a href="#s1-Understanding_NTP">14.3. Understanding NTP</a></span></dt><dt><span class="section"><a href="#s1-Understanding_the_Drift_File">14.4. Understanding the Drift File</a></span></dt><dt><span class="section"><a href="#s1-UTC_timezones_and_DST">14.5. UTC, Timezones, and DST</a></span></dt><dt><span class="section"><a href="#s1-Authentication_Options_for_NTP">14.6. Authentication Options for NTP</a></span></dt><dt><span class="section"><a href="#s1-Managing_the_Time_on_Virtual_Machines">14.7. Managing the Time on Virtual Machines</a></span></dt><dt><span class="section"><a href="#s1-Understanding_Leap_Seconds">14.8. Understanding Leap Seconds</a></span></dt><dt><span class="section"><a href="#s1-Understanding_the_ntpd_Configuration_File">14.9. Understanding the ntpd Configuration File</a></span></dt><dt><span class="section"><a href="#s1-Understanding_the_ntpd_Sysconfig_File">14.10. Understanding the ntpd Sysconfig File</a></span></dt><dt><span class="secti
on"><a href="#s1-Disabling_chrony">14.11. Disabling chrony</a></span></dt><dt><span class="section"><a href="#s1-Checking_if_the_NTP_Daemon_is_Installed">14.12. Checking if the NTP Daemon is Installed</a></span></dt><dt><span class="section"><a href="#s1-Installing_the_NTP_Daemon_ntpd">14.13. Installing the NTP Daemon (ntpd)</a></span></dt><dt><span class="section"><a href="#s1-Checking_the_status_of_NTP">14.14. Checking the Status of NTP</a></span></dt><dt><span class="section"><a href="#s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets">14.15. Configure the Firewall to Allow Incoming NTP Packets</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Change_the_firewall_settings">14.15.1. Change the Firewall Settings</a></span></dt><dt><span class="section"><a href="#s2-Open_Ports_in_the_firewall_for_ntp_packets">14.15.2. Open Ports in the Firewall for NTP Packets</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-Configure_ntpdate_Servers">14.16.
Configure ntpdate Servers</a></span></dt><dt><span class="section"><a href="#s1-Configure_NTP">14.17. Configure NTP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Configure_Access_Control_to_an_NTP_service">14.17.1. Configure Access Control to an NTP Service</a></span></dt><dt><span class="section"><a href="#s2_Configure_Rate_Limiting_Access_to_an_NTP_Service">14.17.2. Configure Rate Limiting Access to an NTP Service</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Peer_Address">14.17.3. Adding a Peer Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Server_Address">14.17.4. Adding a Server Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Broadcast_or_Mutlticast_Server_Address">14.17.5. Adding a Broadcast or Multicast Server Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_Manycast_Client_Address">14.17.6. Adding a Manycast Client Address</a></span></dt><dt><span class="section"><a
href="#s2_Adding_a_Broadcastclient_Address">14.17.7. Adding a Broadcast Client Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_manycastserver_Address">14.17.8. Adding a Manycast Server Address</a></span></dt><dt><span class="section"><a href="#s2_Adding_a_multicastclient_Address">14.17.9. Adding a Multicast Client Address</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_burst_option">14.17.10. Configuring the Burst Option</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_iburst_Option">14.17.11. Configuring the iburst Option</a></span></dt><dt><span class="section"><a href="#s2_Configuring_Symmetric_Authentication_Using_a_Key">14.17.12. Configuring Symmetric Authentication Using a Key</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_Poll_Interval">14.17.13. Configuring the Poll Interval</a></span></dt><dt><span class="section"><a href="#s2_Configuring_Server_Preference">14.17.14. Configuring
Server Preference</a></span></dt><dt><span class="section"><a href="#s2_Configuring_the_Time-To-Live_for_NTP_Packets">14.17.15. Configuring the Time-to-Live for NTP Packets</a></span></dt><dt><span class="section"><a href="#s2_Configuring_The_Version_of_NTP_to_use">14.17.16. Configuring the NTP Version to Use</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-Configuring_the_Hardware_Clock_update">14.18. Configuring the Hardware Clock Update</a></span></dt><dt><span class="section"><a href="#s1-Configuring_Clock_Sources">14.19. Configuring Clock Sources</a></span></dt><dt><span class="section"><a href="#s1-ntpd_additional-resources">14.20. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ntpd-docs-inst">14.20.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-ntpd_useful-websites">14.20.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Configuring_PTP_Usin
g_ptp4l">15. Configuring PTP Using ptp4l</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Introduction_to_PTP">15.1. Introduction to PTP</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Understanding_PTP">15.1.1. Understanding PTP</a></span></dt><dt><span class="section"><a href="#sec-Advantages_of_PTP">15.1.2. Advantages of PTP</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_PTP">15.2. Using PTP</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_for_Driver_and_Hardware_Support">15.2.1. Checking for Driver and Hardware Support</a></span></dt><dt><span class="section"><a href="#sec-Installing_PTP">15.2.2. Installing PTP</a></span></dt><dt><span class="section"><a href="#sec-Starting_ptp4l">15.2.3. Starting ptp4l</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Specifying_a_Configuration_File">15.3. Specifying a Configuration File</a></span></dt><dt><span class="section"><a href="#sec-Using
_the_PTP_Management_Client">15.4. Using the PTP Management Client</a></span></dt><dt><span class="section"><a href="#sec-Synchronizing_the_Clocks">15.5. Synchronizing the Clocks</a></span></dt><dt><span class="section"><a href="#sec-Verifying_Time_Synchronization">15.6. Verifying Time Synchronization</a></span></dt><dt><span class="section"><a href="#sec-Serving_PTP_Time_with_NTP">15.7. Serving PTP Time with NTP</a></span></dt><dt><span class="section"><a href="#sec-Serving_NTP_Time_with_PTP">15.8. Serving NTP Time with PTP</a></span></dt><dt><span class="section"><a href="#sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster">15.9. Synchronize to PTP or NTP Time Using timemaster</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Starting_timemaster_as_a_Service">15.9.1. Starting timemaster as a Service</a></span></dt><dt><span class="section"><a href="#sec-Understanding_the_timemaster_Configuration_File">15.9.2. Understanding the timemaster Configuration File</a>
</span></dt><dt><span class="section"><a href="#sec-Configuring_timemaster_Options">15.9.3. Configuring timemaster Options</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Improving_Accuracy">15.10. Improving Accuracy</a></span></dt><dt><span class="section"><a href="#sec-PTP_additional_resources">15.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-PTP-docs-inst">15.11.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-PTP_useful-websites">15.11.2. Useful Websites</a></span></dt></dl></dd></dl></dd></dl></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 9. Web Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-The_Apache_HTTP_Server">9.1. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-apache-changes">9.1.1. Nota
ble Changes</a></span></dt><dt><span class="section"><a href="#s2-apache-version2-migrating">9.1.2. Updating the Configuration</a></span></dt><dt><span class="section"><a href="#s2-apache-running">9.1.3. Running the httpd Service</a></span></dt><dt><span class="section"><a href="#s2-apache-editing">9.1.4. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="#s2-apache-dso">9.1.5. Working with Modules</a></span></dt><dt><span class="section"><a href="#s2-apache-virtualhosts">9.1.6. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="#s2-apache-mod_ssl">9.1.7. Setting Up an SSL Server</a></span></dt><dt><span class="section"><a href="#s2-apache-resources">9.1.8. Additional Resources</a></span></dt></dl></dd></dl></div><a id="idm261723129088" class="indexterm"></a><a id="idm261723126944" class="indexterm"></a><div class="para">
A <em class="firstterm">web server</em> is a network service that serves content to a client over the web. This typically means web pages, but any other documents can be served as well. Web servers are also known as HTTP servers, as they use the <em class="firstterm">hypertext transport protocol</em> (<acronym class="acronym">HTTP</acronym>).
- </div><div xml:lang="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">9.1. The Apache HTTP Server</h2></div></div></div><a id="idm225467570976" class="indexterm"></a><div class="para">
+ </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">9.1. The Apache HTTP Server</h2></div></div></div><a id="idm261745207712" class="indexterm"></a><div class="para">
The web server available in Fedora is the Apache HTTP server daemon, <code class="systemitem">httpd</code>, an open source web server developed by the <a href="http://www.apache.org/">Apache Software Foundation</a>. In Fedora 19 the Apache server was updated to <span class="application"><strong>Apache HTTP Server 2.4</strong></span>. This section describes the basic configuration of the <code class="systemitem">httpd</code> service, and covers some advanced topics such as adding server modules, setting up virtual hosts, or configuring the secure HTTP server.
</div><div class="para">
There are important differences between the Apache HTTP Server 2.4 and version 2.2, and if you are upgrading from a release prior to Fedora 19, you will need to update the <code class="systemitem">httpd</code> service configuration accordingly. This section reviews some of the newly added features, outlines important changes, and guides you through the update of older configuration files.
- </div><div class="section" id="s2-apache-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.1. Notable Changes</h3></div></div></div><a id="idm225451944320" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-apache-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.1. Notable Changes</h3></div></div></div><a id="idm261746538080" class="indexterm"></a><div class="para">
The Apache HTTP Server version 2.4 has the following changes compared to version 2.2:
</div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">httpd Service Control</span></dt><dd><div class="para">
With the migration away from SysV init scripts, server administrators should switch to using the <code class="command">apachectl</code> and <code class="command">systemctl</code> commands to control the service, in place of the <code class="command">service</code> command. The following examples are specific to the <code class="systemitem">httpd</code> service.
@@ -2715,14 +2735,14 @@ success</pre>
</div></dd><dt class="varlistentry"><span class="term">mod_authz_ldap</span></dt><dd><div class="para">
<span class="application"><strong>httpd 2.4</strong></span> provides LDAP support in sub-package <span class="package">mod_ldap</span> using <span class="application"><strong>mod_authnz_ldap</strong></span>.
</div></dd></dl></div>
- </div></dd></dl></div></div><div class="section" id="s2-apache-version2-migrating"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.2. Updating the Configuration</h3></div></div></div><a id="idm225468707488" class="indexterm"></a><div class="para">
+ </div></dd></dl></div></div><div class="section" id="s2-apache-version2-migrating"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.2. Updating the Configuration</h3></div></div></div><a id="idm261755192736" class="indexterm"></a><div class="para">
To update the configuration files from the Apache HTTP Server version 2.2, take the following steps:
</div><div class="procedure"><ol class="1"><li class="step"><div class="para">
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="idm225412593200" class="indexterm"></a>
+ <a id="idm261755485504" 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.
@@ -2736,19 +2756,19 @@ Syntax OK</pre><div class="para">
</div><pre class="screen">~]# <code class="command">yum install httpd</code></pre><div class="para">
For more information on the concept of targets and how to manage system services in Fedora in general, see
<a class="xref" href="#ch-Services_and_Daemons">Chapter 6, <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">9.1.3.1. Starting the Service</h4></div></div></div><a id="idm225444234064" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-apache-running-starting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.3.1. Starting the Service</h4></div></div></div><a id="idm261649863744" 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 boot time, use the following command:
</div><pre class="screen">~]# <code class="command">systemctl enable httpd.service</code>
ln -s '/usr/lib/systemd/system/httpd.service' '/etc/systemd/system/multi-user.target.wants/httpd.service'</pre><div class="note"><div class="admonition_header"><h2>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">9.1.3.2. Stopping the Service</h4></div></div></div><a id="idm225444236752" class="indexterm"></a><div class="para">
+ </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">9.1.3.2. Stopping the Service</h4></div></div></div><a id="idm261757650912" 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 boot time, type:
</div><pre class="screen">~]# <code class="command">systemctl disable httpd.service</code>
-rm '/etc/systemd/system/multi-user.target.wants/httpd.service'</pre></div><div class="section" id="s3-apache-running-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.3.3. Restarting the Service</h4></div></div></div><a id="idm225446303360" class="indexterm"></a><div class="para">
+rm '/etc/systemd/system/multi-user.target.wants/httpd.service'</pre></div><div class="section" id="s3-apache-running-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.3.3. Restarting the Service</h4></div></div></div><a id="idm261750649648" class="indexterm"></a><div class="para">
There are three different ways to restart a running <code class="systemitem">httpd</code> service:
</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
To restart the service completely, enter the following command as <code class="systemitem">root</code>:
@@ -2764,7 +2784,7 @@ rm '/etc/systemd/system/multi-user.target.wants/httpd.service'</pre></div><div c
This causes the running <code class="systemitem">httpd</code> service to reload its configuration file. Any requests currently being processed will continue to use the old configuration.
</div></li></ol></div><div class="para">
- </div></div><div class="section" id="s3-apache-running-status"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.3.4. Verifying the Service Status</h4></div></div></div><a id="idm225503971344" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-apache-running-status"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.3.4. Verifying the Service Status</h4></div></div></div><a id="idm261691820096" class="indexterm"></a><div class="para">
To verify that the <code class="systemitem">httpd</code> service is running, type the following at a shell prompt:
</div><pre class="screen">~]# <code class="command">systemctl is-active httpd.service</code>
active</pre></div></div><div class="section" id="s2-apache-editing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.4. Editing the Configuration Files</h3></div></div></div><div class="para">
@@ -2774,25 +2794,25 @@ active</pre></div></div><div class="section" id="s2-apache-editing"><div class="
</th><th class="">
Description
</th></tr></thead><tbody><tr><td class="">
- <a id="idm225479909392" class="indexterm"></a>
+ <a id="idm261734485552" class="indexterm"></a>
<code class="filename">/etc/httpd/conf/httpd.conf</code>
</td><td class="">
The main configuration file.
</td></tr><tr><td class="">
- <a id="idm225479913872" class="indexterm"></a>
+ <a id="idm261729420480" class="indexterm"></a>
<code class="filename">/etc/httpd/conf.d/</code>
</td><td class="">
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. See <a class="xref" href="#s3-apache-running-restarting">Section 9.1.3.3, “Restarting the Service”</a> for more information on how to restart the <code class="systemitem">httpd</code> service.
- </div><a id="idm225500884832" class="indexterm"></a><div class="para">
+ </div><a id="idm261755211744" 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">apachectl configtest</code>
Syntax OK</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">9.1.4.1. Common httpd.conf Directives</h4></div></div></div><a id="idm225477620096" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-apache-httpdconf-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.4.1. Common httpd.conf Directives</h4></div></div></div><a id="idm261754378688" 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 class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225407050032" class="indexterm"></a>
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261721328976" 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>>
@@ -2807,7 +2827,7 @@ Syntax OK</pre><div class="para">
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="idm225457998624" class="indexterm"></a>
+</Directory></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261715093520" 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>>
@@ -2817,7 +2837,7 @@ Syntax OK</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 9.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="idm225481426512" class="indexterm"></a>
+</IfDefine></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261722149472" 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>>
@@ -2828,7 +2848,7 @@ Syntax OK</pre><div class="para">
</div><div class="example" id="example-apache-httpdconf-ifmodule"><h6>Example 9.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="idm225463165664" class="indexterm"></a>
+</IfModule></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261728055600" 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>>
@@ -2841,7 +2861,7 @@ Syntax OK</pre><div class="para">
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="idm225449315184" class="indexterm"></a>
+</Location></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261729606256" 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>>
@@ -2853,7 +2873,7 @@ Syntax OK</pre><div class="para">
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="idm225463409520" class="indexterm"></a>
+</Proxy></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261728844320" 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>]…>
@@ -2879,12 +2899,12 @@ Syntax OK</pre><div class="para">
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="idm225435825344" class="indexterm"></a>
+</VirtualHost></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261758369312" 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="idm225461949184" class="indexterm"></a><a id="idm225461951584" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">AccessFileName <em class="replaceable"><code>filename</code></em>…</pre><a id="idm261787660528" class="indexterm"></a><a id="idm261633518784" 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="idm225463362544" class="indexterm"></a><a id="idm225463364304" class="indexterm"></a><div class="para">
+ </div><a id="idm261633522704" class="indexterm"></a><a id="idm261709012592" 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 9.7. Using the AccessFileName directive</h6><div class="example-contents"><pre class="programlisting">AccessFileName .htaccess
@@ -2892,31 +2912,31 @@ Syntax OK</pre><div class="para">
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="idm225499509392" class="indexterm"></a>
+</Files></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261705850544" 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 9.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="idm225426301968" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-action"><h6>Example 9.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="idm261759962080" 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 9.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="idm225470550256" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-adddescription"><h6>Example 9.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="idm261748388848" 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 9.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="idm225501393072" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-addencoding"><h6>Example 9.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="idm261751547424" 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 9.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="idm225474038048" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-addhandler"><h6>Example 9.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="idm261739787168" 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">
@@ -2933,34 +2953,34 @@ Syntax OK</pre><div class="para">
<code class="option">^^BLANKICON^^</code>
</td><td class="">
Represents a blank line.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-addicon"><h6>Example 9.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="idm225474050160" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-addicon"><h6>Example 9.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="idm261745883040" 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 9.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="idm225457254976" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-addiconbyencoding"><h6>Example 9.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="idm261693902320" 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 9.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="idm225471255600" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-addiconbytype"><h6>Example 9.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="idm261750638112" 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 9.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="idm225451374112" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-addlanguage"><h6>Example 9.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="idm261748288976" 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 9.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="idm225483185648" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-addtype"><h6>Example 9.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="idm261738784192" 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="idm225451638864" class="indexterm"></a><div class="para">
+ </div><a id="idm261735254224" 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 9.17. Using the Alias directive</h6><div class="example-contents"><pre class="programlisting">Alias /icons/ /var/www/icons/
@@ -2969,13 +2989,13 @@ Syntax OK</pre><div class="para">
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="idm225460280016" class="indexterm"></a>
+<Directory></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261722115968" 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 9.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="idm225499137888" class="indexterm"></a>
- <code class="option">AllowOverride</code> </span></dt><dd><a id="idm225499141536" class="indexterm"></a><a id="idm225407070576" class="indexterm"></a><div class="para">
+ </div><div class="example" id="example-apache-httpdconf-allow"><h6>Example 9.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="idm261722115808" class="indexterm"></a>
+ <code class="option">AllowOverride</code> </span></dt><dd><a id="idm261700389920" class="indexterm"></a><a id="idm261700391648" 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 9.4, “Available AllowOverride options”</a>.
@@ -3011,24 +3031,24 @@ Syntax OK</pre><div class="para">
<code class="option">Options</code>[<span class="optional">=<em class="replaceable"><code>option</code></em>,…</span>]
</td><td class="">
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 9.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="idm225462228880" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-allowoverride"><h6>Example 9.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="idm261755162976" 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 9.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="idm225455326960" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-browsermatch"><h6>Example 9.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="idm261632682688" 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 9.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="idm225464785248" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-cachedefaultexpire"><h6>Example 9.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="idm261756805504" 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 9.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="idm225407106736" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-cachedisable"><h6>Example 9.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="idm261737259120" 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">
@@ -3049,17 +3069,17 @@ Syntax OK</pre><div class="para">
<code class="option">fd</code>
</td><td class="">
The file descriptor cache.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-cacheenable"><h6>Example 9.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="idm225445096112" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-cacheenable"><h6>Example 9.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="idm261744458736" 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 9.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="idm225457250752" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-cachelastmodifiedfactor"><h6>Example 9.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="idm261757410064" 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 9.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="idm225426407568" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-cachemaxexpire"><h6>Example 9.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="idm261681180496" 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">
@@ -3076,53 +3096,53 @@ Syntax OK</pre><div class="para">
<code class="option">Off</code>
</td><td class="">
Disables caching the content-negotiated documents.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-cachenegotiateddocs"><h6>Example 9.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="idm225454644928" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-cachenegotiateddocs"><h6>Example 9.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="idm261694515280" 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="idm225460257664" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">CacheRoot <em class="replaceable"><code>directory</code></em></pre><a id="idm261709399984" 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 9.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="idm225401675312" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-cacheroot"><h6>Example 9.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="idm261715627072" 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="idm225445343552" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">CustomLog <em class="replaceable"><code>path</code></em> <em class="replaceable"><code>format</code></em></pre><a id="idm261754978416" 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 9.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="idm225443294256" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-customlog"><h6>Example 9.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="idm261726705568" 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 9.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="idm225459916320" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-defaulticon"><h6>Example 9.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="idm261730250352" 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 9.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="idm225459943744" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-defaulttype"><h6>Example 9.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="idm261786850224" 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 9.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="idm225471083504" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-deny"><h6>Example 9.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="idm261784813296" 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 9.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="idm225443464784" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-directoryindex"><h6>Example 9.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="idm261712911600" 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="idm225443469520" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">DocumentRoot <em class="replaceable"><code>directory</code></em></pre><a id="idm261737200640" 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 9.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="idm225356837376" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-documentroot"><h6>Example 9.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="idm261757697280" 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 9.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="idm225463864176" class="indexterm"></a>
+ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261737203488" 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="idm225411839456" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">ErrorLog <em class="replaceable"><code>path</code></em></pre><a id="idm261752400000" 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 9.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="idm225496245968" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-errorlog"><h6>Example 9.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="idm261709074064" 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">
@@ -3139,19 +3159,19 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">Off</code>
</td><td class="">
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 9.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="idm225402391760" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-extendedstatus"><h6>Example 9.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="idm261756030464" 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 9.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="idm225462270976" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-group"><h6>Example 9.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="idm261759053680" 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 9.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="idm225442122512" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-headername"><h6>Example 9.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="idm261680890832" 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">
@@ -3174,17 +3194,17 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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 9.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="idm225415027056" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-hostnamelookups"><h6>Example 9.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="idm261722013648" 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="idm225414975552" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">Include <em class="replaceable"><code>filename</code></em></pre><a id="idm261733393200" 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 9.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="idm225449131120" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-include"><h6>Example 9.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="idm261713852752" 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 9.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="idm225450541264" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-indexignore"><h6>Example 9.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="idm261680347120" 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">
@@ -3289,7 +3309,7 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">XHTML</code>
</td><td class="">
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 9.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="idm225458986240" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-indexoptions"><h6>Example 9.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="idm261700262144" 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">
@@ -3308,33 +3328,33 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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 9.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="idm225463717536" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-keepalive"><h6>Example 9.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="idm261756002656" 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 9.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="idm225473150144" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-keepalivetimeout"><h6>Example 9.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="idm261721370192" 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 9.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="idm225445471664" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-languagepriority"><h6>Example 9.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="idm261740651920" 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 9.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="idm225474275296" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-listen"><h6>Example 9.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="idm261722290160" 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="idm225357176304" class="indexterm"></a><a id="idm225357178672" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">LoadModule <em class="replaceable"><code>name</code></em> <em class="replaceable"><code>path</code></em></pre><a id="idm261691878832" class="indexterm"></a><a id="idm261691881312" class="indexterm"></a><div class="para">
The <em class="replaceable"><code>name</code></em> has to be a valid identifier of the required module. The <em class="replaceable"><code>path</code></em> refers to an existing module file, and must be relative to the directory in which the libraries are placed (that is, <code class="filename">/usr/lib/httpd/</code> on 32-bit and <code class="filename">/usr/lib64/httpd/</code> on 64-bit systems by default).
</div><div class="para">
See <a class="xref" href="#s2-apache-dso">Section 9.1.5, “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 9.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="idm225461739952" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-loadmodule"><h6>Example 9.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="idm261715858624" 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">
@@ -3375,7 +3395,7 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">%{<em class="replaceable"><code>field</code></em>}</code>
</td><td class="">
Represents the content of the HTTP header <em class="replaceable"><code>field</code></em>. The common options include <code class="option">%{Referer}</code> (the URL of the web page that referred the client to the server) and <code class="option">%{User-Agent}</code> (the type of the web browser making the request).
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-logformat"><h6>Example 9.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="idm225481163936" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-logformat"><h6>Example 9.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="idm261779716032" 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">
@@ -3416,12 +3436,12 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">debug</code>
</td><td class="">
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 9.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="idm225479047728" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-loglevel"><h6>Example 9.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="idm261749537968" 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 9.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="idm225443441280" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-maxkeepaliverequests"><h6>Example 9.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="idm261751871248" 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">
@@ -3430,7 +3450,7 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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 9.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="idm225414278656" class="indexterm"></a>
+ </div></div></div><div class="example" id="example-apache-httpdconf-namevirtualhost"><h6>Example 9.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="idm261756896256" 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">
@@ -3475,7 +3495,7 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">None</code>
</td><td class="">
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 9.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="idm225447387776" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-options"><h6>Example 9.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="idm261729428000" 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">
@@ -3492,12 +3512,12 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">deny,allow</code>
</td><td class="">
<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 9.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="idm225455271072" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-order"><h6>Example 9.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="idm261718290464" 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="idm225459921840" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">PidFile <em class="replaceable"><code>path</code></em></pre><a id="idm261737219136" 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 9.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="idm225468568912" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-pidfile"><h6>Example 9.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="idm261653021424" 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">
@@ -3514,12 +3534,12 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">Off</code>
</td><td class="">
Disables forward proxy requests.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-proxyrequests"><h6>Example 9.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="idm225457971088" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-proxyrequests"><h6>Example 9.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="idm261745594064" 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 9.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="idm225473799552" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-readmename"><h6>Example 9.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="idm261685577888" 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">
@@ -3544,14 +3564,14 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">gone</code>
</td><td class="">
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="idm225459035584" class="indexterm"></a><div class="para">
+ </td></tr></tbody></table></div></div><br class="table-break" /><a id="idm261726403296" 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 9.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="idm225474204640" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-redirect"><h6>Example 9.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="idm261726772400" 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="idm225447395456" class="indexterm"></a><div class="para">
+ </div><a id="idm261778818448" 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.
@@ -3562,26 +3582,26 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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="idm225477718656" class="indexterm"></a>
+</Directory></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261738583520" 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 at localhost</code>.
</div><div class="para">
This directive is commonly set to <code class="literal">webmaster@<em class="replaceable"><code>hostname</code></em></code>, where <em class="replaceable"><code>hostname</code></em> is the address of the server. Once set, alias <code class="literal">webmaster</code> to the person responsible for the web server in <code class="filename">/etc/aliases</code>, and as superuser, run the <code class="command">newaliases</code> command.
- </div><div class="example" id="example-apache-httpdconf-serveradmin"><h6>Example 9.59. Using the ServerAdmin directive</h6><div class="example-contents"><pre class="programlisting">ServerAdmin webmaster at penguin.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225434849520" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-serveradmin"><h6>Example 9.59. Using the ServerAdmin directive</h6><div class="example-contents"><pre class="programlisting">ServerAdmin webmaster at penguin.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261649796272" 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 9.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="idm225439585440" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-servername"><h6>Example 9.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="idm261738154064" 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="idm225477894256" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">ServerRoot <em class="replaceable"><code>directory</code></em></pre><a id="idm261745133616" 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 9.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="idm225471733712" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpd-serverroot"><h6>Example 9.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="idm261746745840" 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">
@@ -3602,7 +3622,7 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">EMail</code>
</td><td class="">
Enables appending the server name, version, and the email address of the system administrator as specified by the <code class="option">ServerAdmin</code> directive to server-generated pages.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-serversignature"><h6>Example 9.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="idm225481296464" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-serversignature"><h6>Example 9.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="idm261745199456" 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">
@@ -3637,26 +3657,26 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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 9.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="idm225479621472" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-servertokens"><h6>Example 9.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="idm261751201408" 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 9.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="idm225462742240" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-suexecusergroup"><h6>Example 9.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="idm261725458048" 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 9.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="idm225435375824" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-timeout"><h6>Example 9.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="idm261757701392" 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="idm225460739792" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">TypesConfig <em class="replaceable"><code>path</code></em></pre><a id="idm261738384880" 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 9.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="idm225458203584" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-typesconfig"><h6>Example 9.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="idm261749935840" 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">
@@ -3677,17 +3697,17 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">DNS</code>
</td><td class="">
Disables the use of the name that is specified by the <code class="option">ServerName</code> directive. The hostname determined by a reverse DNS lookup is used instead.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-usecanonicalname"><h6>Example 9.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="idm225427250176" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-usecanonicalname"><h6>Example 9.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="idm261756208288" 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 9.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="idm225477821984" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-user"><h6>Example 9.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="idm261751518256" 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="idm225475137200" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">UserDir <em class="replaceable"><code>option</code></em></pre><a id="idm261739828496" 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 9.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 9.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 class="">
Option
@@ -3708,9 +3728,9 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
All files in this directory must be set accordingly.
</div></div></div><div class="example" id="example-apache-httpdconf-userdir"><h6>Example 9.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">9.1.4.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="idm225470204528" class="indexterm"></a><div class="para">
+ </div><a id="idm261758482432" 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 class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225424558832" class="indexterm"></a>
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261714552832" 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">
@@ -3751,57 +3771,57 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
Note that for the <code class="filename">/etc/httpd/conf.d/ssl.conf</code> file to be present, the <span class="package">mod_ssl</span> needs to be installed. See <a class="xref" href="#s2-apache-mod_ssl">Section 9.1.7, “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">9.1.4.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="idm225425254768" class="indexterm"></a><div class="para">
+ </div><a id="idm261773695184" 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 class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225473907792" class="indexterm"></a>
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261778448544" 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 9.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="idm225459398192" class="indexterm"></a>
+ </div><div class="example" id="example-apache-mpm-maxclients"><h6>Example 9.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="idm261731036576" 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 9.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="idm225463334848" class="indexterm"></a>
+ </div><div class="example" id="example-apache-mpm-maxrequestsperchild"><h6>Example 9.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="idm261752950272" 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 9.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="idm225458540960" class="indexterm"></a>
+ </div><div class="example" id="example-apache-mpm-maxspareservers"><h6>Example 9.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="idm261652993888" 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 9.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="idm225480195392" class="indexterm"></a>
+ </div><div class="example" id="example-apache-mpm-maxsparethreads"><h6>Example 9.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="idm261777103968" 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 9.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="idm225448351184" class="indexterm"></a>
+ </div><div class="example" id="example-apache-mpm-minspareservers"><h6>Example 9.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="idm261709185984" 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 9.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="idm225476679280" class="indexterm"></a>
+ </div><div class="example" id="example-apache-mpm-minsparethreads"><h6>Example 9.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="idm261709159008" 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 9.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="idm225471701760" class="indexterm"></a>
+ </div><div class="example" id="example-apache-mpm-startservers"><h6>Example 9.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="idm261715082976" 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 9.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">9.1.5. Working with Modules</h3></div></div></div><a id="idm225408477696" class="indexterm"></a><a id="idm225437606528" class="indexterm"></a><div class="para">
+ </div><div class="example" id="example-apache-mpm-threadsperchild"><h6>Example 9.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">9.1.5. Working with Modules</h3></div></div></div><a id="idm261728858352" class="indexterm"></a><a id="idm261740476928" 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">9.1.5.1. Loading a Module</h4></div></div></div><a id="idm225466313824" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-apache-dso-loading"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.5.1. Loading a Module</h4></div></div></div><a id="idm261730632896" 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 9.1.4.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 9.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. See <a class="xref" href="#s3-apache-running-restarting">Section 9.1.3.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">9.1.5.2. Writing a Module</h4></div></div></div><a id="idm225475919328" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-apache-dso-writing"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.5.2. Writing a Module</h4></div></div></div><a id="idm261738361056" class="indexterm"></a><div class="para">
If you intend to create a new DSO module, make sure you have the <span class="package">httpd-devel</span> package installed. To do so, enter the following command as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">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.
@@ -3809,7 +3829,7 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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">9.1.6. Setting Up Virtual Hosts</h3></div></div></div><a id="idm225478299264" class="indexterm"></a><a id="idm225463129056" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s2-apache-virtualhosts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.6. Setting Up Virtual Hosts</h3></div></div></div><a id="idm261754656192" class="indexterm"></a><a id="idm261754657632" class="indexterm"></a><div class="para">
The Apache HTTP Server's built in virtual hosting allows the server to provide different information based on which IP address, host name, or port is being requested.
</div><div class="para">
To create a name-based virtual host, copy the example configuration file <code class="filename">/usr/share/doc/httpd-<em class="replaceable"><code>VERSION</code></em>/httpd-vhosts.conf</code> into the <code class="filename">/etc/httpd/conf.d/</code> directory, and replace the <code class="literal">@@Port@@</code> and <code class="literal">@@ServerRoot@@</code> placeholder values. Customize the options according to your requirements as shown in <a class="xref" href="#example-apache-virtualhosts-config">Example 9.80, “Example virtual host configuration”</a>.
@@ -3827,13 +3847,13 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
If you configure a virtual host to listen on a non-default port, make sure you update the <code class="option">Listen</code> directive in the global settings section of the <code class="filename">/etc/httpd/conf/httpd.conf</code> file accordingly.
</div></div></div><div class="para">
To activate a newly created virtual host, the web server has to be restarted first. See <a class="xref" href="#s3-apache-running-restarting">Section 9.1.3.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">9.1.7. Setting Up an SSL Server</h3></div></div></div><a id="idm225474901280" class="indexterm"></a><a id="idm225474901760" class="indexterm"></a><a id="idm225413598880" class="indexterm"></a><a id="idm225413600976" class="indexterm"></a><a id="idm225413602736" class="indexterm"></a><a id="idm225424894144" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-apache-mod_ssl"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.7. Setting Up an SSL Server</h3></div></div></div><a id="idm261721663120" class="indexterm"></a><a id="idm261741760768" class="indexterm"></a><a id="idm261751408400" class="indexterm"></a><a id="idm261741761568" class="indexterm"></a><a id="idm261741763184" class="indexterm"></a><a id="idm261737798144" 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">9.1.7.1. An Overview of Certificates and Security</h4></div></div></div><a id="idm225471579792" class="indexterm"></a><a id="idm225457351120" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-apache-mod_ssl-certificates"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.7.1. An Overview of Certificates and Security</h4></div></div></div><a id="idm261780946816" class="indexterm"></a><a id="idm261738192208" 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="idm225459960944" class="indexterm"></a><a id="idm225459962080" class="indexterm"></a><div class="para">
+ </div><a id="idm261726644384" class="indexterm"></a><a id="idm261722560496" class="indexterm"></a><div class="para">
To provide secure communications using SSL, an SSL server must use a digital certificate signed by a <em class="firstterm">Certificate Authority</em> (<acronym class="acronym">CA</acronym>). The certificate lists various attributes of the server (that is, the server host name, the name of the company, its location, etc.), and the signature produced using the CA's private key. This signature ensures that a particular certificate authority has signed the certificate, and that the certificate has not been modified in any way.
</div><div class="para">
When a web browser establishes a new SSL connection, it checks the certificate provided by the web server. If the certificate does not have a signature from a trusted CA, or if the host name listed in the certificate does not match the host name used to establish the connection, it refuses to communicate with the server and usually presents a user with an appropriate error message.
@@ -3863,9 +3883,9 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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">9.1.7.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, enter the following command as <code class="systemitem">root</code>:
- </div><pre class="screen">~]# <code class="command">yum install mod_ssl openssl</code></pre><a id="idm225459239472" class="indexterm"></a><div class="para">
+ </div><pre class="screen">~]# <code class="command">yum install mod_ssl openssl</code></pre><a id="idm261714504032" 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 9.1.3.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">9.1.7.3. Using an Existing Key and Certificate</h4></div></div></div><a id="idm225472081488" class="indexterm"></a><a id="idm225460676384" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-apache-mod_ssl-keypair"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.7.3. Using an Existing Key and Certificate</h4></div></div></div><a id="idm261780113616" class="indexterm"></a><a id="idm261780115200" 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>
@@ -3886,7 +3906,7 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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 9.1.3.3, “Restarting the Service”</a>.
</div><div class="example" id="example-apache-mod_ssl-keypair"><h6>Example 9.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">9.1.7.4. Generating a New Key and Certificate</h4></div></div></div><a id="idm225442763392" class="indexterm"></a><a id="idm225481303856" class="indexterm"></a><div class="para">
+~]# <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">9.1.7.4. Generating a New Key and Certificate</h4></div></div></div><a id="idm261743242784" class="indexterm"></a><a id="idm261743244624" class="indexterm"></a><div class="para">
In order to generate a new key and certificate pair, the <span class="package">crypto-utils</span> package must be installed on the system. To install it, enter the following command as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">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.
@@ -3949,18 +3969,18 @@ SSLCertificateKeyFile /etc/pki/tls/private/<em class="replaceable"><code>hostnam
Finally, restart the <code class="systemitem">httpd</code> service as described in <a class="xref" href="#s3-apache-running-restarting">Section 9.1.3.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">9.1.8. Additional Resources</h3></div></div></div><div class="para">
To learn more about the Apache HTTP Server, see the following resources.
- </div><h4 id="bh-The_Apache_HTTP_Server-Installed_Documentation">Installed Documentation</h4><a id="idm225450314784" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><h4 id="bh-The_Apache_HTTP_Server-Installed_Documentation">Installed Documentation</h4><a id="idm261754098592" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="filename">httpd(8)</code> — The manual page for the <code class="systemitem">httpd</code> service containing the complete list of its command-line options.
</div></li><li class="listitem"><div class="para">
<code class="filename">genkey(1)</code> — The manual page for <code class="command">genkey</code> utility, provided by the <span class="package">crypto-utils</span> package.
</div></li><li class="listitem"><div class="para">
<code class="filename">apachectl(8)</code> — The manual page for the Apache HTTP Server Control Interface.
- </div></li></ul></div><h4 id="bh-The_Apache_HTTP_Server-Installable_Documentation">Installable Documentation</h4><a id="idm225479461072" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div></li></ul></div><h4 id="bh-The_Apache_HTTP_Server-Installable_Documentation">Installable Documentation</h4><a id="idm261733292480" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://localhost/manual/">http://localhost/manual/</a> — The official documentation for the Apache HTTP Server with the full description of its directives and available modules. Note that in order to access this documentation, you must have the <span class="package">httpd-manual</span> package installed, and the web server must be running.
</div><div class="para">
Before accessing the documentation, issue the following commands as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">yum install httpd-manual</code>
-~]# <code class="command">apachectl graceful</code></pre></li></ul></div><h4 id="bh-The_Apache_HTTP_Server-Online_Documentation">Online Documentation</h4><a id="idm225504481808" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+~]# <code class="command">apachectl graceful</code></pre></li></ul></div><h4 id="bh-The_Apache_HTTP_Server-Online_Documentation">Online Documentation</h4><a id="idm261722557088" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://httpd.apache.org/">http://httpd.apache.org/</a> — The official website for the Apache HTTP Server with documentation on all the directives and default modules.
</div></li><li class="listitem"><div class="para">
ulink url="http://www.modssl.org/" /> — The official website for the <span class="application"><strong>mod_ssl</strong></span> module.
@@ -3968,7 +3988,7 @@ SSLCertificateKeyFile /etc/pki/tls/private/<em class="replaceable"><code>hostnam
<a href="http://www.openssl.org/">http://www.openssl.org/</a> — The OpenSSL home page containing further documentation, frequently asked questions, links to the mailing lists, and other useful resources.
</div></li></ul></div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-Mail_Servers" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 10. Mail Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-email-protocols">10.1. Email Protocols</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-protocols-send">10.1.1. Mail Transport Protocols</a></span></dt><dt><span class="section"><a href="#s2-email-protocols-client">10.1.2. Mail Access Protocols</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-types">10.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-types-mta">10.2.1. Mail Transport Agent</a></span></dt><dt><span class="section"><a href="#s2-email-types-mda">10.2.2. Mail Delivery Agent</a></span></dt><dt><span class="section"><a href="#s2-email-types-mua">10.2.3. Mail User Agent</a></span></dt></dl></
dd><dt><span class="section"><a href="#s1-email-mta">10.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-mta-postfix">10.3.1. Postfix</a></span></dt><dt><span class="section"><a href="#s2-email-mta-sendmail">10.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="#s2-email-mta-fetchmail">10.3.3. Fetchmail</a></span></dt><dt><span class="section"><a href="#s2-email-switchmail">10.3.4. Mail Transport Agent (MTA) Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mda">10.4. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-procmail-configuration">10.4.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="#s2-email-procmail-recipes">10.4.2. Procmail Recipes</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-mua">10.5. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-security">10
.5.1. Securing Communication</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-email-additional-resources">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-email-installed-docs">10.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#s2-email-useful-websites">10.6.2. Useful Websites</a></span></dt><dt><span class="section"><a href="#s2-email-related-books">10.6.3. Related Books</a></span></dt></dl></dd></dl></div><div class="para">
Fedora offers many advanced applications to serve and access email. This chapter describes modern email protocols in use today, and some of the programs designed to send and receive email.
- </div><div class="section" id="s1-email-protocols"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.1. Email Protocols</h2></div></div></div><a id="idm225416152448" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s1-email-protocols"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.1. Email Protocols</h2></div></div></div><a id="idm261745717248" 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.
@@ -3976,7 +3996,7 @@ SSLCertificateKeyFile /etc/pki/tls/private/<em class="replaceable"><code>hostnam
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">10.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">10.1.1.1. SMTP</h4></div></div></div><a id="idm225472513744" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-email-protocols-smtp"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.1.1.1. SMTP</h4></div></div></div><a id="idm261763881408" 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.
@@ -3986,7 +4006,7 @@ SSLCertificateKeyFile /etc/pki/tls/private/<em class="replaceable"><code>hostnam
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">10.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">10.1.2.1. POP</h4></div></div></div><a id="idm225481035120" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-email-protocols-pop"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.1.2.1. POP</h4></div></div></div><a id="idm261717609824" 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 <span class="package">dovecot</span> package is installed on your system by running, as <code class="systemitem">root</code>:
@@ -4010,7 +4030,7 @@ SSLCertificateKeyFile /etc/pki/tls/private/<em class="replaceable"><code>hostnam
<span class="emphasis"><em>RPOP</em></span> — <code class="systemitem">POP3</code> with <code class="systemitem">RPOP</code> authentication. This uses a per-user ID, similar to a password, to authenticate POP requests. However, this ID is not encrypted, so <code class="systemitem">RPOP</code> is no more secure than standard <code class="systemitem">POP</code>.
</div></li></ul></div><div class="para">
For added security, it is possible to use <em class="firstterm">Secure Socket Layer</em> (<em class="firstterm">SSL</em>) encryption for client authentication and data transfer sessions. This can be enabled by using the <code class="command">pop3s</code> service, or by using the <code class="command">stunnel</code> application. For more information on securing email communication, see <a class="xref" href="#s2-email-security">Section 10.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">10.1.2.2. IMAP</h4></div></div></div><a id="idm225441094736" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-protocols-imap"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.1.2.2. IMAP</h4></div></div></div><a id="idm261650407024" class="indexterm"></a><div class="para">
The default <code class="systemitem">IMAP</code> server under Fedora is <span class="application"><strong>Dovecot</strong></span> and is provided by the <span class="package">dovecot</span> package. See <a class="xref" href="#s3-email-protocols-pop">Section 10.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.
@@ -4024,11 +4044,11 @@ SSLCertificateKeyFile /etc/pki/tls/private/<em class="replaceable"><code>hostnam
For added security, it is possible to use <code class="systemitem">SSL</code> encryption for client authentication and data transfer sessions. This can be enabled by using the <code class="command">imaps</code> service, or by using the <code class="command">stunnel</code> program. For more information on securing email communication, see <a class="xref" href="#s2-email-security">Section 10.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">10.1.2.3. Dovecot</h4></div></div></div><a id="idm225446180176" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-mail-server-dovecot"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.1.2.3. Dovecot</h4></div></div></div><a id="idm261751359792" class="indexterm"></a><div class="para">
The <code class="command">imap-login</code> and <code class="command">pop3-login</code> processes which implement the <code class="systemitem">IMAP</code> and <code class="systemitem">POP3</code> protocols are spawned by the master <code class="systemitem">dovecot</code> daemon included in the <span class="package">dovecot</span> package. The use of <code class="systemitem">IMAP</code> and <code class="systemitem">POP</code> is configured through the <code class="filename">/etc/dovecot/dovecot.conf</code> configuration file; by default <code class="command">dovecot</code> runs <code class="systemitem">IMAP</code> and <code class="systemitem">POP3</code> together with their secure versions using <code class="systemitem">SSL</code>. To configure <code class="command">dovecot</code> to use <code class="systemitem">POP</code>, complete the following steps:
</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
Edit the <code class="filename">/etc/dovecot/dovecot.conf</code> configuration file to make sure the <code class="literal">protocols</code> variable is uncommented (remove the hash sign (<code class="literal">#</code>) at the beginning of the line) and contains the <code class="literal">pop3</code> argument. For example:
- </div><pre class="programlisting">protocols = imap imaps pop3 pop3s</pre><div class="para">
+ </div><pre class="screen">protocols = imap pop3 lmtp</pre><div class="para">
When the <code class="literal">protocols</code> variable is left commented out, <code class="command">dovecot</code> will use the default values as described above.
</div></li><li class="listitem"><div class="para">
Make the change operational for the current session by running the following command as <code class="systemitem">root</code>:
@@ -4049,9 +4069,9 @@ ln -s '/usr/lib/systemd/system/dovecot' '/etc/systemd/system/multi-user.target.w
Execute the <code class="filename">/usr/libexec/dovecot/mkcert.sh</code> script which creates the <code class="command">dovecot</code> self signed certificates. These certificates are copied in the <code class="filename">/etc/pki/dovecot/certs</code> and <code class="filename">/etc/pki/dovecot/private</code> directories. To implement the changes, restart <code class="command">dovecot</code> by issuing the following command as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">systemctl restart dovecot</code></pre></li></ul></div><div class="para">
More details on <code class="command">dovecot</code> can be found online at <a href="http://www.dovecot.org">http://www.dovecot.org</a>.
- </div></div></div></div><div class="section" id="s1-email-types"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.2. Email Program Classifications</h2></div></div></div><a id="idm225471648336" class="indexterm"></a><div class="para">
+ </div></div></div></div><div class="section" id="s1-email-types"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.2. Email Program Classifications</h2></div></div></div><a id="idm261749853456" 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">10.2.1. Mail Transport Agent</h3></div></div></div><a id="idm225443488000" class="indexterm"></a><a id="idm225455434416" class="indexterm"></a><a id="idm225455432976" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-email-types-mta"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.1. Mail Transport Agent</h3></div></div></div><a id="idm261758725008" class="indexterm"></a><a id="idm261758723088" class="indexterm"></a><a id="idm261728985984" 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.
@@ -4061,11 +4081,11 @@ ln -s '/usr/lib/systemd/system/dovecot' '/etc/systemd/system/multi-user.target.w
Since Fedora offers two MTAs, <em class="firstterm">Postfix</em> and <em class="firstterm">Sendmail</em>, email client programs are often not required to act as an MTA. Fedora also includes a special purpose MTA called <em class="firstterm">Fetchmail</em>.
</div><div class="para">
For more information on Postfix, Sendmail, and Fetchmail, see <a class="xref" href="#s1-email-mta">Section 10.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">10.2.2. Mail Delivery Agent</h3></div></div></div><a id="idm225479058864" class="indexterm"></a><a id="idm225462369696" class="indexterm"></a><a id="idm225462368256" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-email-types-mda"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.2. Mail Delivery Agent</h3></div></div></div><a id="idm261761518944" class="indexterm"></a><a id="idm261761517024" class="indexterm"></a><a id="idm261744848784" 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">10.2.3. Mail User Agent</h3></div></div></div><a id="idm225461377776" class="indexterm"></a><a id="idm225475430336" class="indexterm"></a><a id="idm225475428896" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-email-types-mua"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.3. Mail User Agent</h3></div></div></div><a id="idm261737017712" class="indexterm"></a><a id="idm261752568768" class="indexterm"></a><a id="idm261752567328" class="indexterm"></a><div class="para">
A <em class="firstterm">Mail User Agent</em> (<em class="firstterm">MUA</em>) is synonymous with an email client application. An MUA is a program that, at a minimum, allows a user to read and compose email messages. Many MUAs are capable of retrieving messages via the <code class="systemitem">POP</code> or <code class="systemitem">IMAP</code> protocols, setting up mailboxes to store messages, and sending outbound messages to an MTA.
</div><div class="para">
MUAs may be graphical, such as <span class="application"><strong>Evolution</strong></span>, or have simple text-based interfaces, such as <span class="application"><strong>Mutt</strong></span>.
@@ -4077,7 +4097,7 @@ ln -s '/usr/lib/systemd/system/dovecot' '/etc/systemd/system/multi-user.target.w
Similarly, to disable the service, type the following at a shell prompt:
</div><pre class="screen">~]# <code class="command">systemctl disable <em class="replaceable"><code>service</code></em></code></pre><div class="para">
For more information on how to manage system services in Fedora 21, see <a class="xref" href="#ch-Services_and_Daemons">Chapter 6, <em>Services and Daemons</em></a>.
- </div><div class="section" id="s2-email-mta-postfix"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.1. Postfix</h3></div></div></div><a id="idm225460492736" class="indexterm"></a><a id="idm225477167952" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-email-mta-postfix"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.1. Postfix</h3></div></div></div><a id="idm261714278272" class="indexterm"></a><a id="idm261714276832" 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 changed root environment to limit the effects of attacks.
@@ -4085,7 +4105,7 @@ ln -s '/usr/lib/systemd/system/dovecot' '/etc/systemd/system/multi-user.target.w
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">10.3.1.1. The Default Postfix Installation</h4></div></div></div><a id="idm225460555184" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-email-mta-postfix-default"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.1.1. The Default Postfix Installation</h4></div></div></div><a id="idm261754755072" class="indexterm"></a><div class="para">
The Postfix executable is <code class="filename">postfix</code>. This daemon launches all related processes needed to handle mail delivery.
</div><div class="para">
Postfix stores its configuration files in the <code class="filename">/etc/postfix/</code> directory. The following is a list of the more commonly used files:
@@ -4142,15 +4162,15 @@ search_base = dc=<em class="replaceable"><code>example</code></em>, dc=<em class
The <code class="filename">/etc/postfix/ldap-aliases.cf</code> file can specify various parameters, including parameters that enable <code class="systemitem">LDAP</code> <code class="systemitem">SSL</code> and <code class="systemitem">STARTTLS</code>. For more information, see the <code class="filename">ldap_table(5)</code> man page.
</div></div></div><div class="para">
For more information on <code class="systemitem">LDAP</code>, see <a class="xref" href="#s1-OpenLDAP">Section 11.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">10.3.2. Sendmail</h3></div></div></div><a id="idm225446661856" class="indexterm"></a><a id="idm225455011264" class="indexterm"></a><div class="para">
+ </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">10.3.2. Sendmail</h3></div></div></div><a id="idm261760897456" class="indexterm"></a><a id="idm261724724960" class="indexterm"></a><div class="para">
Sendmail's core purpose, like other MTAs, is to safely transfer email among hosts, usually using the <code class="systemitem">SMTP</code> protocol. Note that Sendmail is considered deprecated and users are encouraged to use Postfix when possible. See <a class="xref" href="#s2-email-mta-postfix">Section 10.3.1, “Postfix”</a> for more information.
- </div><div class="section" id="s3-email-mta-sendmail-purpose"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.1. Purpose and Limitations</h4></div></div></div><a id="idm225470344496" class="indexterm"></a><a id="idm225470343056" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-email-mta-sendmail-purpose"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.1. Purpose and Limitations</h4></div></div></div><a id="idm261748796272" class="indexterm"></a><a id="idm261748794832" class="indexterm"></a><div class="para">
It is important to be aware of what Sendmail is and what it can do, as opposed to what it is not. In these days of monolithic applications that fulfill multiple roles, Sendmail may seem like the only application needed to run an email server within an organization. Technically, this is true, as Sendmail can spool mail to each users' directory and deliver outbound mail for users. However, most users actually require much more than simple email delivery. Users usually want to interact with their email using an MUA, that uses <code class="systemitem">POP</code> or <code class="systemitem">IMAP</code>, to download their messages to their local machine. Or, they may prefer a Web interface to gain access to their mailbox. These other applications can work in conjunction with Sendmail, but they actually exist for different reasons and can operate separately from one another.
</div><div class="para">
It is beyond the scope of this section to go into all that Sendmail should or could be configured to do. With literally hundreds of different options and rule sets, entire volumes have been dedicated to helping explain everything that can be done and how to fix things that go wrong. See the <a class="xref" href="#s1-email-additional-resources">Section 10.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">10.3.2.2. The Default Sendmail Installation</h4></div></div></div><a id="idm225467741088" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-mta-sendmail-default"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.2. The Default Sendmail Installation</h4></div></div></div><a id="idm261742371232" 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>:
@@ -4181,9 +4201,9 @@ search_base = dc=<em class="replaceable"><code>example</code></em>, dc=<em class
</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 commands, as <code class="systemitem">root</code>:
-<pre class="screen">~]# <code class="command">cd /etc/mail</code>
-~]# <code class="command">make all</code></pre>
+ Several of the configuration files in the <code class="filename">/etc/mail/</code> directory, such as <code class="filename">access</code>, <code class="filename">domaintable</code>, <code class="filename">mailertable</code> and <code class="filename">virtusertable</code>, must actually store their information in database files before Sendmail can use any configuration changes. To include any changes made to these configurations in their database files, run the following commands, as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">cd /etc/mail/</code>
+~]# <code class="command">make all</code></pre>
This will update <code class="filename">virtusertable.db</code>, <code class="filename">access.db</code>, <code class="filename">domaintable.db</code>, <code class="filename">mailertable.db</code>, <code class="filename">sendmail.cf</code>, and <code class="filename">submit.cf</code>.
</div><div class="para">
To update all the database files listed above and to update a custom database file, use a command in the following format: <pre class="synopsis"><code class="command">make <em class="replaceable"><code>name.db</code></em> all</code></pre> where <em class="replaceable"><code>name</code></em> represents the name of the custom database file to be updated.
@@ -4198,7 +4218,7 @@ search_base = dc=<em class="replaceable"><code>example</code></em>, dc=<em class
To finalize the change, the <code class="filename">virtusertable.db</code> file must be updated:
</div><pre class="screen">~]# <code class="command">make <code class="filename">virtusertable.db</code> all</code></pre><div class="para">
Using the <code class="option">all</code> option will result in the <code class="filename">virtusertable.db</code> and <code class="filename">access.db</code> being updated at the same time.
- </div></div><div class="section" id="s3-email-mta-sendmail-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.3. Common Sendmail Configuration Changes</h4></div></div></div><a id="idm225371417744" class="indexterm"></a><a id="idm225371416336" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-mta-sendmail-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.3. Common Sendmail Configuration Changes</h4></div></div></div><a id="idm261753174032" class="indexterm"></a><a id="idm261719929008" 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 replacing or making any changes to the <code class="filename">sendmail.cf</code> file, create a backup copy.
@@ -4209,8 +4229,8 @@ search_base = dc=<em class="replaceable"><code>example</code></em>, dc=<em class
</div><pre class="screen">~]# <code class="command">systemctl restart sendmail</code></pre></div></div><div class="para">
The default configuration in Fedora works for most <code class="systemitem">SMTP</code>-only sites. However, it does not work for <em class="firstterm">UUCP</em> (<em class="firstterm">UNIX-to-UNIX Copy Protocol</em>) sites. If using UUCP mail transfers, the <code class="filename">/etc/mail/sendmail.mc</code> file must be reconfigured and a new <code class="filename">/etc/mail/sendmail.cf</code> file must be generated.
</div><div class="para">
- Consult the <code class="filename">/usr/share/sendmail-cf/README</code> file before editing any files in the directories under the <code class="filename">/usr/share/sendmail-cf</code> directory, as they can affect the future configuration of the <code class="filename">/etc/mail/sendmail.cf</code> file.
- </div></div><div class="section" id="s3-email-sendmail-changes-masquerading"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.4. Masquerading</h4></div></div></div><a id="idm225477408928" class="indexterm"></a><a id="idm225444176048" class="indexterm"></a><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">10.3.2.4. Masquerading</h4></div></div></div><a id="idm261785230544" class="indexterm"></a><a id="idm261714541712" class="indexterm"></a><div class="para">
One common Sendmail configuration is to have a single machine act as a mail gateway for all machines on the network. For example, a company may want to have a machine called <code class="computeroutput">mail.example.com</code> that handles all of their email and assigns a consistent return address to all outgoing mail.
</div><div class="para">
In this situation, the Sendmail server must masquerade the machine names on the company network so that their return address is <code class="computeroutput">user at example.com</code> instead of <code class="computeroutput">user at host.example.com</code>.
@@ -4224,7 +4244,7 @@ MASQUERADE_AS(`example.com.')dnl
MASQUERADE_DOMAIN(`example.com.')dnl
MASQUERADE_AS(example.com)dnl</pre><div class="para">
After generating a new <code class="filename">sendmail.cf</code> file using the <code class="command">m4</code> macro processor, this configuration makes all mail from inside the network appear as if it were sent from <code class="systemitem">example.com</code>.
- </div></div><div class="section" id="s3-email-sendmail-stopping-spam"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.5. Stopping Spam</h4></div></div></div><a id="idm225480473648" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-sendmail-stopping-spam"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.5. Stopping Spam</h4></div></div></div><a id="idm261751743312" 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>.
@@ -4242,7 +4262,7 @@ MASQUERADE_AS(example.com)dnl</pre><div class="para">
The above examples only represent a small part of what Sendmail can do in terms of allowing or blocking access. See the <code class="filename">/usr/share/sendmail-cf/README</code> file for more information and examples.
</div><div class="para">
Since Sendmail calls the Procmail MDA when delivering mail, it is also possible to use a spam filtering program, such as SpamAssassin, to identify and file spam for users. See <a class="xref" href="#s3-email-mda-spam">Section 10.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">10.3.2.6. Using Sendmail with LDAP</h4></div></div></div><a id="idm225427886672" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-mta-sendmail-ldap"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.6. Using Sendmail with LDAP</h4></div></div></div><a id="idm261787687200" 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.
@@ -4257,7 +4277,7 @@ FEATURE('ldap_routing')dnl</pre><div class="note"><div class="admonition_header"
Next, recreate the <code class="filename">/etc/mail/sendmail.cf</code> file by running the <code class="command">m4</code> macro processor and again restarting Sendmail. See <a class="xref" href="#s3-email-mta-sendmail-changes">Section 10.3.2.3, “Common Sendmail Configuration Changes”</a> for instructions.
</div><div class="para">
For more information on <code class="systemitem">LDAP</code>, see <a class="xref" href="#s1-OpenLDAP">Section 11.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">10.3.3. Fetchmail</h3></div></div></div><a id="idm225455866176" class="indexterm"></a><a id="idm225455864736" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s2-email-mta-fetchmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.3. Fetchmail</h3></div></div></div><a id="idm261748835504" class="indexterm"></a><a id="idm261748834064" 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>:
@@ -4267,7 +4287,7 @@ FEATURE('ldap_routing')dnl</pre><div class="note"><div class="admonition_header"
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">10.3.3.1. Fetchmail Configuration Options</h4></div></div></div><a id="idm225481282288" class="indexterm"></a><a id="idm225481280848" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-email-mda-fetchmail-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.3.1. Fetchmail Configuration Options</h4></div></div></div><a id="idm261752810864" class="indexterm"></a><a id="idm261746101808" 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:
@@ -4297,7 +4317,7 @@ poll mail.domain2.com
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">10.3.3.2. Global Options</h4></div></div></div><a id="idm225447406560" class="indexterm"></a><a id="idm225447404640" class="indexterm"></a><div class="para">
+ </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">10.3.3.2. Global Options</h4></div></div></div><a id="idm261735412224" class="indexterm"></a><a id="idm261740394048" 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.
@@ -4305,7 +4325,7 @@ poll mail.domain2.com
<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">10.3.3.3. Server Options</h4></div></div></div><a id="idm225480127792" class="indexterm"></a><a id="idm225479194560" class="indexterm"></a><div class="para">
+ </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">10.3.3.3. Server Options</h4></div></div></div><a id="idm261725477248" class="indexterm"></a><a id="idm261725475328" 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.
@@ -4317,7 +4337,7 @@ poll mail.domain2.com
<code class="command">proto <em class="replaceable"><code>protocol</code></em> </code> — Replace <em class="replaceable"><code>protocol</code></em> with the protocol, such as <code class="command">pop3</code> or <code class="command">imap</code>, to use when checking for messages on the server.
</div></li><li class="listitem"><div class="para">
<code class="command">timeout <em class="replaceable"><code>seconds</code></em> </code> — Replace <em class="replaceable"><code>seconds</code></em> with the number of seconds of server inactivity after which Fetchmail gives up on a connection attempt. If this value is not set, a default of <code class="command">300</code> seconds is used.
- </div></li></ul></div></div><div class="section" id="s3-email-fetchmail-configuration-user"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.3.4. User Options</h4></div></div></div><a id="idm225439307056" class="indexterm"></a><a id="idm225439305136" class="indexterm"></a><div class="para">
+ </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">10.3.3.4. User Options</h4></div></div></div><a id="idm261740367792" class="indexterm"></a><a id="idm261687928240" 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.
@@ -4337,11 +4357,11 @@ poll mail.domain2.com
<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">10.3.3.5. Fetchmail Command Options</h4></div></div></div><a id="idm225472446352" class="indexterm"></a><div class="para">
+ </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">10.3.3.5. Fetchmail Command Options</h4></div></div></div><a id="idm261720776432" 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">10.3.3.6. Informational or Debugging Options</h4></div></div></div><a id="idm225480943840" class="indexterm"></a><div class="para">
+ </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">10.3.3.6. Informational or Debugging Options</h4></div></div></div><a id="idm261733490048" 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.
@@ -4351,7 +4371,7 @@ poll mail.domain2.com
<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">10.3.3.7. Special Options</h4></div></div></div><a id="idm225442310464" class="indexterm"></a><div class="para">
+ </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">10.3.3.7. Special Options</h4></div></div></div><a id="idm261749343456" 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.
@@ -4363,17 +4383,17 @@ poll mail.domain2.com
<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">10.3.4. Mail Transport Agent (MTA) Configuration</h3></div></div></div><a id="idm225455155792" class="indexterm"></a><a id="idm225455154352" class="indexterm"></a><a id="idm225460907440" class="indexterm"></a><a id="idm225460905712" class="indexterm"></a><a id="idm225478336912" class="indexterm"></a><a id="idm225478335952" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s2-email-switchmail"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.4. Mail Transport Agent (MTA) Configuration</h3></div></div></div><a id="idm261741667056" class="indexterm"></a><a id="idm261741665616" class="indexterm"></a><a id="idm261757644880" class="indexterm"></a><a id="idm261757643152" class="indexterm"></a><a id="idm261712987904" class="indexterm"></a><a id="idm261712986944" class="indexterm"></a><div class="para">
A <em class="firstterm">Mail Transport Agent</em> (MTA) is essential for sending email. A <em class="firstterm">Mail User Agent</em> (MUA) such as <span class="application"><strong>Evolution</strong></span>, <span class="application"><strong>Thunderbird</strong></span>, and <span class="application"><strong>Mutt</strong></span>, is used to read and compose email. When a user sends an email from an MUA, the message is handed off to the MTA, which sends the message through a series of MTAs until it reaches its destination.
</div><div class="para">
Even if a user does not plan to send email from the system, some automated tasks or system programs might use the <code class="command">mail</code> command to send email containing log messages to the <code class="systemitem">root</code> user of the local system.
- </div><a id="idm225481367504" class="indexterm"></a><a id="idm225481366544" class="indexterm"></a><div class="para">
+ </div><a id="idm261749612368" class="indexterm"></a><a id="idm261716379904" class="indexterm"></a><div class="para">
Fedora 21 provides two MTAs: Postfix and Sendmail. If both are installed, Postfix is the default MTA. Note that Sendmail is considered deprecated in MAJOROS;.
</div></div></div><div class="section" id="s1-email-mda"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.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="idm225461294848" class="indexterm"></a><a id="idm225445404400" class="indexterm"></a><div class="para">
+ </div><a id="idm261716986288" class="indexterm"></a><a id="idm261756765504" 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.
@@ -4383,7 +4403,7 @@ poll mail.domain2.com
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">10.4.1. Procmail Configuration</h3></div></div></div><a id="idm225443043680" class="indexterm"></a><a id="idm225455583936" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-email-procmail-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.4.1. Procmail Configuration</h3></div></div></div><a id="idm261754813984" class="indexterm"></a><a id="idm261780589392" 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:
@@ -4425,7 +4445,7 @@ INCLUDERC=$MAILDIR/spam.rc</pre><div class="para">
Other important environmental variables are pulled from the shell, such as <code class="command">LOGNAME</code>, the login name; <code class="command">HOME</code>, the location of the home directory; and <code class="command">SHELL</code>, the default shell.
</div><div class="para">
A comprehensive explanation of all environments variables, and their default values, is available in the <code class="filename">procmailrc</code> man page.
- </div></div><div class="section" id="s2-email-procmail-recipes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.4.2. Procmail Recipes</h3></div></div></div><a id="idm225475487312" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-email-procmail-recipes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.4.2. Procmail Recipes</h3></div></div></div><a id="idm261757709952" class="indexterm"></a><div class="para">
New users often find the construction of recipes the most difficult part of learning to use Procmail. This difficulty is often attributed to recipes matching messages by using <em class="firstterm">regular expressions</em> which are used to specify qualifications for string matching. However, regular expressions are not very difficult to construct and even less difficult to understand when read. Additionally, the consistency of the way Procmail recipes are written, regardless of regular expressions, makes it easy to learn by example. To see example Procmail recipes, see <a class="xref" href="#s3-email-procmail-recipes-examples">Section 10.4.2.5, “Recipe Examples”</a>.
</div><div class="para">
Procmail recipes take the following form:
@@ -4440,11 +4460,11 @@ INCLUDERC=$MAILDIR/spam.rc</pre><div class="para">
A recipe can contain several conditions to match against the message. If it has no conditions, every message matches the recipe. Regular expressions are placed in some conditions to facilitate message matching. If multiple conditions are used, they must all match for the action to be performed. Conditions are checked based on the flags set in the recipe's first line. Optional special characters placed after the asterisk character (<code class="command">*</code>) can further control the condition.
</div><div class="para">
The <code class="command"><em class="replaceable"><code>action-to-perform</code></em></code> argument specifies the action taken when the message matches one of the conditions. There can only be one action per recipe. In many cases, the name of a mailbox is used here to direct matching messages into that file, effectively sorting the email. Special action characters may also be used before the action is specified. See <a class="xref" href="#s3-email-procmail-recipes-special">Section 10.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">10.4.2.1. Delivering vs. Non-Delivering Recipes</h4></div></div></div><a id="idm225481984128" class="indexterm"></a><a id="idm225481982208" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-email-procmail-recipes-delivering"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.4.2.1. Delivering vs. Non-Delivering Recipes</h4></div></div></div><a id="idm261716961680" class="indexterm"></a><a id="idm261716959760" 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">10.4.2.2. Flags</h4></div></div></div><a id="idm225467374928" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-procmail-recipes-flags"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.4.2.2. Flags</h4></div></div></div><a id="idm261749206320" class="indexterm"></a><div class="para">
Flags are essential to determine how or if a recipe's conditions are compared to a message. The <span class="application"><strong>egrep</strong></span> utility is used internally for matching of the conditions. The following flags are commonly used:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">A</code> — Specifies that this recipe is only used if the previous recipe without an <code class="command">A</code> or <code class="command">a</code> flag also matched this message.
@@ -4474,11 +4494,11 @@ INCLUDERC=$MAILDIR/spam.rc</pre><div class="para">
<code class="command">W</code> — Is identical to <code class="command">w</code> except that "Program failure" messages are suppressed.
</div></li></ul></div><div class="para">
For a detailed list of additional flags, see the <code class="filename">procmailrc</code> man page.
- </div></div><div class="section" id="s3-email-procmail-recipes-lockfile"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.4.2.3. Specifying a Local Lockfile</h4></div></div></div><a id="idm225477261520" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-procmail-recipes-lockfile"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.4.2.3. Specifying a Local Lockfile</h4></div></div></div><a id="idm261739770560" 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">10.4.2.4. Special Conditions and Actions</h4></div></div></div><a id="idm225468671312" class="indexterm"></a><a id="idm225449951568" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-procmail-recipes-special"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.4.2.4. Special Conditions and Actions</h4></div></div></div><a id="idm261733336160" class="indexterm"></a><a id="idm261733334240" 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:
@@ -4500,7 +4520,7 @@ INCLUDERC=$MAILDIR/spam.rc</pre><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">10.4.2.5. Recipe Examples</h4></div></div></div><a id="idm225456459936" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-procmail-recipes-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.4.2.5. Recipe Examples</h4></div></div></div><a id="idm261717251328" 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. The proper use and adaptation of regular expressions can be derived by viewing these recipe examples. In addition, introductory information about basic regular expression rules can be found in the <code class="filename">grep(1)</code> man page.
@@ -4531,7 +4551,7 @@ tuxlug</pre><div class="para">
Any messages sent from the <code class="computeroutput">tux-lug at domain.com</code> mailing list are placed in the <code class="filename">tuxlug</code> mailbox automatically for the MUA. Note that the condition in this example matches the message if it has the mailing list's email address on the <code class="computeroutput">From</code>, <code class="computeroutput">Cc</code>, or <code class="computeroutput">To</code> lines.
</div><div class="para">
Consult the many Procmail online resources available in <a class="xref" href="#s1-email-additional-resources">Section 10.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">10.4.2.6. Spam Filters</h4></div></div></div><a id="idm225445385456" class="indexterm"></a><a id="idm225445383536" class="indexterm"></a><a id="idm225445382096" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-mda-spam"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.4.2.6. Spam Filters</h4></div></div></div><a id="idm261733641328" class="indexterm"></a><a id="idm261731003840" class="indexterm"></a><a id="idm261731002400" 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.
@@ -4555,7 +4575,7 @@ tuxlug</pre><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">
+ </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">
See <a class="xref" href="#ch-Services_and_Daemons">Chapter 6, <em>Services and Daemons</em></a> for more information on how to configure services in Fedora.
@@ -4567,28 +4587,28 @@ tuxlug</pre><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">10.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 <span class="application"><strong>Mutt</strong></span> offer SSL-encrypted email sessions.
- </div><a id="idm225452003360" class="indexterm"></a><div class="para">
+ </div><a id="idm261731484848" class="indexterm"></a><div class="para">
Like any other service that flows over a network unencrypted, important email information, such as user names, passwords, and entire messages, may be intercepted and viewed by users on the network. Additionally, since the standard <code class="systemitem">POP</code> and <code class="systemitem">IMAP</code> protocols pass authentication information unencrypted, it is possible for an attacker to gain access to user accounts by collecting user names and passwords as they are passed over the network.
- </div><div class="section" id="s3-email-security-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.5.1.1. Secure Email Clients</h4></div></div></div><a id="idm225461723744" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-email-security-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.5.1.1. Secure Email Clients</h4></div></div></div><a id="idm261739167040" 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">10.5.1.2. Securing Email Client Communications</h4></div></div></div><a id="idm225471397536" class="indexterm"></a><a id="idm225507393200" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-security-servers"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.5.1.2. Securing Email Client Communications</h4></div></div></div><a id="idm261781506400" class="indexterm"></a><a id="idm261787701728" 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.
+ Self-signed certificates should be used for testing purposes only. Any server used in a production environment should use an SSL certificate signed by a CA.
</div></div></div><div class="para">
- To create a self-signed SSL certificate for <code class="systemitem">IMAP</code> or <code class="systemitem">POP</code>, change to the <code class="filename">/etc/pki/dovecot/</code> directory, edit the certificate parameters in the <code class="filename">/etc/pki/dovecot/dovecot-openssl.conf</code> configuration file as you prefer, and type the following commands, as <code class="systemitem">root</code>:
+ To create a self-signed SSL certificate for <code class="systemitem">IMAP</code> or <code class="systemitem">POP</code>, change to the <code class="filename">/etc/pki/dovecot/</code> directory, edit the certificate parameters in the <code class="filename">/etc/pki/dovecot/dovecot-openssl.cnf</code> configuration file as you prefer, and type the following commands, as <code class="systemitem">root</code>:
</div><pre class="screen">dovecot]# <code class="command">rm -f certs/dovecot.pem private/dovecot.pem</code>
dovecot]# <code class="command">/usr/libexec/dovecot/mkcert.sh</code></pre><div class="para">
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">
Issue the following command to restart the <code class="command">dovecot</code> daemon:
- </div><pre class="screen">~]# <code class="command">systemctl restart dovecot</code></pre><div class="para">
- Alternatively, the <code class="command">stunnel</code> command can be used as an SSL encryption wrapper around the standard, non-secure connections to <code class="systemitem">IMAP</code> or <code class="systemitem">POP</code> services.
+ </div><pre class="screen">~]# <code class="command">systemctl restart dovecot</code></pre><div class="para">
+ Alternatively, the <code class="command">stunnel</code> command can be used as an encryption wrapper around the standard, non-secure connections to <code class="systemitem">IMAP</code> or <code class="systemitem">POP</code> services.
</div><div class="para">
The <code class="command">stunnel</code> utility uses external OpenSSL libraries included with Fedora to provide strong cryptography and to protect the network connections. It is recommended to apply to a CA to obtain an SSL certificate, but it is also possible to create a self-signed certificate.
</div><div class="note"><div class="admonition_header"><h2>Installing the stunnel package</h2></div><div class="admonition"><div class="para">
@@ -4613,9 +4633,9 @@ connect = 143</pre><div class="para">
Once you start <code class="command">stunnel</code> with the created configuration file using the <code class="command">stunnel /etc/stunnel/mail.conf</code> command, it will be possible to use an <code class="systemitem">IMAP</code> or a <code class="systemitem">POP</code> email client and connect to the email server using SSL encryption.
</div><div class="para">
For more information on <code class="command">stunnel</code>, see the <code class="filename">stunnel(8)</code> man page or the documents in the <code class="filename">/usr/share/doc/stunnel/</code> directory.
- </div></div></div></div><div class="section" id="s1-email-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.6. Additional Resources</h2></div></div></div><a id="idm225444480848" class="indexterm"></a><a id="idm225444479408" class="indexterm"></a><a id="idm225476468112" class="indexterm"></a><a id="idm225476466672" class="indexterm"></a><div class="para">
+ </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">10.6. Additional Resources</h2></div></div></div><a id="idm261745025312" class="indexterm"></a><a id="idm261740484800" class="indexterm"></a><a id="idm261740483360" class="indexterm"></a><a id="idm261740481920" 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">10.6.1. Installed Documentation</h3></div></div></div><a id="idm225451713296" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><div class="section" id="s2-email-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.6.1. Installed Documentation</h3></div></div></div><a id="idm261755724240" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
Information on configuring Sendmail is included with the <span class="package">sendmail</span> and <span class="package">sendmail-cf</span> packages.
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="filename">/usr/share/sendmail-cf/README</code> — Contains information on the <code class="command">m4</code> macro processor, file locations for Sendmail, supported mailers, how to access enhanced features, and more.
@@ -4639,7 +4659,7 @@ connect = 143</pre><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/</code> — Contains a large amount of information pertaining to SpamAssassin.
- </div></li></ul></div></li></ul></div></div><div class="section" id="s2-email-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.6.2. Useful Websites</h3></div></div></div><a id="idm225479883616" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </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">10.6.2. Useful Websites</h3></div></div></div><a id="idm261738579408" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://www.sendmail.org/">http://www.sendmail.org/</a> — Offers a thorough technical breakdown of Sendmail features, documentation and configuration examples.
</div></li><li class="listitem"><div class="para">
<a href="http://www.sendmail.com/">http://www.sendmail.com/</a> — Contains news, interviews and articles concerning Sendmail, including an expanded view of the many options available.
@@ -4653,7 +4673,7 @@ connect = 143</pre><div class="para">
<a href="http://www.uwasa.fi/~ts/info/proctips.html">http://www.uwasa.fi/~ts/info/proctips.html</a> — Contains dozens of tips that make using Procmail much easier. Includes instructions on how to test <code class="filename">.procmailrc</code> files and use Procmail scoring to decide if a particular action should be taken.
</div></li><li class="listitem"><div class="para">
<a href="http://www.spamassassin.org/">http://www.spamassassin.org/</a> — 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">10.6.3. Related Books</h3></div></div></div><a id="idm225481133904" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </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">10.6.3. Related Books</h3></div></div></div><a id="idm261733584384" 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.
@@ -4663,7 +4683,7 @@ connect = 143</pre><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 11. Directory Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-OpenLDAP">11.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-introduction">11.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-installation">11.1.2. Installing the OpenLDAP Suite</a></span></dt><dt><span class="section"><a href="#s2-ldap-configuration">11.1.3. Configuring an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="#s2-ldap-running">11.1.4. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="#s2-ldap-pam">11.1.5. Configuring a System to Authenticate Using OpenLDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-resources">11.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">11.1. OpenLDAP</h2></div></div></div><a id="idm225472304000" class="indexterm"></a><a id="idm225472305696" class="indexterm"></a><a id="idm225472307088" class="indexterm"></a><a id="idm225446219984" class="indexterm"></a><div class="para">
+ </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 11. Directory Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-OpenLDAP">11.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ldap-introduction">11.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-installation">11.1.2. Installing the OpenLDAP Suite</a></span></dt><dt><span class="section"><a href="#s2-ldap-configuration">11.1.3. Configuring an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="#s2-selinux-openldap">11.1.4. SELinux Policy for Applications Using LDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-running">11.1.5. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="#s2-ldap-pam">11.1.6. Configuring a System to Authentic
ate Using OpenLDAP</a></span></dt><dt><span class="section"><a href="#s2-ldap-resources">11.1.7. Additional Resources</a></span></dt><dt><span class="section"><a href="#s3-ldap-related-books">11.1.8. Related Books</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">11.1. OpenLDAP</h2></div></div></div><a id="idm261757343392" class="indexterm"></a><a id="idm261757894912" class="indexterm"></a><a id="idm261757895408" class="indexterm"></a><a id="idm261757898512" 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.
@@ -4672,24 +4692,24 @@ connect = 143</pre><div class="para">
</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">11.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.
+ Using a client-server architecture, LDAP provides a reliable means to create a central information directory accessible from the network. When a client attempts to modify information within this directory, the server verifies the user has permission to make the change, and then adds or updates the entry as requested. To ensure the communication is secure, the <em class="firstterm">Transport Layer Security</em> (<acronym class="acronym">TLS</acronym>) cryptographic protocol can be used to prevent an attacker from intercepting the transmission.
</div><div class="important"><div class="admonition_header"><h2>Using Mozilla NSS</h2></div><div class="admonition"><div class="para">
- The OpenLDAP suite in Fedora 21 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>.
+ The OpenLDAP suite in Fedora 21 no longer uses OpenSSL. Instead, it uses the Mozilla implementation of <em class="firstterm">Network Security Services</em> (<acronym class="acronym">NSS</acronym>). OpenLDAP continues to work with existing certificates, keys, and other TLS configuration. For more information on how to configure it to use Mozilla certificate and key database, see <a href="http://www.openldap.org/faq/index.cgi?file=1514"><em class="citetitle">How do I use TLS/SSL with Mozilla NSS</em></a>.
</div></div></div><div class="para">
The LDAP server supports several database systems, which gives administrators the flexibility to choose the best suited solution for the type of information they are planning to serve. Because of a well-defined client <em class="firstterm">Application Programming Interface</em> (<acronym class="acronym">API</acronym>), the number of applications able to communicate with an LDAP server is numerous, and increasing in both quantity and quality.
</div><div class="section" id="s3-ldap-terminology"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.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 class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225472705584" class="indexterm"></a>
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261690893312" 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="idm225437891584" class="indexterm"></a>
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261757275664" 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.
+ An attribute can either have a single value, or an unordered space-separated list of values. While certain attributes are optional, others are required. Required attributes are specified using the <code class="option">objectClass</code> definition, and can be found in schema files located in the <code class="filename">/etc/openldap/slapd.d/cn=config/cn=schema/</code> directory.
</div><div class="para">
The assertion of an attribute and its corresponding value is also referred to as a <em class="firstterm">Relative Distinguished Name</em> (<acronym class="acronym">RDN</acronym>). Unlike distinguished names that are unique globally, a relative distinguished name is only unique per entry.
- </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225451505184" class="indexterm"></a>
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261745678640" 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>
@@ -4697,7 +4717,7 @@ connect = 143</pre><div class="para">
<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">11.1.1.2. OpenLDAP Features</h4></div></div></div><a id="idm225467840928" class="indexterm"></a><div class="para">
+ </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">11.1.1.2. OpenLDAP Features</h4></div></div></div><a id="idm261756161008" 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.
@@ -4711,19 +4731,19 @@ connect = 143</pre><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">11.1.1.3. OpenLDAP Server Setup</h4></div></div></div><a id="idm225444164736" class="indexterm"></a><div class="para">
+ </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">11.1.1.3. OpenLDAP Server Setup</h4></div></div></div><a id="idm261731437440" class="indexterm"></a><div class="para">
The typical steps to set up an LDAP server on Fedora are as follows:
</div><div class="procedure"><ol class="1"><li class="step"><div class="para">
Install the OpenLDAP suite. See <a class="xref" href="#s2-ldap-installation">Section 11.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 11.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 11.1.4, “Running an OpenLDAP Server”</a>.
+ Start the <code class="systemitem">slapd</code> service as described in <a class="xref" href="#s2-ldap-running">Section 11.1.5, “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">11.1.2. Installing the OpenLDAP Suite</h3></div></div></div><a id="idm225482070800" class="indexterm"></a><a id="idm225482069824" class="indexterm"></a><div class="para">
+ </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">11.1.2. Installing the OpenLDAP Suite</h3></div></div></div><a id="idm261758792560" class="indexterm"></a><a id="idm261693449264" 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 11.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 class="">
Package
@@ -4756,19 +4776,19 @@ connect = 143</pre><div class="para">
</td><td class="">
A package containing <code class="systemitem">nslcd</code>, a local LDAP name service that allows a user to perform local LDAP queries.
</td></tr><tr><td class="">
- <span class="package">mod_authz_ldap</span>
+ <span class="package">mod_ldap</span>
</td><td class="">
<div class="para">
- A package containing <code class="systemitem">mod_authz_ldap</code>, the LDAP authorization module for the Apache HTTP Server. This module uses the short form of the distinguished name for a subject and the issuer of the client SSL certificate to determine the distinguished name of the user within an LDAP directory. It is also capable of authorizing users based on attributes of that user's LDAP directory entry, determining access to assets based on the user and group privileges of the asset, and denying access for users with expired passwords. Note that the <code class="systemitem">mod_ssl</code> module is required when using the <code class="systemitem">mod_authz_ldap</code> module.
+ A package containing the <code class="systemitem">mod_authnz_ldap</code> and <code class="systemitem">mod_ldap</code> modules. The <code class="systemitem">mod_authnz_ldap</code> module is the LDAP authorization module for the Apache HTTP Server. This module can authenticate users' credentials against an LDAP directory, and can enforce access control based on the user name, full DN, group membership, an arbitrary attribute, or a complete filter string. The <code class="systemitem">mod_ldap</code> module contained in the same package provides a configurable shared memory cache, to avoid repeated directory access across many HTTP requests, and also support for SSL/TLS.
</div>
</td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
To install these packages, use the <code class="command">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 5.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">11.1.2.1. Overview of OpenLDAP Server Utilities</h4></div></div></div><a id="idm225452213488" class="indexterm"></a><div class="para">
+ </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, see <a class="xref" href="#sec-Installing">Section 5.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">11.1.2.1. Overview of OpenLDAP Server Utilities</h4></div></div></div><a id="idm261693087968" 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 11.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 class="">
Command
@@ -4811,14 +4831,14 @@ connect = 143</pre><div class="para">
</td><td class="">
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 11.1.6.1, “Installed Documentation”</a>.
+ For a detailed description of these utilities and their usage, see the corresponding manual pages as referred to in <a class="xref" href="#bh-Installed_Documentation_OpenLDAP">the section called “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">slapadd</code> utility, type the following at a shell prompt:
</div><pre class="screen"><code class="command">chown -R ldap:ldap /var/lib/ldap</code></pre></div></div><div class="warning"><div class="admonition_header"><h2>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 11.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">11.1.2.2. Overview of OpenLDAP Client Utilities</h4></div></div></div><a id="idm225371089280" class="indexterm"></a><div class="para">
+ </div><pre class="screen">~]# <code class="command">systemctl stop slapd.service</code></pre><div class="para">
+ For more information on how to start, stop, restart, and check the current status of the <code class="systemitem">slapd</code> service, see <a class="xref" href="#s2-ldap-running">Section 11.1.5, “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">11.1.2.2. Overview of OpenLDAP Client Utilities</h4></div></div></div><a id="idm261728972384" 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 11.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 class="">
Command
@@ -4866,7 +4886,7 @@ connect = 143</pre><div class="para">
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">11.1.2.3. Overview of Common LDAP Client Applications</h4></div></div></div><a id="idm225479859936" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-ldap-packages-applications"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.2.3. Overview of Common LDAP Client Applications</h4></div></div></div><a id="idm261747850704" 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">11.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:
@@ -4875,24 +4895,24 @@ connect = 143</pre><div class="para">
</th><th class="">
Description
</th></tr></thead><tbody><tr><td class="">
- <a id="idm225455589392" class="indexterm"></a>
+ <a id="idm261757045488" class="indexterm"></a>
<code class="filename">/etc/openldap/ldap.conf</code>
</td><td class="">
The configuration file for client applications that use the OpenLDAP libraries. This includes <code class="command">ldapadd</code>, <code class="command">ldapsearch</code>, <span class="application"><strong>Evolution</strong></span>, etc.
</td></tr><tr><td class="">
- <a id="idm225459296000" class="indexterm"></a>
+ <a id="idm261713154320" class="indexterm"></a>
<code class="filename">/etc/openldap/slapd.d/</code>
</td><td class="">
The directory containing the <code class="systemitem">slapd</code> configuration.
</td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
Note that OpenLDAP no longer reads its configuration from the <code class="filename">/etc/openldap/slapd.conf</code> file. Instead, it uses a configuration database located in the <code class="filename">/etc/openldap/slapd.d/</code> directory. If you have an existing <code class="filename">slapd.conf</code> file from a previous installation, you can convert it to the new format by running the following command as <code class="systemitem">root</code>:
- </div><pre class="screen"><code class="command">slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d/</code></pre><div class="para">
+ </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 11.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">11.1.3.1. Changing the Global Configuration</h4></div></div></div><a id="idm225442213472" class="indexterm"></a><a id="idm225479733040" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s3-ldap-configuration-global"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.3.1. Changing the Global Configuration</h4></div></div></div><a id="idm261728095200" class="indexterm"></a><a id="idm261728097872" class="indexterm"></a><div class="para">
Global configuration options for the LDAP server are stored in the <code class="filename">/etc/openldap/slapd.d/cn=config.ldif</code> file. The following directives are commonly used:
- </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225462457904" class="indexterm"></a>
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261742355488" 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">
@@ -4921,17 +4941,17 @@ connect = 143</pre><div class="para">
<code class="option">proxy_authz_anon</code>
</td><td class="">
Enables processing of anonymous proxy authorization control.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-ldap-configuration-olcallows"><h6>Example 11.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="idm225475403168" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-ldap-configuration-olcallows"><h6>Example 11.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="idm261750687968" 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 11.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="idm225443282576" class="indexterm"></a>
+ </div><div class="example" id="example-ldap-configuration-olcconnmaxpending"><h6>Example 11.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="idm261718757696" 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 11.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="idm225461711712" class="indexterm"></a>
+ </div><div class="example" id="example-ldap-configuration-olcconnmaxpendingauth"><h6>Example 11.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="idm261649638880" 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">
@@ -4956,78 +4976,176 @@ connect = 143</pre><div class="para">
<code class="option">tls_authc</code>
</td><td class="">
Disallows the STARTTLS command when authenticated.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-ldap-configuration-olcdisallows"><h6>Example 11.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="idm225474959936" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-ldap-configuration-olcdisallows"><h6>Example 11.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="idm261759849680" 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 11.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="idm225496252336" class="indexterm"></a>
+ </div><div class="example" id="example-ldap-configuration-olcidletimeout"><h6>Example 11.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="idm261756108240" 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 11.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="idm225424906064" class="indexterm"></a>
+ </div><div class="example" id="example-ldap-configuration-olclogfile"><h6>Example 11.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="idm261649732288" 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 11.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="idm225455454176" class="indexterm"></a>
+ </div><div class="example" id="example-ldap-configuration-olcreferral"><h6>Example 11.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="idm261746175744" 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 11.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">11.1.3.2. Changing the Database-Specific Configuration</h4></div></div></div><a id="idm225467868784" class="indexterm"></a><a id="idm225467870672" class="indexterm"></a><div class="para">
+ </div><div class="example" id="example-ldap-configuration-olcwritetimeout"><h6>Example 11.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">11.1.3.2. Changing the Database-Specific Configuration</h4></div></div></div><a id="idm261724754960" class="indexterm"></a><a id="idm261724916000" class="indexterm"></a><div class="para">
By default, the OpenLDAP server uses Berkeley DB (BDB) as a database back end. The configuration for this database is stored in the <code class="filename">/etc/openldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif</code> file. The following directives are commonly used in a database-specific configuration:
- </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225466879024" class="indexterm"></a>
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261722059024" 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 11.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="idm225455058080" class="indexterm"></a>
+ </div><div class="example" id="example-ldap-configuration-olcreadonly"><h6>Example 11.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="idm261741671936" 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 11.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="idm225434970608" class="indexterm"></a>
+ </div><div class="example" id="example-ldap-configuration-olcrootdn"><h6>Example 11.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="idm261710117088" 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>
+ It accepts either a plain text string, or a hash. To generate a hash, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">slappaswd</code>
New password:
Re-enter new password:
-{SSHA}WczWsyPEnMchFf1GRTweq2q7XJcvmSxD</pre><div class="example" id="example-ldap-configuration-olcrootpw"><h6>Example 11.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="idm225453080016" class="indexterm"></a>
+{SSHA}WczWsyPEnMchFf1GRTweq2q7XJcvmSxD</pre><div class="example" id="example-ldap-configuration-olcrootpw"><h6>Example 11.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="idm261783461936" 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 11.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">11.1.3.3. Extending Schema</h4></div></div></div><a id="idm225478783168" class="indexterm"></a><a id="idm225478785616" class="indexterm"></a><div class="para">
- Since OpenLDAP 2.3, the <code class="filename">/etc/openldap/slapd.d/</code> directory also contains LDAP definitions that were previously located in <code class="filename">/etc/openldap/schema/</code>. It is possible to extend the schema used by OpenLDAP to support additional attribute types and object classes using the default schema files as a guide. However, this task is beyond the scope of this chapter. For more information on this topic, refer to <a href="http://www.openldap.org/doc/admin/schema.html">http://www.openldap.org/doc/admin/schema.html</a>.
- </div></div></div><div class="section" id="s2-ldap-running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.1.4. Running an OpenLDAP Server</h3></div></div></div><a id="idm225445487296" 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 6, <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">11.1.4.1. Starting the Service</h4></div></div></div><a id="idm225462120544" 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">
+ </div><div class="example" id="example-ldap-configuration-olcsuffix"><h6>Example 11.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">11.1.3.3. Extending Schema</h4></div></div></div><a id="idm261751449456" class="indexterm"></a><a id="idm261751450112" class="indexterm"></a><div class="para">
+ Since OpenLDAP 2.3, the <code class="filename">/etc/openldap/slapd.d/</code> directory also contains LDAP definitions that were previously located in <code class="filename">/etc/openldap/schema/</code>. It is possible to extend the schema used by OpenLDAP to support additional attribute types and object classes using the default schema files as a guide. However, this task is beyond the scope of this chapter. For more information on this topic, see <a href="http://www.openldap.org/doc/admin/schema.html">http://www.openldap.org/doc/admin/schema.html</a>.
+ </div></div><div class="section" id="s3-establishing_a_secure_connection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.3.4. Establishing a Secure Connection</h4></div></div></div><a id="idm261701125152" class="indexterm"></a><a id="idm261721834384" class="indexterm"></a><a id="idm261721836048" class="indexterm"></a><a id="idm261721837264" class="indexterm"></a><div class="para">
+ OpenLDAP clients and servers can be secured using the Transport Layer Security (TLS) framework. TLS is a cryptographic protocol designed to provide communication security over the network. As noted above, OpenLDAP suite in Fedora uses Mozilla NSS as the TLS implementation.
+ </div><div class="para">
+ To establish a secure connection using TLS, obtain the required certificates as described in <a href="http://www.openldap.org/faq/index.cgi?file=1514"><em class="citetitle">How do I use TLS/SSL with Mozilla NSS</em></a>. Then, a number of options must be configured on both the client and the server. At a minimum, a server must be configured with the Certificate Authority (CA) certificates and also its own server certificate and private key. The clients must be configured with the name of the file containing all the trusted CA certificates.
+ </div><div class="para">
+ Typically, a server only needs to sign a single CA certificate. A client may want to connect to a variety of secure servers, therefore it is common to specify a list of several trusted CAs in its configuration.
+ </div><h5 id="br-server_configuration">Server Configuration</h5><div class="para">
+ This section lists global configuration directives for <code class="systemitem">slapd</code> that need to be specified in the <code class="filename">/etc/openldap/slapd.d/cn=config.ldif</code> file on an OpenLDAP server in order to establish TLS.
+ </div><div class="para">
+ While the old style configuration uses a single file, normally installed as <code class="filename">/usr/local/etc/openldap/slapd.conf</code>, the new style uses a slapd backend database to store the configuration. The configuration database normally resides in the <code class="filename">/usr/local/etc/openldap/slapd.d/</code> directory.
+ </div><div class="para">
+ The following directives are also valid for establishing SSL. In addition to TLS directives, you need to enable a port dedicated to SSL on the server side – typically it is port 636. To do so, edit the <code class="filename">/etc/sysconfig/slapd</code> file and append the <code class="literal">ldaps:///</code> string to the list of URLs specified with the <code class="option">SLAPD_URLS</code> directive.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">olcTLSCACertificateFile</code> </span></dt><dd><div class="para">
+ The <code class="option">olcTLSCACertificateFile</code> directive specifies the file encoded with Privacy-Enhanced Mail (PEM) schema that contains trusted CA certificates. The directive takes the following form:
+ </div><pre class="synopsis"><code class="option">olcTLSCACertificateFile</code>: <em class="replaceable"><code>path</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> either with a path to the CA certificate file, or, if you use Mozilla NSS, with a certificate name.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">olcTLSCACertificatePath</code> </span></dt><dd><div class="para">
+ The <code class="option">olcTLSCACertificatePath</code> directive specifies the path to a directory containing individual CA certificates in separate files. This directory must be specially managed with the OpenSSL <span class="application"><strong>c_rehash</strong></span> utility that generates symbolic links with the hashed names that point to the actual certificate files. In general, it is simpler to use the <code class="option">olcTLSCACertificateFile</code> directive instead.
+ </div><div class="para">
+ If Mozilla NSS is used, <code class="option">olcTLSCACertificatePath</code> accepts a path to the Mozilla NSS database (as shown in <a class="xref" href="#ex-using_olcTLSCACertificatePath_with_Mozilla_NSS">Example 11.13, “Using olcTLSCACertificatePath with Mozilla NSS”</a>). In such a case, <span class="application"><strong>c_rehash</strong></span> is not needed.
+ </div><div class="para">
+ The directive takes the following form:
+ </div><pre class="synopsis"><code class="option">olcTLSCACertificatePath</code>: <em class="replaceable"><code>path</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a path to the directory containing the CA certificate files, or with a path to a Mozilla NSS database file.
+ </div><div class="example" id="ex-using_olcTLSCACertificatePath_with_Mozilla_NSS"><h6>Example 11.13. Using olcTLSCACertificatePath with Mozilla NSS</h6><div class="example-contents"><div class="para">
+ With Mozilla NSS, the <code class="option">olcTLSCACertificatePath</code> directive specifies the path of the directory containing the NSS certificate and key database files. For example:
+ </div><pre class="synopsis"><code class="option">olcTLSCACertificatePath</code>: <code class="filename">sql:/home/nssdb/sharednssdb</code></pre><div class="para">
+ The <code class="command">certutil</code> command is used to add a CA certificate to these NSS database files:
+ </div><pre class="synopsis"><code class="command">certutil</code> <code class="option">-d</code> <code class="filename">sql:/home/nssdb/sharednssdb</code> <code class="option">-A</code> <code class="option">-n</code> "<em class="replaceable"><code>CA_certificate</code></em>" <code class="option">-t</code> <code class="literal">CT,,</code> <code class="option">-a</code> <code class="option">-i</code> <code class="filename">certificate.pem</code></pre><div class="para">
+ The above command adds a CA certificate stored in a PEM-formatted file named <em class="replaceable"><code>certificate.pem</code></em>. The <code class="option">-d</code> option specifies the database directory containing the certificate and key database files, the <code class="option">-n</code> option sets a name for the certificate, <code class="option">-t</code> <code class="literal">CT,,</code> means that the certificate is trusted to be used in TLS clients and servers. The <code class="option">-A</code> option adds an existing certificate to a certificate database, the <code class="option">-a</code> option allows the use of ASCII format for input or output, and the <code class="option">-i</code> option passes the <code class="filename">certificate.pem</code> input file to the command.
+ </div></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <code class="option">olcTLSCertificateFile</code> </span></dt><dd><div class="para">
+ The <code class="option">olcTLSCertificateFile</code> directive specifies the file that contains the <code class="systemitem">slapd</code> server certificate. The directive takes the following form:
+ </div><pre class="synopsis"><code class="option">olcTLSCertificateFile</code>: <em class="replaceable"><code>path</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a path to the <code class="systemitem">slapd</code> server certificate file, or, if you use Mozilla NSS, with a certificate name.
+ </div><div class="example" id="ex-using_olcTLSCertificateFile_with_Mozilla_NSS"><h6>Example 11.14. Using olcTLSCertificateFile with Mozilla NSS</h6><div class="example-contents"><div class="para">
+ When using Mozilla NSS with certificate and key database files specified with the <code class="option">olcTLSCACertificatePath</code> directive, <code class="option">olcTLSCertificateFile</code> is used to specify the name of the certificate to use. First, execute the following command to view a list of certificates available in your NSS database file:
+ </div><pre class="synopsis"><code class="command">certutil</code> <code class="option">-d</code> <code class="filename">sql:/home/nssdb/sharednssdb</code> <code class="option">-L</code></pre><div class="para">
+ Select a certificate from the list and pass its name to <code class="option">olcTLSCertificateFile</code>. For example:
+ </div><pre class="synopsis"><code class="command">olcTLSCertificateFile</code> <span class="emphasis"><em>slapd_cert</em></span></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <code class="option">olcTLSCertificateKeyFile</code> </span></dt><dd><div class="para">
+ The <code class="option">olcTLSCertificateKeyFile</code> directive specifies the file that contains the private key that matches the certificate stored in the file specified with <code class="option">olcTLSCertificateFile</code>. Note that the current implementation does not support encrypted private keys, and therefore the containing file must be sufficiently protected. The directive takes the following form:
+ </div><pre class="synopsis"><code class="option">olcTLSCertificateKeyFile</code>: <em class="replaceable"><code>path</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a path to the private key file if you use PEM certificates. When using Mozilla NSS, <em class="replaceable"><code>path</code></em> stands for the name of a file that contains the password for the key for the certificate specified with the <code class="option">olcTLSCertificateFile</code> directive (see <a class="xref" href="#ex-using_olcTLSCertificateKeyFile_with_Mozilla_NSS">Example 11.15, “Using olcTLSCertificateKeyFile with Mozilla NSS”</a>).
+ </div><div class="example" id="ex-using_olcTLSCertificateKeyFile_with_Mozilla_NSS"><h6>Example 11.15. Using olcTLSCertificateKeyFile with Mozilla NSS</h6><div class="example-contents"><div class="para">
+ When using Mozilla NSS, this directive specifies the name of a file that contains the password for the key for the certificate specified with <code class="option">olcTLSCertificateFile</code>:
+ </div><pre class="synopsis"><code class="option">olcTLSCertificateKeyFile</code>: <span class="emphasis"><em>slapd_cert_key</em></span></pre><div class="para">
+ The <code class="command">modutil</code> command can be used to turn off password protection or to change the password for NSS database files. For example:
+ </div><pre class="synopsis"><code class="command">modutil</code> <code class="option">-dbdir</code> <code class="filename">sql:/home/nssdb/sharednssdb</code> <code class="option">-changepw</code></pre></div></div><br class="example-break" /></dd></dl></div><h5 id="br-client_configuration">Client Configuration</h5><div class="para">
+ Specify the following directives in the <code class="filename">/etc/openldap/ldap.conf</code> configuration file on the client system. Most of these directives are parallel to the server configuration options. Directives in<code class="filename">/etc/openldap/ldap.conf</code> are configured on a system-wide basis, however, individual users may override them in their <code class="filename">~/.ldaprc</code> files.
+ </div><div class="para">
+ The same directives can be used to establish an SSL connection. The <code class="literal">ldaps://</code> string must be used instead of <code class="literal">ldap://</code> in OpenLDAP commands such as <code class="command">ldapsearch</code>. This forces commands to use the default port for SSL, port 636, configured on the server.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">TLS_CACERT</code> </span></dt><dd><div class="para">
+ The <code class="option">TLS_CACERT</code> directive specifies a file containing certificates for all of the Certificate Authorities the client will recognize. This is equivalent to the <code class="option">olcTLSCACertificateFile</code> directive on a server. <code class="option">TLS_CACERT</code> should always be specified before <code class="option">TLS_CACERTDIR</code> in <code class="filename">/etc/openldap/ldap.conf</code>. The directive takes the following form:
+ </div><pre class="synopsis"><code class="option">TLS_CACERT</code> <em class="replaceable"><code>path</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a path to the CA certificate file.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">TLS_CACERTDIR</code> </span></dt><dd><div class="para">
+ The <code class="option">TLS_CACERTDIR</code> directive specifies the path to a directory that contains Certificate Authority certificates in separate files. As with <code class="option">olcTLSCACertificatePath</code> on a server, the specified directory must be managed with the OpenSSL <span class="application"><strong>c_rehash</strong></span> utility. Path to Mozilla NSS database file is also accepted, <span class="application"><strong>c_rehash</strong></span> is not needed in such case. The directive takes the following form:
+ </div><pre class="synopsis"><code class="option">TLS_CACERTDIR</code> <em class="replaceable"><code>directory</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>directory</code></em> with a path to the directory containing CA certificate files. With Mozilla NSS, <em class="replaceable"><code>directory</code></em> stands for a path to the certificate or key database file.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">TLS_CERT</code> </span></dt><dd><div class="para">
+ The <code class="option">TLS_CERT</code> specifies the file that contains a client certificate. This directive can only be specified in a user's <code class="filename">~/.ldaprc</code> file. With Mozilla NSS, this directive specifies the name of the certificate to be chosen from the database specified with the aforementioned <code class="option">TLS_CACERTDIR</code> directive. The directive takes the following form:
+ </div><pre class="synopsis"><code class="option">TLS_CERT</code> <em class="replaceable"><code>path</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a path to the client certificate file, or with a name of a certificate from the NSS database.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">TLS_KEY</code> </span></dt><dd><div class="para">
+ The <code class="option">TLS_KEY</code> specifies the file that contains the private key that matches the certificate stored in the file specified with the <code class="option">TLS_CERT</code> directive. As with <code class="option">olcTLSCertificateFile</code> on a server, encrypted key files are not supported, so the file itself must be carefully protected. This option is only configurable in a user's <code class="filename">~/.ldaprc</code> file.
+ </div><div class="para">
+ When using Mozilla NSS, <code class="option">TLS_KEY</code> specifies the name of a file that contains the password for the private key that protects the certificate specified with the <code class="option">TLS_CERT</code> directive. Similarly to the <code class="option">olcTLSCertificateKeyFile</code> directive on a server (see <a class="xref" href="#ex-using_olcTLSCertificateKeyFile_with_Mozilla_NSS">Example 11.15, “Using olcTLSCertificateKeyFile with Mozilla NSS”</a>), you can use the <code class="command">modutil</code> command to manage this password.
+ </div><div class="para">
+ The <code class="option">TLS_KEY</code> directive takes the following form:
+ </div><pre class="synopsis"><code class="option">TLS_KEY</code> <em class="replaceable"><code>path</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a path to the client certificate file or with a name of the password file in the NSS database.
+ </div></dd></dl></div></div><div class="section" id="s3-setting_up_replication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.3.5. Setting Up Replication</h4></div></div></div><a id="idm261738899232" class="indexterm"></a><a id="idm261712845648" class="indexterm"></a><a id="idm261712847360" class="indexterm"></a><div class="para">
+ Replication is the process of copying updates from one LDAP server (<span class="emphasis"><em>provider</em></span>) to one or more other servers or clients (<span class="emphasis"><em>consumers</em></span>). A provider replicates directory updates to consumers, the received updates can be further propagated by the consumer to other servers, so a consumer can also act simultaneously as a provider. Also, a consumer does not have to be an LDAP server, it may be just an LDAP client. In OpenLDAP, you can use several replication modes, most notable are <span class="emphasis"><em>mirror</em></span> and <span class="emphasis"><em>sync</em></span>. For more information on OpenLDAP replication modes, see the <span class="emphasis"><em>OpenLDAP Software Administrator's Guide</em></span> installed with <span class="package">openldap-servers</span> package (see <a class="xref" href="#bh-Installed_Documentation_OpenLDAP">the section called “Installed Documentation”</a>).
+ </div><div class="para">
+ To enable a chosen replication mode, use one of the following directives in <code class="filename">/etc/openldap/slapd.d/</code> on both provider and consumers.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">olcMirrorMode</code> </span></dt><dd><div class="para">
+ The <code class="option">olcMirrorMode</code> directive enables the mirror replication mode. It takes the following form:
+ </div><pre class="synopsis"><code class="option">olcMirrorMode</code> <code class="option">on</code></pre><div class="para">
+ This option needs to be specified both on provider and consumers. Also a <code class="option">serverID</code> must be specified along with <code class="option">syncrepl</code> options. Find a detailed example in the <span class="emphasis"><em>18.3.4. MirrorMode</em></span> section of the <span class="emphasis"><em>OpenLDAP Software Administrator's Guide</em></span> (see <a class="xref" href="#bh-Installed_Documentation_OpenLDAP">the section called “Installed Documentation”</a>).
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">olcSyncrepl</code> </span></dt><dd><div class="para">
+ The <code class="option">olcSyncrepl</code> directive enables the sync replication mode. It takes the following form:
+ </div><pre class="synopsis"><code class="option">olcSyncrepl</code> <code class="option">on</code></pre><div class="para">
+ The sync replication mode requires a specific configuration on both the provider and the consumers. This configuration is thoroughly described in the <span class="emphasis"><em>18.3.1. Syncrepl</em></span> section of the <span class="emphasis"><em>OpenLDAP Software Administrator's Guide</em></span> (see <a class="xref" href="#bh-Installed_Documentation_OpenLDAP">the section called “Installed Documentation”</a>).
+ </div></dd></dl></div></div><div class="section" id="s3-loading_modules_or_backends"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.3.6. Loading Modules and Backends</h4></div></div></div><a id="idm261752841168" class="indexterm"></a><a id="idm261752842864" class="indexterm"></a><a id="idm261734449264" class="indexterm"></a><a id="idm261734450192" class="indexterm"></a><div class="para">
+ You can enhance the <code class="systemitem">slapd</code> service with dynamically loaded modules. Support for these modules must be enabled with the <code class="option">--enable-modules</code> option when configuring <code class="systemitem">slapd</code>. Modules are stored in files with the <span class="emphasis"><em>.la</em></span> extension:
+ </div><pre class="synopsis"><em class="replaceable"><code>module_name</code></em>.la</pre><div class="para">
+ <em class="firstterm">Backends</em> store or retrieve data in response to LDAP requests. Backends may be compiled statically into <code class="systemitem">slapd</code>, or when module support is enabled, they may be dynamically loaded. In the latter case, the following naming convention is applied:
+ </div><pre class="synopsis">back_<em class="replaceable"><code>backend_name</code></em>.la</pre><div class="para">
+ To load a module or a backend, use the following directive in <code class="filename">/etc/openldap/slapd.d/</code>:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">olcModuleLoad</code> </span></dt><dd><div class="para">
+ The <code class="option">olcModuleLoad</code> directive specifies a dynamically loadable module to load. It takes the following form:
+ </div><pre class="synopsis"><code class="option">olcModuleLoad</code>: <em class="replaceable"><code>module</code></em></pre><div class="para">
+ Here, <em class="replaceable"><code>module</code></em> stands either for a file containing the module, or a backend, that will be loaded.
+ </div></dd></dl></div></div></div><div class="section" id="s2-selinux-openldap"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.1.4. SELinux Policy for Applications Using LDAP</h3></div></div></div><div class="para">
+ SELinux is an implementation of a mandatory access control mechanism in the Linux kernel. By default, SELinux prevents applications from accessing an OpenLDAP server. To enable authentication through LDAP, which is required by several applications, the <code class="systemitem">allow_ypbind</code> SELinux Boolean needs to be enabled. Certain applications also demand an enabled <code class="systemitem">authlogin_nsswitch_use_ldap</code> Boolean in this scenario. Execute the following commands to enable the aforementioned Booleans:
+ </div><pre class="synopsis">~]# <code class="command">setsebool</code> <code class="option">-P</code> <code class="option">allow_ypbind</code>=<code class="literal">1</code></pre><pre class="synopsis">~]# <code class="command">setsebool</code> <code class="option">-P</code> <code class="option">authlogin_nsswitch_use_ldap</code>=<code class="literal">1</code></pre><div class="para">
+ The <code class="option">-P</code> option makes this setting persistent across system reboots. See the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SELinux_Users_and_Administrators_Guide/">Red Hat Enterprise Linux 7 SELinux User's and Administrator's Guide</a> for more detailed information about SELinux.
+ </div></div><div class="section" id="s2-ldap-running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.1.5. Running an OpenLDAP Server</h3></div></div></div><a id="idm261687242224" class="indexterm"></a><div class="para">
+ This section describes how to start, stop, restart, and check the current status of the <span class="application"><strong>Standalone LDAP Daemon</strong></span>. For more information on how to manage system services in general, see <a class="xref" href="#ch-Services_and_Daemons">Chapter 6, <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">11.1.5.1. Starting the Service</h4></div></div></div><a id="idm261755411632" class="indexterm"></a><div class="para">
+ To start the <code class="systemitem">slapd</code> service in the current session, type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">systemctl start slapd.service</code></pre><div class="para">
+ To configure the service to start automatically at the boot time, use the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">systemctl enable slapd.service</code></pre><div class="para">
See <a class="xref" href="#ch-Services_and_Daemons">Chapter 6, <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">11.1.4.2. Stopping the Service</h4></div></div></div><a id="idm225371906496" 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">
+ </div></div><div class="section" id="s3-ldap-running-stopping"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.5.2. Stopping the Service</h4></div></div></div><a id="idm261744565728" class="indexterm"></a><div class="para">
+ To stop the running <code class="systemitem">slapd</code> service in the current session, type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">systemctl stop slapd.service</code></pre><div class="para">
+ To prevent the service from starting automatically at the boot time, type as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">systemctl disable slapd.service</code>
+rm '/etc/systemd/system/multi-user.target.wants/slapd.service'</pre><div class="para">
See <a class="xref" href="#ch-Services_and_Daemons">Chapter 6, <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">11.1.4.3. Restarting the Service</h4></div></div></div><a id="idm225438759392" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-ldap-running-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.5.3. Restarting the Service</h4></div></div></div><a id="idm261731038848" 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">11.1.4.4. Checking the Service Status</h4></div></div></div><a id="idm225454537472" 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">11.1.5. Configuring a System to Authenticate Using OpenLDAP</h3></div></div></div><div class="para">
+ </div><pre class="screen">~]# <code class="command">systemctl restart slapd.service</code></pre><div class="para">
+ This stops the service and immediately starts it again. Use this command to reload the configuration.
+ </div></div><div class="section" id="s3-ldap-running-status"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.5.4. Verifying the Service Status</h4></div></div></div><a id="idm261649680848" class="indexterm"></a><div class="para">
+ To verify that the <code class="systemitem">slapd</code> service is running, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">systemctl is-active slapd.service</code>
+active</pre></div></div><div class="section" id="s2-ldap-pam"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.1.6. 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 11.1.2, “Installing the OpenLDAP Suite”</a> and <a class="xref" href="#s2-ldap-configuration">Section 11.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="section" id="s3-ldap-migrationtools"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.5.1. Migrating Old Authentication Information to LDAP Format</h4></div></div></div><a id="idm225372611984" class="indexterm"></a><div class="para">
+ </div><pre class="screen">~]# <code class="command">yum install openldap openldap-clients nss-pam-ldapd</code></pre><div class="section" id="s3-ldap-migrationtools"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.6.1. Migrating Old Authentication Information to LDAP Format</h4></div></div></div><a id="idm261751099936" 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">
+ </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";
@@ -5035,9 +5153,9 @@ $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>
+ </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 11.8, “Commonly used LDAP migration scripts”</a>.
+ To decide which script to run in order to migrate the user database, see <a class="xref" href="#table-ldap-migrationtools">Table 11.8, “Commonly used LDAP migration scripts”</a>.
</div><div class="table" id="table-ldap-migrationtools"><h6>Table 11.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 class="">
Existing Name Service
</th><th class="">
@@ -5081,72 +5199,72 @@ $DEFAULT_BASE = "dc=example,dc=com";</pre><div class="para">
</td><td class="">
<code class="filename">migrate_all_nis_offline.sh</code>
</td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
- For more information on how to use these scripts, refer to the <code class="filename">README</code> and the <code class="filename">migration-tools.txt</code> files in the <code class="filename">/usr/share/doc/migrationtools/</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">11.1.6. Additional Resources</h3></div></div></div><div class="para">
+ For more information on how to use these scripts, see the <code class="filename">README</code> and the <code class="filename">migration-tools.txt</code> files in the <code class="filename">/usr/share/doc/migrationtools/</code> directory.
+ </div></div></div><div class="section" id="s2-ldap-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.1.7. 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">11.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 class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/openldap-servers/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/README.schema</code></span></dt><dd><div class="para">
- A README file containing the description of installed schema files.
- </div></dd></dl></div><div class="para">
- Additionally, there is also a number of manual pages that are installed with the <span class="package">openldap</span>, <span class="package">openldap-servers</span>, and <span class="package">openldap-clients</span> packages:
- </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">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">11.1.6.2. Useful Websites</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.openldap.org/doc/admin24/">http://www.openldap.org/doc/admin24/</a></span></dt><dd><div class="para">
- 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://www.kingsmountain.com/ldapRoadmap.shtml</a></span></dt><dd><div class="para">
- Jeff Hodges' <em class="citetitle">LDAP Roadmap & FAQ</em> containing links to several useful resources and emerging news concerning the LDAP protocol.
- </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.ldapman.org/articles/">http://www.ldapman.org/articles/</a></span></dt><dd><div class="para">
- A collection of articles that offer a good introduction to LDAP, including methods to design a directory tree and customizing directory structures.
- </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.padl.com/">http://www.padl.com/</a></span></dt><dd><div class="para">
- 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">11.1.6.3. Related Books</h4></div></div></div><div class="variablelist"><dl class="variablelist"><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 12. File and Print Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-Samba">12.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="#samba-rgs-overview">12.1.1. Introduction to Samba</a></span></dt><dt><span class="section"><a href="#s2-samba-daemons">12.1.2. Samba Daemons and Related Services</a></span></dt><dt><span class="section"><a href="#s2-samba-connect-share">12.1.3. Connecting to a Samba Share</a></span></dt><dt><span class="section"><a href="#s2-samba-configuring">12.1.4. Configuring a Samba Server</a></span></dt><dt><span class="section"><a href="#s2-samba-startstop">12.1.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="#s2-samba-servers">12.1.6. Samba Server Types and the <co
de class="filename">smb.conf</code> File</a></span></dt><dt><span class="section"><a href="#s2-samba-security-modes">12.1.7. Samba Security Modes</a></span></dt><dt><span class="section"><a href="#s2-samba-account-info-dbs">12.1.8. Samba Account Information Databases</a></span></dt><dt><span class="section"><a href="#s2-samba-network-browsing">12.1.9. Samba Network Browsing</a></span></dt><dt><span class="section"><a href="#s2-samba-cups">12.1.10. Samba with CUPS Printing Support</a></span></dt><dt><span class="section"><a href="#s2-samba-programs">12.1.11. Samba Distribution Programs</a></span></dt><dt><span class="section"><a href="#s2-samba-resources">12.1.12. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-FTP">12.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-protocol">12.2.1. The File Transfer Protocol</a></span></dt><dt><span class="section"><a href="#s2-ftp-servers">12.2.2. FTP Servers</a></span></dt><dt>
<span class="section"><a href="#s3-ftp-vsftpd-conf">12.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-start">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf">12.2.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-resources">12.2.6. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Printer_Configuration">12.3. Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Starting_Printer_Config">12.3.1. Starting the Printer Configuration Tool</a></span></dt><dt><span class="section"><a href="#sec-Setting_Printer">12.3.2. Starting Printer Setup</a></span></dt><dt><span class="section"><a href="#sec-Adding_Other_Printer">12.3.3. Adding a Local Printer</a></span></dt><dt><span class="s
ection"><a href="#s1-printing-jetdirect-printer">12.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="#s1-printing-ipp-printer">12.3.5. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="#sec-printing-LPDLPR-printer">12.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-smb-printer">12.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="#s1-printing-select-model">12.3.8. Selecting the Printer Model and Finishing</a></span></dt><dt><span class="section"><a href="#s1-printing-test-page">12.3.9. Printing a Test Page</a></span></dt><dt><span class="section"><a href="#s1-printing-edit">12.3.10. Modifying Existing Printers</a></span></dt><dt><span class="section"><a href="#s1-printing-additional-resources">12.3.11. Additional Resources</a></span></dt></dl></dd></dl></div><div class="para">
+ </div><h3 id="bh-Installed_Documentation_OpenLDAP">Installed Documentation</h3><div class="para">
+ The following documentation is installed with the <span class="package">openldap-servers</span> package:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/openldap-servers/guide.html</code> — A copy of the <em class="citetitle">OpenLDAP Software Administrator's Guide</em>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/openldap-servers/README.schema</code> — A README file containing the description of installed schema files.
+ </div></li></ul></div><div class="para">
+ Additionally, there is also a number of manual pages that are installed with the <span class="package">openldap</span>, <span class="package">openldap-servers</span>, and <span class="package">openldap-clients</span> packages:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Client Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldapadd</span>(1)</span> — The manual page for the <code class="command">ldapadd</code> command describes how to add entries to an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldapdelete</span>(1)</span> — The manual page for the <code class="command">ldapdelete</code> command describes how to delete entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldapmodify</span>(1)</span> — The manual page for the <code class="command">ldapmodify</code> command describes how to modify entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldapsearch</span>(1)</span> — The manual page for the <code class="command">ldapsearch</code> command describes how to search for entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldappasswd</span>(1)</span> — The manual page for the <code class="command">ldappasswd</code> command describes how to set or change the password of an LDAP user.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldapcompare</span>(1)</span> — Describes how to use the <code class="command">ldapcompare</code> tool.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldapwhoami</span>(1)</span> — Describes how to use the <code class="command">ldapwhoami</code> tool.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldapmodrdn</span>(1)</span> — Describes how to modify the RDNs of entries.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Server Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">slapd</span>(8C)</span> — Describes command line options for the LDAP server.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Administrative Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">slapadd</span>(8C)</span> — Describes command line options used to add entries to a <code class="command">slapd</code> database.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">slapcat</span>(8C)</span> — Describes command line options used to generate an LDIF file from a <code class="command">slapd</code> database.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">slapindex</span>(8C)</span> — Describes command line options used to regenerate an index based upon the contents of a <code class="command">slapd</code> database.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">slappasswd</span>(8C)</span> — Describes command line options used to generate user passwords for LDAP directories.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Configuration Files</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldap.conf</span>(5)</span> — The manual page for the <code class="filename">ldap.conf</code> file describes the format and options available within the configuration file for LDAP clients.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">slapd-config</span>(5)</span> — Describes the format and options available within the <code class="filename">/etc/openldap/slapd.d</code> configuration directory.
+ </div></li></ul></div></dd></dl></div><h3 id="bh-Online_Documentation_OpenLDAP">Online Documentation</h3><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.openldap.org/doc/admin24/">http://www.openldap.org/doc/admin24/</a></span></dt><dd><div 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://www.kingsmountain.com/ldapRoadmap.shtml</a></span></dt><dd><div class="para">
+ Jeff Hodges' <em class="citetitle">LDAP Roadmap & FAQ</em> containing links to several useful resources and emerging news concerning the LDAP protocol.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.ldapman.org/articles/">http://www.ldapman.org/articles/</a></span></dt><dd><div class="para">
+ A collection of articles that offer a good introduction to LDAP, including methods to design a directory tree and customizing directory structures.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.padl.com/">http://www.padl.com/</a></span></dt><dd><div class="para">
+ 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"><h3 class="title">11.1.8. Related Books</h3></div></div></div><div class="variablelist"><dl class="variablelist"><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 xml:lang="en-US" class="chapter" id="ch-File_and_Print_Servers" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 12. File and Print Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-Samba">12.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="#samba-rgs-overview">12.1.1. Introduction to Samba</a></span></dt><dt><span class="section"><a href="#s2-samba-daemons">12.1.2. Samba Daemons and Related Services</a></span></dt><dt><span class="section"><a href="#s2-samba-connect-share">12.1.3. Connecting to a Samba Share</a></span></dt><dt><span class="section"><a href="#s2-samba-configuring">12.1.4. Configuring a Samba Server</a></span></dt><dt><span class="section"><a href="#s2-samba-startstop">12.1.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="#s2-samba-servers">12.1.6. Samba Server Types and the <code clas
s="filename">smb.conf</code> File</a></span></dt><dt><span class="section"><a href="#s2-samba-security-modes">12.1.7. Samba Security Modes</a></span></dt><dt><span class="section"><a href="#s2-samba-account-info-dbs">12.1.8. Samba Account Information Databases</a></span></dt><dt><span class="section"><a href="#s2-samba-network-browsing">12.1.9. Samba Network Browsing</a></span></dt><dt><span class="section"><a href="#s2-samba-cups">12.1.10. Samba with CUPS Printing Support</a></span></dt><dt><span class="section"><a href="#s2-samba-programs">12.1.11. Samba Distribution Programs</a></span></dt><dt><span class="section"><a href="#s2-samba-resources">12.1.12. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-FTP">12.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-ftp-protocol">12.2.1. The File Transfer Protocol</a></span></dt><dt><span class="section"><a href="#s2-ftp-servers">12.2.2. FTP Servers</a></span></dt><dt><span c
lass="section"><a href="#s3-ftp-vsftpd-conf">12.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-start">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="#s2-ftp-vsftpd-conf">12.2.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dt><span class="section"><a href="#s2-ftp-resources">12.2.6. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Printer_Configuration">12.3. Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Starting_Printer_Config">12.3.1. Starting the Printers Configuration Tool</a></span></dt><dt><span class="section"><a href="#sec-Setting_Printer">12.3.2. Starting Printer Setup</a></span></dt><dt><span class="section"><a href="#sec-Adding_Other_Printer">12.3.3. Adding a Local Printer</a></span></dt><dt><span class="section
"><a href="#s1-printing-jetdirect-printer">12.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="#s1-printing-ipp-printer">12.3.5. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="#sec-printing-LPDLPR-printer">12.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="#s1-printing-smb-printer">12.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="#s1-printing-select-model">12.3.8. Selecting the Printer Model and Finishing</a></span></dt><dt><span class="section"><a href="#s1-printing-test-page">12.3.9. Printing a Test Page</a></span></dt><dt><span class="section"><a href="#s1-printing-edit">12.3.10. Modifying Existing Printers</a></span></dt><dt><span class="section"><a href="#s1-printing-additional-resources">12.3.11. Additional Resources</a></span></dt></dl></dd></dl></div><div class="para">
This chapter guides you through the installation and configuration of <span class="application"><strong>Samba</strong></span>, an open source implementation of the <em class="firstterm">Server Message Block</em> (<acronym class="acronym">SMB</acronym>) and <em class="firstterm">common Internet file system</em> (<code class="systemitem">CIFS</code>) protocol, and <span class="application"><strong>vsftpd</strong></span>, the primary FTP server shipped with Fedora. Additionally, it explains how to use the <span class="application"><strong>Printer</strong></span> tool to configure printers.
- </div><div xml:lang="en-US" class="section" id="s1-Samba" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.1. Samba</h2></div></div></div><a id="idm225475894080" class="indexterm"></a><a id="idm225475897584" class="indexterm"></a><div class="para">
+ </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">12.1. Samba</h2></div></div></div><a id="idm261754441120" class="indexterm"></a><a id="idm261754444672" class="indexterm"></a><div class="para">
<span class="application"><strong>Samba</strong></span> is an open source implementation of the <em class="firstterm">server message block</em> (<code class="systemitem">SMB</code>) protocol. Modern versions of this protocol are also known as the <em class="firstterm">common Internet file system</em> (<code class="systemitem">CIFS</code>) protocol. It allows the networking of Microsoft <span class="trademark">Windows</span>®, Linux, UNIX, and other operating systems together, enabling access to Windows-based file and printer shares. Samba's use of <code class="systemitem">SMB</code> allows it to appear as a Windows server to Windows clients.
</div><div class="note"><div class="admonition_header"><h2>Installing the samba package</h2></div><div class="admonition"><div class="para">
In order to use <span class="application"><strong>Samba</strong></span>, first ensure the <span class="package">samba</span> package is installed on your system by running, as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">yum install samba</code></pre><div class="para">
For more information on installing packages with Yum, see <a class="xref" href="#sec-Installing">Section 5.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">12.1.1. Introduction to Samba</h3></div></div></div><a id="idm225474043440" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="samba-rgs-overview"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.1.1. Introduction to Samba</h3></div></div></div><a id="idm261752868112" class="indexterm"></a><div class="para">
Fedora includes Samba version <code class="literal">4.1</code>:
- </div><div class="section" id="s3-samba-abilities"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.1.1. Samba Features</h4></div></div></div><a id="idm225474046736" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-abilities"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.1.1. Samba Features</h4></div></div></div><a id="idm261748485616" class="indexterm"></a><div class="para">
Samba is a powerful and versatile server application.
</div><div class="para">
What Samba can do:
@@ -5172,25 +5290,25 @@ $DEFAULT_BASE = "dc=example,dc=com";</pre><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">12.1.2. Samba Daemons and Related Services</h3></div></div></div><a id="idm225469091600" class="indexterm"></a><div class="para">
+ </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">12.1.2. Samba Daemons and Related Services</h3></div></div></div><a id="idm261738115904" 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">12.1.2.1. Samba Daemons</h4></div></div></div><a id="idm225469095248" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.2.1. Samba Daemons</h4></div></div></div><a id="idm261738119552" class="indexterm"></a><div class="para">
Samba is comprised of three daemons (<code class="command">smbd</code>, <code class="command">nmbd</code>, and <code class="command">winbindd</code>). Three services (<code class="command">smb</code>, <code class="command">nmb</code>, and <code class="command">winbind</code>) control how the daemons are started, stopped, and other service-related features. These services act as different init scripts. Each daemon is listed in detail below, as well as which specific service has control over it.
- </div><h5 id="s4-samba-daemon-smbd"> <code class="command">smbd</code> </h5><a id="idm225471305136" class="indexterm"></a><div class="para">
+ </div><h5 id="s4-samba-daemon-smbd"> <code class="command">smbd</code> </h5><a id="idm261745658448" 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 id="s4-samba-daemon-nmbd"> <code class="command">nmbd</code> </h5><a id="idm225473938608" class="indexterm"></a><div class="para">
+ </div><h5 id="s4-samba-daemon-nmbd"> <code class="command">nmbd</code> </h5><a id="idm261751269024" class="indexterm"></a><div class="para">
The <code class="command">nmbd</code> server daemon understands and replies to NetBIOS name service requests such as those produced by SMB/CIFS in Windows-based systems. These systems include Windows 95/98/ME, Windows NT, Windows 2000, Windows XP, and LanManager clients. It also participates in the browsing protocols that make up the Windows <span class="guilabel"><strong>Network Neighborhood</strong></span> view. The default port that the server listens to for <code class="systemitem">NMB</code> traffic is <code class="systemitem">UDP</code> port <code class="systemitem">137</code>.
</div><div class="para">
The <code class="command">nmbd</code> daemon is controlled by the <code class="command">nmb</code> service.
- </div><h5 id="s4-samba-daemon-winbindd"> <code class="command">winbindd</code> </h5><a id="idm225454354960" class="indexterm"></a><div class="para">
+ </div><h5 id="s4-samba-daemon-winbindd"> <code class="command">winbindd</code> </h5><a id="idm261746565568" class="indexterm"></a><div class="para">
The <code class="command">winbind</code> service resolves user and group information received from a server running Windows NT, 2000, 2003, Windows Server 2008, or Windows Server 2012. This makes Windows user and group information understandable by UNIX platforms. This is achieved by using Microsoft RPC calls, <em class="firstterm">Pluggable Authentication Modules</em> (PAM), and the <em class="firstterm">Name Service Switch</em> (NSS). This allows Windows NT domain users to appear and operate as UNIX users on a UNIX machine. Though bundled with the Samba distribution, the <code class="command">winbind</code> service is controlled separately from the <code class="command">smb</code> service.
</div><div class="para">
The <code class="command">winbindd</code> daemon is controlled by the <code class="command">winbind</code> service and does not require the <code class="command">smb</code> service to be started in order to operate. <code class="command">winbindd</code> is also used when Samba is an Active Directory member, and may also be used on a Samba domain controller (to implement nested groups and interdomain trust). Because <code class="command">winbind</code> is a client-side service used to connect to Windows NT-based servers, further discussion of <code class="command">winbind</code> is beyond the scope of this chapter.
</div><div class="note"><div class="admonition_header"><h2>Obtaining a list of utilities that are shipped with Samba</h2></div><div class="admonition"><div class="para">
See <a class="xref" href="#s2-samba-programs">Section 12.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">12.1.3. Connecting to a Samba Share</h3></div></div></div><a id="idm225454357664" class="indexterm"></a><div class="para">
+ </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">12.1.3. Connecting to a Samba Share</h3></div></div></div><a id="idm261742580960" 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
@@ -5200,9 +5318,9 @@ $DEFAULT_BASE = "dc=example,dc=com";</pre><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">12.1.3.1. Command Line</h4></div></div></div><a id="idm225469168016" class="indexterm"></a><a id="idm225471762304" class="indexterm"></a><a id="idm225462722880" class="indexterm"></a><div class="para">
+ </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">12.1.3.1. Command Line</h4></div></div></div><a id="idm261758075264" class="indexterm"></a><a id="idm261747533040" class="indexterm"></a><a id="idm261757402976" 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="idm225462722336" class="indexterm"></a><a id="idm225462724112" class="indexterm"></a><div class="para">
+ </div><a id="idm261757402432" class="indexterm"></a><a id="idm261756485472" 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.
@@ -5210,7 +5328,7 @@ $DEFAULT_BASE = "dc=example,dc=com";</pre><div class="para">
If you see the <code class="prompt">smb:\></code> prompt, you have successfully logged in. Once you are logged in, type <strong class="userinput"><code>help</code></strong> for a list of commands. If you want to browse the contents of your home directory, replace <em class="replaceable"><code>sharename</code></em> with your username. If the <code class="command">-U</code> switch is not used, the username of the current user is passed to the Samba server.
</div><div class="para">
To exit <code class="command">smbclient</code>, type <strong class="userinput"><code>exit</code></strong> at the <code class="prompt">smb:\></code> prompt.
- </div></div><div class="section" id="s2-samba-mounting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.3.2. Mounting the Share</h4></div></div></div><a id="idm225461272960" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-samba-mounting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.3.2. Mounting the Share</h4></div></div></div><a id="idm261724474944" 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>:
@@ -5229,11 +5347,11 @@ $DEFAULT_BASE = "dc=example,dc=com";</pre><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">12.1.4. Configuring a Samba Server</h3></div></div></div><a id="idm225497224512" class="indexterm"></a><a id="idm225504119056" class="indexterm"></a><div class="para">
+ </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">12.1.4. Configuring a Samba Server</h3></div></div></div><a id="idm261721941264" class="indexterm"></a><a id="idm261721942400" class="indexterm"></a><div class="para">
The default configuration file (<code class="filename">/etc/samba/smb.conf</code>) allows users to view their home directories as a Samba share. It also shares all printers configured for the system as Samba shared printers. You can attach a printer to the system and print to it from the Windows machines on your network.
- </div><div class="section" id="s3-samba-configuring-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.4.1. Graphical Configuration</h4></div></div></div><a id="idm225497226464" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-configuring-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.4.1. Graphical Configuration</h4></div></div></div><a id="idm261707979728" class="indexterm"></a><div class="para">
To configure Samba using a graphical interface, use one of the available Samba graphical user interfaces. A list of available GUIs can be found at <a href="http://www.samba.org/samba/GUI/">http://www.samba.org/samba/GUI/</a>.
- </div></div><div class="section" id="s3-samba-configuring-cmdline"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.4.2. Command Line Configuration</h4></div></div></div><a id="idm225471541952" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-samba-configuring-cmdline"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.4.2. Command Line Configuration</h4></div></div></div><a id="idm261725900880" 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>
@@ -5255,7 +5373,7 @@ 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">12.1.4.3. Encrypted Passwords</h4></div></div></div><div class="para">
Encrypted passwords are enabled by default because it is more secure to use them. To create a user with an encrypted password, use the command <code class="command">smbpasswd -a <em class="replaceable"><code>username</code></em></code>.
- </div><a id="idm225450553616" class="indexterm"></a><a id="idm225450556096" class="indexterm"></a><a id="idm225453361008" class="indexterm"></a><a id="idm225453362880" class="indexterm"></a><a id="idm225444803136" class="indexterm"></a><a id="idm225453365824" class="indexterm"></a><a id="idm225444803616" 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">12.1.5. Starting and Stopping Samba</h3></div></div></div><a id="idm225444807440" class="indexterm"></a><a id="idm225476733312" class="indexterm"></a><a id="idm225460932080" class="indexterm"></a><a id="idm225464199072" class="indexterm"></a><a id="idm225464200176" class="indexterm"></a><div class="para">
+ </div><a id="idm261763809024" class="indexterm"></a><a id="idm261751805392" class="indexterm"></a><a id="idm261751808240" class="indexterm"></a><a id="idm261751809264" class="indexterm"></a><a id="idm261737929440" class="indexterm"></a><a id="idm261737928960" class="indexterm"></a><a id="idm261737930400" 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">12.1.5. Starting and Stopping Samba</h3></div></div></div><a id="idm261648354544" class="indexterm"></a><a id="idm261729829424" class="indexterm"></a><a id="idm261723229232" class="indexterm"></a><a id="idm261723229824" class="indexterm"></a><a id="idm261721609120" 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. Also, it is recommended to run <code class="systemitem">winbind</code> before <code class="systemitem">smbd</code>.
@@ -5277,13 +5395,13 @@ create mask = 0765</pre><div class="para">
By default, the <code class="command">smb</code> service does <span class="emphasis"><em>not</em></span> start automatically at boot time. To configure Samba to start at boot time, type the following at a shell prompt as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">systemctl enable smb.service</code></pre><div class="para">
See <a class="xref" href="#ch-Services_and_Daemons">Chapter 6, <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">12.1.6. Samba Server Types and the <code class="filename">smb.conf</code> File</h3></div></div></div><a id="idm225476849664" class="indexterm"></a><a id="idm225476728912" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-samba-servers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.1.6. Samba Server Types and the <code class="filename">smb.conf</code> File</h3></div></div></div><a id="idm261708033808" class="indexterm"></a><a id="idm261729828736" 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">12.1.6.1. Stand-alone Server</h4></div></div></div><a id="idm225498506528" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-standalone"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.6.1. Stand-alone Server</h4></div></div></div><a id="idm261724871648" 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 12.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">12.1.6.1.1. Anonymous Read-Only</h5></div></div></div><a id="idm225498509376" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s4-samba-standalone-anonreadonly"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.1.6.1.1. Anonymous Read-Only</h5></div></div></div><a id="idm261724875360" 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
@@ -5293,7 +5411,7 @@ security = share
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">12.1.6.1.2. Anonymous Read/Write</h5></div></div></div><a id="idm225463520240" class="indexterm"></a><div class="para">
+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">12.1.6.1.2. Anonymous Read/Write</h5></div></div></div><a id="idm261759605280" 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.
@@ -5307,7 +5425,7 @@ 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">12.1.6.1.3. Anonymous Print Server</h5></div></div></div><a id="idm225446978080" class="indexterm"></a><div class="para">
+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">12.1.6.1.3. Anonymous Print Server</h5></div></div></div><a id="idm261758663824" 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
@@ -5323,7 +5441,7 @@ 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">12.1.6.1.4. Secure Read/Write File and Print Server</h5></div></div></div><a id="idm225438887456" class="indexterm"></a><div class="para">
+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">12.1.6.1.4. Secure Read/Write File and Print Server</h5></div></div></div><a id="idm261652935328" 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
@@ -5352,9 +5470,9 @@ 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">12.1.6.2. Domain Member Server</h4></div></div></div><a id="idm225468283456" class="indexterm"></a><div class="para">
+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">12.1.6.2. Domain Member Server</h4></div></div></div><a id="idm261712796240" 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">12.1.6.2.1. Active Directory Domain Member Server</h5></div></div></div><a id="idm225439492608" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s4-samba-domain-member-ads"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.1.6.2.1. Active Directory Domain Member Server</h5></div></div></div><a id="idm261712800048" 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
@@ -5381,7 +5499,7 @@ password server = kerberos.example.com</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">12.1.6.2.2. Windows NT4-based Domain Member Server</h5></div></div></div><a id="idm225449415648" class="indexterm"></a><div class="para">
+ </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">12.1.6.2.2. Windows NT4-based Domain Member Server</h5></div></div></div><a id="idm261705628784" 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
@@ -5403,13 +5521,13 @@ guest ok = Yes</pre><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">12.1.6.3. Domain Controller</h4></div></div></div><a id="idm225470072240" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s3-samba-domain-controller"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.6.3. Domain Controller</h4></div></div></div><a id="idm261713879104" 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">12.1.6.3.1. Primary Domain Controller (PDC) using <code class="command">tdbsam</code> </h5></div></div></div><a id="idm225458122608" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s4-samba-pdc-tdbsam"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.1.6.3.1. Primary Domain Controller (PDC) using <code class="command">tdbsam</code> </h5></div></div></div><a id="idm261717842416" 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 12.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.
@@ -5483,11 +5601,11 @@ domain master = Yes
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">12.1.6.3.2. Primary Domain Controller (PDC) with Active Directory</h5></div></div></div><a id="idm225460424544" class="indexterm"></a><div class="para">
+ </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">12.1.6.3.2. Primary Domain Controller (PDC) with Active Directory</h5></div></div></div><a id="idm261740453952" 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">12.1.7. Samba Security Modes</h3></div></div></div><a id="idm225427075984" class="indexterm"></a><div class="para">
+ </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">12.1.7. Samba Security Modes</h3></div></div></div><a id="idm261782586624" 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">12.1.7.1. User-Level Security</h4></div></div></div><a id="idm225434858608" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-user-level"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.7.1. User-Level Security</h4></div></div></div><a id="idm261690758576" 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:
@@ -5496,13 +5614,13 @@ domain master = Yes
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">12.1.7.1.1. Domain Security Mode (User-Level Security)</h5></div></div></div><a id="idm225464598944" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-domain-security-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.1.7.1.1. Domain Security Mode (User-Level Security)</h5></div></div></div><a id="idm261761397840" 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">12.1.7.1.2. Active Directory Security Mode (User-Level Security)</h5></div></div></div><a id="idm225437787792" class="indexterm"></a><div class="para">
+...</pre></div><div class="section" id="s3-samba-ads-security-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.1.7.1.2. Active Directory Security Mode (User-Level Security)</h5></div></div></div><a id="idm261746563408" 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:
@@ -5511,7 +5629,7 @@ workgroup = MARKETING
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">12.1.7.1.3. Server Security Mode (User-Level Security)</h5></div></div></div><a id="idm225466227072" class="indexterm"></a><div class="para">
+...</pre></div><div class="section" id="s3-samba-server-security-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.1.7.1.3. Server Security Mode (User-Level Security)</h5></div></div></div><a id="idm261685601888" 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.
@@ -5522,18 +5640,18 @@ password server = kerberos.example.com
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">12.1.7.2. Share-Level Security</h4></div></div></div><a id="idm225505733264" class="indexterm"></a><div class="para">
+...</pre></div></div><div class="section" id="s3-samba-share-level"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.7.2. Share-Level Security</h4></div></div></div><a id="idm261713957952" 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">12.1.8. Samba Account Information Databases</h3></div></div></div><a id="idm225433969440" class="indexterm"></a><div class="para">
+...</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">12.1.8. Samba Account Information Databases</h3></div></div></div><a id="idm261755235968" 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="idm225502099136" class="indexterm"></a><a id="idm225461196560" class="indexterm"></a><a id="idm225456235856" class="indexterm"></a><a id="idm225461112512" class="indexterm"></a><a id="idm225442482176" class="indexterm"></a><a id="idm225468897424" class="indexterm"></a><a id="idm225468485472" class="indexterm"></a><a id="idm225480321856" class="indexterm"></a><a id="idm225460979104" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Plain Text</span></dt><dd><div class="para">
+ </div><a id="idm261756752560" class="indexterm"></a><a id="idm261742875312" class="indexterm"></a><a id="idm261723477904" class="indexterm"></a><a id="idm261741538720" class="indexterm"></a><a id="idm261749324880" class="indexterm"></a><a id="idm261726137312" class="indexterm"></a><a id="idm261744401280" class="indexterm"></a><a id="idm261755466704" class="indexterm"></a><a id="idm261779433472" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Plain Text</span></dt><dd><div class="para">
Plain text back ends are nothing more than the <code class="command">/etc/passwd</code> type back ends. With a plain text back end, all usernames and passwords are sent unencrypted between the client and the Samba server. This method is very unsecure and is not recommended for use by any means. It is possible that different Windows clients connecting to the Samba server with plain text passwords cannot support such an authentication method.
</div></dd><dt class="varlistentry"><span class="term"> <code class="command">smbpasswd</code> </span></dt><dd><div class="para">
A popular back end used in previous Samba packages, the <code class="command">smbpasswd</code> back end utilizes a plain ASCII text layout that includes the MS Windows LanMan and NT account, and encrypted password information. The <code class="command">smbpasswd</code> back end lacks the storage of the Windows NT/2000/2003 SAM extended controls. The <code class="command">smbpasswd</code> back end is not recommended because it does not scale well or hold any Windows information, such as RIDs for NT-based groups. The <code class="command">tdbsam</code> back end solves these issues for use in a smaller database (250 users), but is still not an enterprise-class solution.
@@ -5551,17 +5669,17 @@ security = share
As such, if you are using the <code class="command">ldapsam</code> back end for your Samba server, you will need to configure <code class="command">slapd</code> to include one of these schema file. See <a class="xref" href="#s3-ldap-configuration-schema">Section 11.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">12.1.9. Samba Network Browsing</h3></div></div></div><a id="idm225477853168" class="indexterm"></a><a id="idm225469058128" class="indexterm"></a><div class="para">
+ </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">12.1.9. Samba Network Browsing</h3></div></div></div><a id="idm261746559152" class="indexterm"></a><a id="idm261690577648" 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">12.1.9.1. Domain Browsing</h4></div></div></div><a id="idm225464078272" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-domain-browsing"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.9.1. Domain Browsing</h4></div></div></div><a id="idm261726483120" class="indexterm"></a><div class="para">
By default, a Windows server PDC for a domain is also the domain master browser for that domain. A Samba server must <span class="emphasis"><em>not</em></span> be set up as a domain master server in this type of situation.
</div><div class="para">
For subnets that do not include the Windows server PDC, a Samba server can be implemented as a local master browser. Configuring the <code class="filename">/etc/samba/smb.conf</code> file for a local master browser (or no browsing at all) in a domain controller environment is the same as workgroup configuration (see <a class="xref" href="#s2-samba-configuring">Section 12.1.4, “Configuring a Samba Server”</a>).
- </div></div><div class="section" id="s3-samba-wins"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.9.2. WINS (Windows Internet Name Server)</h4></div></div></div><a id="idm225445856160" class="indexterm"></a><a id="idm225463419120" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-samba-wins"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.9.2. WINS (Windows Internet Name Server)</h4></div></div></div><a id="idm261744831648" class="indexterm"></a><a id="idm261706908256" 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.
@@ -5570,9 +5688,9 @@ security = share
</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">12.1.10. Samba with CUPS Printing Support</h3></div></div></div><a id="idm225463651600" class="indexterm"></a><div class="para">
+ </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">12.1.10. Samba with CUPS Printing Support</h3></div></div></div><a id="idm261759147200" 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">12.1.10.1. Simple <code class="filename">smb.conf</code> Settings</h4></div></div></div><a id="idm225464928560" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-cups-smb.conf"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.10.1. Simple <code class="filename">smb.conf</code> Settings</h4></div></div></div><a id="idm261741256704" 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
@@ -5597,7 +5715,7 @@ printer admin = ed, john</pre><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">12.1.11. Samba Distribution Programs</h3></div></div></div><a id="idm225444693504" class="indexterm"></a><h4 id="s3-samba-programs-findsmb"> <code class="filename">findsmb</code> </h4><a id="idm225471070928" class="indexterm"></a><a id="idm225478777472" class="indexterm"></a><pre class="screen"><code class="command">findsmb <em class="replaceable"><code>subnet_broadcast_address</code></em></code></pre><div class="para">
+ </div></div></div><div class="section" id="s2-samba-programs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.1.11. Samba Distribution Programs</h3></div></div></div><a id="idm261713064304" class="indexterm"></a><h4 id="s3-samba-programs-findsmb"> <code class="filename">findsmb</code> </h4><a id="idm261714344144" class="indexterm"></a><a id="idm261760560096" 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:
@@ -5612,7 +5730,7 @@ IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
10.1.57.141 JAWS +[KWIKIMART] [Unix] [Samba 2.2.7a-security-rollup-fix]
10.1.56.159 FRED +[MYGROUP] [Unix] [Samba 3.0.0-14.3E]
10.1.59.192 LEGION *[MYGROUP] [Unix] [Samba 2.2.7-security-rollup-fix]
-10.1.56.205 NANCYN +[MYGROUP] [Unix] [Samba 2.2.7a-security-rollup-fix]</pre><h4 id="s3-samba-programs-net"> <code class="filename">net</code> </h4><a id="idm225427117840" class="indexterm"></a><a id="idm225437012240" 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">
+10.1.56.205 NANCYN +[MYGROUP] [Unix] [Samba 2.2.7a-security-rollup-fix]</pre><h4 id="s3-samba-programs-net"> <code class="filename">net</code> </h4><a id="idm261756705744" class="indexterm"></a><a id="idm261741462576" class="indexterm"></a><pre class="screen"><code class="command">net <em class="replaceable"><code>protocol function misc_options target_options</code></em></code></pre><div class="para">
The <code class="command">net</code> utility is similar to the <code class="command">net</code> utility used for Windows and MS-DOS. The first argument is used to specify the protocol to use when executing a command. The <code class="command"><em class="replaceable"><code>protocol</code></em> </code> option can be <code class="command">ads</code>, <code class="command">rap</code>, or <code class="command">rpc</code> for specifying the type of server connection. Active Directory uses <code class="command">ads</code>, Win9x/NT3 uses <code class="command">rap</code>, and Windows NT4/2000/2003/2008 uses <code class="command">rpc</code>. If the protocol is omitted, <code class="command">net</code> automatically tries to determine it.
</div><div class="para">
The following example displays a list of the available shares for a host named <code class="command">wakko</code>:
@@ -5632,14 +5750,14 @@ User name Comment
-----------------------------
andriusb Documentation
joe Marketing
-lisa Sales</pre><h4 id="s3-samba-programs-nmblookup"> <code class="filename">nmblookup</code> </h4><a id="idm225444052464" class="indexterm"></a><a id="idm225438592992" class="indexterm"></a><pre class="screen"><code class="command">nmblookup <em class="replaceable"><code>options netbios_name</code></em></code></pre><div class="para">
+lisa Sales</pre><h4 id="s3-samba-programs-nmblookup"> <code class="filename">nmblookup</code> </h4><a id="idm261741697904" class="indexterm"></a><a id="idm261777348208" class="indexterm"></a><pre class="screen"><code class="command">nmblookup <em class="replaceable"><code>options netbios_name</code></em></code></pre><div class="para">
The <code class="command">nmblookup</code> program resolves NetBIOS names into <code class="systemitem">IP</code> addresses. The program broadcasts its query on the local subnet until the target machine replies.
</div><div class="para">
The following example displays the <code class="systemitem">IP</code> address of the NetBIOS name <code class="literal">trek</code>:
</div><pre class="screen">
<strong class="userinput"><code>~]$ nmblookup trek</code></strong>
querying trek on 10.1.59.255
-10.1.56.45 trek<00></pre><h4 id="s3-samba-programs-pdbedit"> <code class="filename">pdbedit</code> </h4><a id="idm225459461728" class="indexterm"></a><a id="idm225438737152" class="indexterm"></a><pre class="screen"><code class="command">pdbedit <em class="replaceable"><code>options</code></em></code></pre><div class="para">
+10.1.56.45 trek<00></pre><h4 id="s3-samba-programs-pdbedit"> <code class="filename">pdbedit</code> </h4><a id="idm261727630928" class="indexterm"></a><a id="idm261756022704" 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:
@@ -5693,23 +5811,23 @@ lisa:504:
kristin:506:
<strong class="userinput"><code>~]$ pdbedit -x joe</code></strong>
<strong class="userinput"><code>~]$ pdbedit -L</code></strong>
-andriusb:505: lisa:504: kristin:506:</pre><h4 id="s3-samba-programs-rpcclient"> <code class="filename">rpcclient</code> </h4><a id="idm225470356848" class="indexterm"></a><a id="idm225480059888" class="indexterm"></a><pre class="screen"><code class="command">rpcclient <em class="replaceable"><code>server options</code></em></code></pre><div class="para">
+andriusb:505: lisa:504: kristin:506:</pre><h4 id="s3-samba-programs-rpcclient"> <code class="filename">rpcclient</code> </h4><a id="idm261745212592" class="indexterm"></a><a id="idm261748567008" class="indexterm"></a><pre class="screen"><code class="command">rpcclient <em class="replaceable"><code>server options</code></em></code></pre><div class="para">
The <code class="command">rpcclient</code> program issues administrative commands using Microsoft RPCs, which provide access to the Windows administration graphical user interfaces (GUIs) for systems management. This is most often used by advanced users that understand the full complexity of Microsoft RPCs.
- </div><h4 id="s3-samba-programs-smbcacls"> <code class="filename">smbcacls</code> </h4><a id="idm225476482528" class="indexterm"></a><a id="idm225464397088" 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">
+ </div><h4 id="s3-samba-programs-smbcacls"> <code class="filename">smbcacls</code> </h4><a id="idm261781355696" class="indexterm"></a><a id="idm261726723472" class="indexterm"></a><pre class="screen"><code class="command">smbcacls <em class="replaceable"><code>//server/share filename options</code></em></code></pre><div class="para">
The <code class="command">smbcacls</code> program modifies Windows ACLs on files and directories shared by a Samba server or a Windows server.
- </div><h4 id="s3-samba-programs-smbclient"> <code class="filename">smbclient</code> </h4><a id="idm225469086480" class="indexterm"></a><a id="idm225462550416" 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">
+ </div><h4 id="s3-samba-programs-smbclient"> <code class="filename">smbclient</code> </h4><a id="idm261785088208" class="indexterm"></a><a id="idm261724491616" class="indexterm"></a><pre class="screen"><code class="command">smbclient <em class="replaceable"><code>//server/share password options</code></em></code></pre><div class="para">
The <code class="command">smbclient</code> program is a versatile UNIX client which provides functionality similar to <code class="command">ftp</code>.
- </div><h4 id="s3-samba-programs-smbcontrol"> <code class="filename">smbcontrol</code> </h4><a id="idm225416334496" class="indexterm"></a><a id="idm225437823776" 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">
+ </div><h4 id="s3-samba-programs-smbcontrol"> <code class="filename">smbcontrol</code> </h4><a id="idm261723262976" class="indexterm"></a><a id="idm261752019184" class="indexterm"></a><pre class="screen"><code class="command">smbcontrol -i <em class="replaceable"><code>options</code></em></code></pre><pre class="screen"><code class="command">smbcontrol <em class="replaceable"><code>options destination messagetype parameters</code></em></code></pre><div class="para">
The <code class="command">smbcontrol</code> program sends control messages to running <code class="command">smbd</code>, <code class="command">nmbd</code>, or <code class="command">winbindd</code> daemons. Executing <code class="command">smbcontrol -i</code> runs commands interactively until a blank line or a <em class="parameter"><code>'q'</code></em> is entered.
- </div><h4 id="s3-samba-programs-smbpasswd"> <code class="filename">smbpasswd</code> </h4><a id="idm225465093888" class="indexterm"></a><a id="idm225469298400" class="indexterm"></a><pre class="screen"><code class="command">smbpasswd <em class="replaceable"><code>options username password</code></em></code></pre><div class="para">
+ </div><h4 id="s3-samba-programs-smbpasswd"> <code class="filename">smbpasswd</code> </h4><a id="idm261706562800" class="indexterm"></a><a id="idm261721707648" class="indexterm"></a><pre class="screen"><code class="command">smbpasswd <em class="replaceable"><code>options username password</code></em></code></pre><div class="para">
The <code class="command">smbpasswd</code> program manages encrypted passwords. This program can be run by a superuser to change any user's password and also by an ordinary user to change their own Samba password.
- </div><h4 id="s3-samba-programs-smbspool"> <code class="filename">smbspool</code> </h4><a id="idm225437791024" class="indexterm"></a><a id="idm225454507184" 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">
+ </div><h4 id="s3-samba-programs-smbspool"> <code class="filename">smbspool</code> </h4><a id="idm261778477296" class="indexterm"></a><a id="idm261746301952" class="indexterm"></a><pre class="screen"><code class="command">smbspool <em class="replaceable"><code>job user title copies options filename</code></em></code></pre><div class="para">
The <code class="command">smbspool</code> program is a CUPS-compatible printing interface to Samba. Although designed for use with CUPS printers, <code class="command">smbspool</code> can work with non-CUPS printers as well.
- </div><h4 id="s3-samba-programs-smbstatus"> <code class="filename">smbstatus</code> </h4><a id="idm225462830304" class="indexterm"></a><a id="idm225468939184" class="indexterm"></a><pre class="screen"><code class="command">smbstatus <em class="replaceable"><code>options</code></em></code></pre><div class="para">
+ </div><h4 id="s3-samba-programs-smbstatus"> <code class="filename">smbstatus</code> </h4><a id="idm261744687280" class="indexterm"></a><a id="idm261744385664" class="indexterm"></a><pre class="screen"><code class="command">smbstatus <em class="replaceable"><code>options</code></em></code></pre><div class="para">
The <code class="command">smbstatus</code> program displays the status of current connections to a Samba server.
- </div><h4 id="s3-samba-programs-smbtar"> <code class="filename">smbtar</code> </h4><a id="idm225447843168" class="indexterm"></a><a id="idm225469303936" class="indexterm"></a><pre class="screen"><code class="command">smbtar <em class="replaceable"><code>options</code></em></code></pre><div class="para">
+ </div><h4 id="s3-samba-programs-smbtar"> <code class="filename">smbtar</code> </h4><a id="idm261715443632" class="indexterm"></a><a id="idm261717238544" class="indexterm"></a><pre class="screen"><code class="command">smbtar <em class="replaceable"><code>options</code></em></code></pre><div class="para">
The <code class="command">smbtar</code> program performs backup and restores of Windows-based share files and directories to a local tape archive. Though similar to the <code class="command">tar</code> command, the two are not compatible.
- </div><h4 id="s3-samba-programs-testparm"> <code class="filename">testparm</code> </h4><a id="idm225475123904" class="indexterm"></a><a id="idm225458996832" 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">
+ </div><h4 id="s3-samba-programs-testparm"> <code class="filename">testparm</code> </h4><a id="idm261714602400" class="indexterm"></a><a id="idm261739477536" class="indexterm"></a><pre class="screen"><code class="command">testparm <em class="replaceable"><code>options filename hostname IP_address</code></em></code></pre><div class="para">
The <code class="command">testparm</code> program checks the syntax of the <code class="filename">/etc/samba/smb.conf</code> file. If your <code class="filename">smb.conf</code> file is in the default location (<code class="filename">/etc/samba/smb.conf</code>) you do not need to specify the location. Specifying the host name and <code class="systemitem">IP</code> address to the <code class="command">testparm</code> program verifies that the <code class="filename">hosts.allow</code> and <code class="filename">host.deny</code> files are configured correctly. The <code class="command">testparm</code> program also displays a summary of your <code class="filename">smb.conf</code> file and the server's role (stand-alone, domain, etc.) after testing. This is convenient when debugging as it excludes comments and concisely presents information for experienced administrators to read.
</div><div class="para">
For example:
@@ -5751,11 +5869,11 @@ Press enter to see a dump of your service definitions
force user = andriusb
force group = users
read only = No
- guest only = Yes</pre><h4 id="s3-samba-programs-wbinfo"> <code class="filename">wbinfo</code> </h4><a id="idm225480989808" class="indexterm"></a><a id="idm225474399712" class="indexterm"></a><pre class="screen"><code class="command">wbinfo <em class="replaceable"><code>options</code></em></code></pre><div class="para">
+ guest only = Yes</pre><h4 id="s3-samba-programs-wbinfo"> <code class="filename">wbinfo</code> </h4><a id="idm261632833792" class="indexterm"></a><a id="idm261717844416" 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">12.1.12. Additional Resources</h3></div></div></div><a id="idm225458527664" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-samba-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.1.12. Additional Resources</h3></div></div></div><a id="idm261724488432" 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">12.1.12.1. Installed Documentation</h4></div></div></div><a id="idm225463779712" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><div class="section" id="s3-samba-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.12.1. Installed Documentation</h4></div></div></div><a id="idm261754583120" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="filename">/usr/share/doc/samba/</code> — All additional files included with the Samba distribution. This includes all helper scripts, sample configuration files, and documentation.
</div></li></ul></div><div class="para">
See the following manual pages for detailed information about <span class="application"><strong>Samba</strong></span>:
@@ -5769,25 +5887,25 @@ Press enter to see a dump of your service definitions
<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">12.1.12.2. Related Books</h4></div></div></div><a id="idm225480306288" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </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">12.1.12.2. Related Books</h4></div></div></div><a id="idm261785492096" 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">12.1.12.3. Useful Websites</h4></div></div></div><a id="idm225471632560" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </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">12.1.12.3. Useful Websites</h4></div></div></div><a id="idm261788142096" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://www.samba.org/">http://www.samba.org/</a> — Homepage for the Samba distribution and all official documentation created by the Samba development team. Many resources are available in HTML and PDF formats, while others are only available for purchase. Although many of these links are not Fedora specific, some concepts may apply.
</div></li><li class="listitem"><div class="para">
<a href="http://us1.samba.org/samba/archives.html">http://samba.org/samba/archives.html </a> — Active email lists for the Samba community. Enabling digest mode is recommended due to high levels of list activity.
</div></li><li class="listitem"><div class="para">
Samba newsgroups — Samba threaded newsgroups, such as <a href="http://www.gmane.org/">www.gmane.org</a>, that use the <code class="systemitem">NNTP</code> protocol are also available. This an alternative to receiving mailing list emails.
- </div></li></ul></div></div></div></div><div xml:lang="en-US" class="section" id="s1-FTP" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.2. FTP</h2></div></div></div><a id="idm225463402464" class="indexterm"></a><a id="idm225470181872" class="indexterm"></a><div class="para">
+ </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">12.2. FTP</h2></div></div></div><a id="idm261739389744" class="indexterm"></a><a id="idm261709490304" 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">12.2.1. The File Transfer Protocol</h3></div></div></div><a id="idm225458559056" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-ftp-protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.1. The File Transfer Protocol</h3></div></div></div><a id="idm261746306544" 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">12.2.1.1. Multiple Ports, Multiple Modes</h4></div></div></div><a id="idm225447194544" class="indexterm"></a><a id="idm225454554736" class="indexterm"></a><a id="idm225449186256" class="indexterm"></a><a id="idm225496605072" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-ftp-protocol-multiport"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.1.1. Multiple Ports, Multiple Modes</h4></div></div></div><a id="idm261693941152" class="indexterm"></a><a id="idm261731914416" class="indexterm"></a><a id="idm261782946800" class="indexterm"></a><a id="idm261747608992" 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:
@@ -5797,7 +5915,7 @@ Press enter to see a dump of your service definitions
Passive mode, like active mode, is initiated by the <code class="systemitem">FTP</code> client application. When requesting data from the server, the <code class="systemitem">FTP</code> client indicates it wants to access the data in passive mode and the server provides the <code class="systemitem">IP</code> address and a random, unprivileged port (greater than <code class="constant">1024</code>) on the server. The client then connects to that port on the server to download the requested information.
</div><div class="para">
While passive mode resolves issues for client-side firewall interference with data connections, it can complicate administration of the server-side firewall. You can reduce the number of open ports on a server by limiting the range of unprivileged ports on the <code class="systemitem">FTP</code> server. This also simplifies the process of configuring firewall rules for the server. See <a class="xref" href="#s3-ftp-vsftpd-conf-opt-net">Section 12.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">12.2.2. FTP Servers</h3></div></div></div><a id="idm225455357248" class="indexterm"></a><a id="idm225499207152" class="indexterm"></a><a id="idm225437962096" class="indexterm"></a><a id="idm225462829504" class="indexterm"></a><div class="para">
+ </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">12.2.2. FTP Servers</h3></div></div></div><a id="idm261747277552" class="indexterm"></a><a id="idm261724304736" class="indexterm"></a><a id="idm261760660592" class="indexterm"></a><a id="idm261751410848" class="indexterm"></a><div class="para">
Fedora ships with two different <code class="systemitem">FTP</code> servers:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">proftpd</code> - A fast, stable, and highly configurable FTP server.
@@ -5823,7 +5941,7 @@ Press enter to see a dump of your service definitions
<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">12.2.3. Files Installed with <code class="command">vsftpd</code> </h3></div></div></div><a id="idm225474739472" class="indexterm"></a><div class="para">
+ </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">12.2.3. Files Installed with <code class="command">vsftpd</code> </h3></div></div></div><a id="idm261759020032" class="indexterm"></a><div class="para">
The <code class="filename">vsftpd</code> RPM installs the daemon (<code class="filename">/usr/sbin/vsftpd</code>), its configuration and related files, as well as <code class="systemitem">FTP</code> directories onto the system. The following lists the files and directories related to <code class="command">vsftpd</code> configuration:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="filename">/etc/rc.d/init.d/vsftpd</code> — The <span class="emphasis"><em>initialization script</em></span> (<em class="firstterm">initscript</em>) used by the <code class="command">systemctl</code> command to start, stop, or reload <code class="command">vsftpd</code>. See <a class="xref" href="#s2-ftp-vsftpd-start">Section 12.2.4, “Starting and Stopping <code class="command">vsftpd</code> ”</a> for more information about using this script.
@@ -5837,7 +5955,7 @@ Press enter to see a dump of your service definitions
<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">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </h3></div></div></div><a id="idm225475539808" class="indexterm"></a><a id="idm225477855120" class="indexterm"></a><a id="idm225454595376" class="indexterm"></a><a id="idm225467864624" class="indexterm"></a><a id="idm225464161168" class="indexterm"></a><div class="para">
+ </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">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </h3></div></div></div><a id="idm261747000752" class="indexterm"></a><a id="idm261777349152" class="indexterm"></a><a id="idm261714334784" class="indexterm"></a><a id="idm261757665248" class="indexterm"></a><a id="idm261717078944" 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:
@@ -5853,15 +5971,15 @@ Press enter to see a dump of your service definitions
To conditionally restart the server, as <code class="systemitem">root</code> type:
</div><pre class="screen"><code class="command">systemctl condrestart vsftpd.service</code></pre><div class="para">
By default, the <code class="command">vsftpd</code> service does <span class="emphasis"><em>not</em></span> start automatically at boot time. To configure the <code class="command">vsftpd</code> service to start at boot time, use a service manager such as <code class="command">systemctl</code>. See <a class="xref" href="#ch-Services_and_Daemons">Chapter 6, <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">12.2.4.1. Starting Multiple Copies of <code class="command">vsftpd</code> </h4></div></div></div><a id="idm225501486128" class="indexterm"></a><a id="idm225470731440" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-ftp-vsftpd-start-multi"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.4.1. Starting Multiple Copies of <code class="command">vsftpd</code> </h4></div></div></div><a id="idm261752534352" class="indexterm"></a><a id="idm261749847104" class="indexterm"></a><div class="para">
Sometimes one computer is used to serve multiple <code class="systemitem">FTP</code> domains. This is a technique called <em class="firstterm">multihoming</em>. One way to multihome using <code class="command">vsftpd</code> is by running multiple copies of the daemon, each with its own configuration file.
</div><div class="para">
- To do this, first assign all relevant <code class="systemitem">IP</code> addresses to network devices or alias network devices on the system. For more information about configuring network devices, device aliases, and additional information about network configuration scripts, refer to the <em class="citetitle">Red Hat Enterprise Linux 7 Networking Guide</em>.
+ To do this, first assign all relevant <code class="systemitem">IP</code> addresses to network devices or alias network devices on the system. For more information about configuring network devices, device aliases, and additional information about network configuration scripts, refer to the <a href="http://docs.fedoraproject.org/en-US/Fedora/21/html/Networking_Guide/index.html"><em class="citetitle">Fedora Networking Guide</em></a>.
</div><div class="para">
- Next, the DNS server for the <code class="systemitem">FTP</code> domains must be configured to reference the correct machine. For information about BIND and its configuration files, refer to the <em class="citetitle">Red Hat Enterprise Linux 7 Networking Guide</em>.
+ Next, the DNS server for the <code class="systemitem">FTP</code> domains must be configured to reference the correct machine. For information about BIND and its configuration files, refer to the <a href="http://docs.fedoraproject.org/en-US/Fedora/21/html/Networking_Guide/index.html"><em class="citetitle">Fedora Networking Guide</em></a>.
</div><div class="para">
If there is more configuration files present in the <code class="filename">/etc/vsftpd</code> directory, calling <code class="command">systemctl start vsftpd.service</code> results in the <code class="filename">/etc/rc.d/init.d/vsftpd</code> initscript starting the same number of processes as the number of configuration files. Each configuration file must have a unique name in the <code class="filename">/etc/vsftpd/</code> directory and must be readable and writable only by <code class="systemitem">root</code>.
- </div></div></div><div class="section" id="s2-ftp-vsftpd-conf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.5. <code class="command">vsftpd</code> Configuration Options</h3></div></div></div><a id="idm225471205456" class="indexterm"></a><a id="idm225424052944" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s2-ftp-vsftpd-conf"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.5. <code class="command">vsftpd</code> Configuration Options</h3></div></div></div><a id="idm261693427840" class="indexterm"></a><a id="idm261693943360" 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:
@@ -5877,7 +5995,7 @@ Press enter to see a dump of your service definitions
For an overview of ways to secure <code class="command">vsftpd</code>, refer to the Fedora 21 <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">12.2.5.1. Daemon Options</h4></div></div></div><a id="idm225474088800" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-ftp-vsftpd-conf-opt-daemon"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.5.1. Daemon Options</h4></div></div></div><a id="idm261788252432" 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.
@@ -5891,7 +6009,7 @@ Press enter to see a dump of your service definitions
<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">12.2.5.2. Log In Options and Access Controls</h4></div></div></div><a id="idm225480633472" class="indexterm"></a><a id="idm225479454816" class="indexterm"></a><div class="para">
+ </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">12.2.5.2. Log In Options and Access Controls</h4></div></div></div><a id="idm261738567264" class="indexterm"></a><a id="idm261749292864" 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.
@@ -5943,7 +6061,7 @@ Press enter to see a dump of your service definitions
<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">12.2.5.3. Anonymous User Options</h4></div></div></div><a id="idm225453046272" class="indexterm"></a><div class="para">
+ </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">12.2.5.3. Anonymous User Options</h4></div></div></div><a id="idm261783700064" 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.
@@ -5975,7 +6093,7 @@ Press enter to see a dump of your service definitions
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">12.2.5.4. Local User Options</h4></div></div></div><a id="idm225444698496" class="indexterm"></a><div class="para">
+ </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">12.2.5.4. Local User Options</h4></div></div></div><a id="idm261650319632" 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.
@@ -6021,7 +6139,7 @@ Press enter to see a dump of your service definitions
<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">12.2.5.5. Directory Options</h4></div></div></div><a id="idm225460234208" class="indexterm"></a><div class="para">
+ </div></li></ul></div></div><div class="section" id="s3-ftp-vsftpd-conf-opt-dir"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.5.5. Directory Options</h4></div></div></div><a id="idm261784115872" 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.
@@ -6051,7 +6169,7 @@ Press enter to see a dump of your service definitions
<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">12.2.5.6. File Transfer Options</h4></div></div></div><a id="idm225435646640" class="indexterm"></a><div class="para">
+ </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">12.2.5.6. File Transfer Options</h4></div></div></div><a id="idm261723255520" 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.
@@ -6069,7 +6187,7 @@ Press enter to see a dump of your service definitions
<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">12.2.5.7. Logging Options</h4></div></div></div><a id="idm225454410496" class="indexterm"></a><div class="para">
+ </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">12.2.5.7. Logging Options</h4></div></div></div><a id="idm261755918992" 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).
@@ -6105,7 +6223,7 @@ Press enter to see a dump of your service definitions
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">12.2.5.8. Network Options</h4></div></div></div><a id="idm225470248992" class="indexterm"></a><div class="para">
+ </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">12.2.5.8. Network Options</h4></div></div></div><a id="idm261759221536" 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.
@@ -6189,9 +6307,9 @@ Press enter to see a dump of your service definitions
<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">12.2.6. Additional Resources</h3></div></div></div><a id="idm225462520656" class="indexterm"></a><div class="para">
+ </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">12.2.6. Additional Resources</h3></div></div></div><a id="idm261745193952" 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">12.2.6.1. Installed Documentation</h4></div></div></div><a id="idm225470011744" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><div class="section" id="s3-ftp-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.6.1. Installed Documentation</h4></div></div></div><a id="idm261749820960" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
The <code class="filename">/usr/share/doc/vsftpd/</code> directory — This directory contains a <code class="filename">README</code> with basic information about the software. The <code class="filename">TUNING</code> file contains basic performance tuning tips and the <code class="filename">SECURITY/</code> directory contains information about the security model employed by <code class="command">vsftpd</code>.
</div></li><li class="listitem"><div class="para">
<code class="command">vsftpd</code> related man pages — There are a number of man pages for the daemon and configuration files. The following lists some of the more important man pages.
@@ -6201,39 +6319,39 @@ Press enter to see a dump of your service definitions
<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">12.2.6.2. Useful Websites</h4></div></div></div><a id="idm225480493584" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </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">12.2.6.2. Useful Websites</h4></div></div></div><a id="idm261716762976" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://vsftpd.beasts.org/">http://vsftpd.beasts.org/</a> — The <code class="command">vsftpd</code> project page is a great place to locate the latest documentation and to contact the author of the software.
</div></li><li class="listitem"><div class="para">
<a href="http://slacksite.com/other/ftp.html">http://slacksite.com/other/ftp.html</a> — This website provides a concise explanation of the differences between active and passive mode <code class="systemitem">FTP</code>.
</div></li><li class="listitem"><div class="para">
<a href="http://www.ietf.org/rfc/rfc0959.txt">http://www.ietf.org/rfc/rfc0959.txt</a> — The original <em class="firstterm">Request for Comments</em> (<em class="firstterm">RFC</em>) of the <code class="systemitem">FTP</code> protocol from the IETF.
- </div></li></ul></div></div></div></div><div xml:lang="en-US" class="section" id="sec-Printer_Configuration" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.3. Printer Configuration</h2></div></div></div><a id="idm225462162496" class="indexterm"></a><a id="idm225435325696" class="indexterm"></a><div class="para">
- The <span class="application"><strong>Printer</strong></span> configuration tool serves for printer configuring, maintenance of printer configuration files, print spool directories and print filters, and printer classes management.
+ </div></li></ul></div></div></div></div><div xml:lang="en-US" class="section" id="sec-Printer_Configuration" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.3. Printer Configuration</h2></div></div></div><a id="idm261740399696" class="indexterm"></a><a id="idm261760691424" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Printers</strong></span> configuration tool serves for printer configuring, maintenance of printer configuration files, print spool directories and print filters, and printer classes management.
</div><div class="para">
The tool is based on the Common Unix Printing System (<acronym class="acronym">CUPS</acronym>). If you upgraded the system from a previous Fedora version that used CUPS, the upgrade process preserved the configured printers.
- </div><div class="note"><div class="admonition_header"><h2>Using the CUPS web application or command line tools</h2></div><div class="admonition"><a id="idm225457616560" class="indexterm"></a><div class="para">
+ </div><div class="note"><div class="admonition_header"><h2>Using the CUPS web application or command-line tools</h2></div><div class="admonition"><a id="idm261746315648" class="indexterm"></a><div class="para">
You can perform the same and additional operations on printers directly from the CUPS web application or command line. To access the application, in a web browser, go to <a href="http://localhost:631/">http://localhost:631/</a>. For CUPS manuals refer to the links on the <span class="guilabel"><strong>Home</strong></span> tab of the web site.
- </div></div></div><div class="section" id="sec-Starting_Printer_Config"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.1. Starting the Printer Configuration Tool</h3></div></div></div><div class="para">
- With the <span class="application"><strong>Printer</strong></span> configuration configuration tool you can perform various operations on existing printers and set up new printers. You can also use CUPS directly (go to <a href="http://localhost:631/">http://localhost:631/</a> to access the CUPS web application).
+ </div></div></div><div class="section" id="sec-Starting_Printer_Config"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.1. Starting the Printers Configuration Tool</h3></div></div></div><div class="para">
+ With the <span class="application"><strong>Printers</strong></span> configuration tool you can perform various operations on existing printers and set up new printers. You can also use CUPS directly (go to <a href="http://localhost:631/">http://localhost:631/</a> to access the CUPS web application).
</div><div class="para">
- To start the <span class="application"><strong>Printer</strong></span> configuration tool if using the GNOME desktop, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">Printer</code>, select the icon, and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Printer</strong></span> configuration tool appears. The <span class="keycap"><strong>Super</strong></span> key appears in a variety of guises, depending on the keyboard and other hardware, but often as either the Windows or Command key, and typically to the left of the <span class="keycap"><strong>Spacebar</strong></span>.
+ To start the <span class="application"><strong>Printers</strong></span> configuration tool if using the GNOME desktop, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">Printers</code>, and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Printers</strong></span> configuration tool appears. The <span class="keycap"><strong>Super</strong></span> key appears in a variety of guises, depending on the keyboard and other hardware, but often as either the Windows or Command key, and typically to the left of the <span class="keycap"><strong>Spacebar</strong></span>.
</div><div class="para">
- The <span class="guilabel"><strong>Printer Configuration</strong></span> window depicted in <a class="xref" href="#fig-printconf-main">Figure 12.2, “Printer Configuration window”</a> appears.
- </div><div class="figure" id="fig-printconf-main"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-main.png" alt="Printer Configuration window" /><div class="longdesc"><div class="para">
- Printer Configuration window
- </div></div></div></div><h6>Figure 12.2. Printer Configuration window</h6></div><br class="figure-break" /></div><div class="section" id="sec-Setting_Printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.2. Starting Printer Setup</h3></div></div></div><a id="idm225456732352" class="indexterm"></a><div class="para">
+ The <span class="guilabel"><strong>Printers</strong></span> window depicted in <a class="xref" href="#fig-printconf-main">Figure 12.2, “Printers Configuration window”</a> appears.
+ </div><div class="figure" id="fig-printconf-main"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-main.png" alt="Printers Configuration window" /><div class="longdesc"><div class="para">
+ Printers Configuration window
+ </div></div></div></div><h6>Figure 12.2. Printers Configuration window</h6></div><br class="figure-break" /></div><div class="section" id="sec-Setting_Printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.2. Starting Printer Setup</h3></div></div></div><a id="idm261715911888" class="indexterm"></a><div class="para">
Printer setup process varies depending on the printer queue type.
</div><div class="para">
- If you are setting up a local printer connected with USB, the printer is discovered and added automatically. You will be prompted to confirm the packages to be installed and provide the <code class="systemitem">root</code> password. Local printers connected with other port types and network printers need to be set up manually.
+ If you are setting up a local printer connected with USB, the printer is discovered and added automatically. You will be prompted to confirm the packages to be installed and provide an administrator or the <code class="systemitem">root</code> user password. Local printers connected with other port types and network printers need to be set up manually.
</div><div class="procedure" id="proc-Setting_up_Printer"><div class="para">
Follow this procedure to start a manual printer setup:
</div><ol class="1"><li class="step"><div class="para">
- Start the Printer configuration tool (refer to <a class="xref" href="#sec-Starting_Printer_Config">Section 12.3.1, “Starting the Printer Configuration Tool”</a>).
+ Start the Printers configuration tool (refer to <a class="xref" href="#sec-Starting_Printer_Config">Section 12.3.1, “Starting the Printers Configuration Tool”</a>).
</div></li><li class="step"><div class="para">
- In the <span class="guilabel"><strong>Authentication Required</strong></span> box, type the root user password and confirm.
+ Select <span class="guimenuitem"><strong>Unlock</strong></span> to enable changes to be made. In the <span class="guilabel"><strong>Authentication Required</strong></span> box, type an administrator or the <code class="systemitem">root</code> user password and confirm.
</div></li><li class="step"><div class="para">
Select the plus sign to open the <span class="guimenuitem"><strong>Add a New Printer</strong></span> dialog. Select the printer from the list or enter its address below.
- </div></li></ol></div></div><div class="section" id="sec-Adding_Other_Printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.3. Adding a Local Printer</h3></div></div></div><a id="idm225402398224" class="indexterm"></a><div class="para">
+ </div></li></ol></div></div><div class="section" id="sec-Adding_Other_Printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.3. Adding a Local Printer</h3></div></div></div><a id="idm261759535120" class="indexterm"></a><div class="para">
Follow this procedure to add a local printer connected with other than a serial port:
</div><div class="procedure" id="proc-Adding_Other_Printer"><ol class="1"><li class="step"><div class="para">
Open the <code class="systemitem">Add a New Printer</code> dialog (refer to <a class="xref" href="#sec-Setting_Printer">Section 12.3.2, “Starting Printer Setup”</a>).
@@ -6260,7 +6378,7 @@ Press enter to see a dump of your service definitions
</div></li></ol></div></div><div class="section" id="s1-printing-jetdirect-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.4. Adding an AppSocket/HP JetDirect printer</h3></div></div></div><div class="para">
Follow this procedure to add an AppSocket/HP JetDirect printer:
</div><div class="procedure" id="proc-Adding_JetDirect_Printer"><ol class="1"><li class="step"><div class="para">
- Open the <code class="systemitem">Add a New Printer</code> dialog (refer to <a class="xref" href="#sec-Starting_Printer_Config">Section 12.3.1, “Starting the Printer Configuration Tool”</a>).
+ Open the <code class="systemitem">Add a New Printer</code> dialog (refer to <a class="xref" href="#sec-Starting_Printer_Config">Section 12.3.1, “Starting the Printers Configuration Tool”</a>).
</div></li><li class="step"><div class="para">
In the list on the left, select <span class="guimenu"><strong>Network Printer</strong></span> → <span class="guimenuitem"><strong>AppSocket/HP JetDirect</strong></span>.
</div></li><li class="step"><div class="para">
@@ -6275,20 +6393,20 @@ Press enter to see a dump of your service definitions
Click <span class="guibutton"><strong>Forward</strong></span>.
</div></li><li class="step"><div class="para">
Select the printer model. See <a class="xref" href="#s1-printing-select-model">Section 12.3.8, “Selecting the Printer Model and Finishing”</a> for details.
- </div></li></ol></div></div><div class="section" id="s1-printing-ipp-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.5. Adding an IPP Printer</h3></div></div></div><a id="idm225442816704" class="indexterm"></a><div class="para">
+ </div></li></ol></div></div><div class="section" id="s1-printing-ipp-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.5. Adding an IPP Printer</h3></div></div></div><a id="idm261745773424" class="indexterm"></a><div class="para">
An <code class="systemitem">IPP</code> printer is a printer attached to a different system on the same TCP/IP network. The system this printer is attached to may either be running CUPS or simply configured to use <code class="systemitem">IPP</code>.
</div><div class="para">
If a firewall is enabled on the printer server, then the firewall must be configured to allow incoming <code class="systemitem">TCP</code> connections on port <code class="literal">631</code>. Note that the CUPS browsing protocol allows client machines to discover shared CUPS queues automatically. To enable this, the firewall on the client machine must be configured to allow incoming <code class="systemitem">UDP</code> packets on port <code class="literal">631</code>.
</div><div class="procedure" id="proc-Adding_IPP_Printer"><div class="para">
Follow this procedure to add an <code class="systemitem">IPP</code> printer:
</div><ol class="1"><li class="step"><div class="para">
- Open the <code class="systemitem">New Printer</code> dialog (refer to <a class="xref" href="#sec-Setting_Printer">Section 12.3.2, “Starting Printer Setup”</a>).
+ Open the <code class="systemitem">Printers</code> dialog (refer to <a class="xref" href="#sec-Setting_Printer">Section 12.3.2, “Starting Printer Setup”</a>).
</div></li><li class="step"><div class="para">
In the list of devices on the left, select <span class="guimenu"><strong>Network Printer</strong></span> and <span class="guimenuitem"><strong>Internet Printing Protocol (ipp)</strong></span> or <span class="guimenuitem"><strong>Internet Printing Protocol (https)</strong></span>.
</div></li><li class="step"><div class="para">
On the right, enter the connection settings:
</div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><span class="guilabel"><strong>Host</strong></span></span></dt><dd><div class="para">
- The hostname of the <code class="systemitem">IPP</code> printer.
+ The host name of the <code class="systemitem">IPP</code> printer.
</div></dd><dt class="varlistentry"><span class="term"><span class="guilabel"><strong>Queue</strong></span></span></dt><dd><div class="para">
The queue name to be given to the new queue (if the box is left empty, a name based on the device node will be used).
</div></dd></dl></div><div class="figure" id="fig-printconf-ipp"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-ipp.png" alt="Adding an IPP printer" /><div class="longdesc"><div class="para">
@@ -6299,7 +6417,7 @@ Press enter to see a dump of your service definitions
Click <span class="guibutton"><strong>Forward</strong></span> to continue.
</div></li><li class="step"><div class="para">
Select the printer model. See <a class="xref" href="#s1-printing-select-model">Section 12.3.8, “Selecting the Printer Model and Finishing”</a> for details.
- </div></li></ol></div></div><div class="section" id="sec-printing-LPDLPR-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.6. Adding an LPD/LPR Host or Printer</h3></div></div></div><a id="idm225448360272" class="indexterm"></a><div class="procedure" id="proc-Adding_HTTPS_Printer"><div class="para">
+ </div></li></ol></div></div><div class="section" id="sec-printing-LPDLPR-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.6. Adding an LPD/LPR Host or Printer</h3></div></div></div><a id="idm261747282848" class="indexterm"></a><div class="procedure" id="proc-Adding_HTTPS_Printer"><div class="para">
Follow this procedure to add an LPD/LPR host or printer:
</div><ol class="1"><li class="step"><div class="para">
Open the <code class="systemitem">New Printer</code> dialog (refer to <a class="xref" href="#sec-Setting_Printer">Section 12.3.2, “Starting Printer Setup”</a>).
@@ -6308,7 +6426,7 @@ Press enter to see a dump of your service definitions
</div></li><li class="step"><div class="para">
On the right, enter the connection settings:
</div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><span class="guilabel"><strong>Host</strong></span></span></dt><dd><div class="para">
- The hostname of the LPD/LPR printer or host.
+ The host name of the LPD/LPR printer or host.
</div><div class="para">
Optionally, click <span class="guibutton"><strong>Probe</strong></span> to find queues on the LPD host.
</div></dd><dt class="varlistentry"><span class="term"><span class="guilabel"><strong>Queue</strong></span></span></dt><dd><div class="para">
@@ -6319,7 +6437,7 @@ Press enter to see a dump of your service definitions
Click <span class="guibutton"><strong>Forward</strong></span> to continue.
</div></li><li class="step"><div class="para">
Select the printer model. See <a class="xref" href="#s1-printing-select-model">Section 12.3.8, “Selecting the Printer Model and Finishing”</a> for details.
- </div></li></ol></div></div><div class="section" id="s1-printing-smb-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.7. Adding a Samba (SMB) printer</h3></div></div></div><a id="idm225474172992" class="indexterm"></a><a id="idm225502089088" class="indexterm"></a><div class="procedure" id="proc-Adding_SMB_Printer"><div class="para">
+ </div></li></ol></div></div><div class="section" id="s1-printing-smb-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.7. Adding a Samba (SMB) printer</h3></div></div></div><a id="idm261740638192" class="indexterm"></a><a id="idm261717966512" class="indexterm"></a><div class="procedure" id="proc-Adding_SMB_Printer"><div class="para">
Follow this procedure to add a Samba printer:
</div><div class="note"><div class="admonition_header"><h2>Installing the samba-client package</h2></div><div class="admonition"><div class="para">
Note that in order to add a Samba printer, you need to have the <span class="package">samba-client</span> package installed. You can do so by running, as <code class="systemitem">root</code>:
@@ -6416,19 +6534,19 @@ Press enter to see a dump of your service definitions
To delete an existing printer, in the <span class="guilabel"><strong>Printer</strong></span> configuration window, select the printer and go to <span class="guimenu"><strong>Printer</strong></span> → <span class="guimenuitem"><strong>Delete</strong></span>. Confirm the printer deletion. Alternatively, press the <span class="keycap"><strong>Delete</strong></span> key.
</div><div class="para">
To set the default printer, right-click the printer in the printer list and click the <span class="guimenuitem"><strong>Set As Default</strong></span> button in the context menu.
- </div><div class="section" id="idm225437009232"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm225437009232">12.3.10.1. The Settings Page</h4></div></div></div><a id="idm225437008432" class="indexterm"></a><div class="para">
+ </div><div class="section" id="idm261758857840"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm261758857840">12.3.10.1. The Settings Page</h4></div></div></div><a id="idm261758857040" class="indexterm"></a><div class="para">
To change printer driver configuration, double-click the corresponding name in the <span class="guilabel"><strong>Printer</strong></span> list and click the <span class="guilabel"><strong>Settings</strong></span> label on the left to display the <span class="guilabel"><strong>Settings</strong></span> page.
</div><div class="para">
You can modify printer settings such as make and model, print a test page, change the device location (URI), and more.
</div><div class="figure" id="fig-printconf-config1"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-config1.png" alt="Settings page" /><div class="longdesc"><div class="para">
Settings Page
- </div></div></div></div><h6>Figure 12.11. Settings page</h6></div><br class="figure-break" /></div><div class="section" id="idm225468344192"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm225468344192">12.3.10.2. The Policies Page</h4></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 12.11. Settings page</h6></div><br class="figure-break" /></div><div class="section" id="idm261782557856"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm261782557856">12.3.10.2. The Policies Page</h4></div></div></div><div class="para">
Click the <span class="guilabel"><strong>Policies</strong></span> button on the left to change settings in printer state and print output.
</div><div class="para">
You can select the printer states, configure the <span class="guilabel"><strong>Error Policy</strong></span> of the printer (you can decide to abort the print job, retry, or stop it if an error occurs).
</div><div class="para">
You can also create a <em class="firstterm">banner page</em> (a page that describes aspects of the print job such as the originating printer, the user name from the which the job originated, and the security status of the document being printed): click the <span class="guilabel"><strong>Starting Banner</strong></span> or <span class="guilabel"><strong>Ending Banner</strong></span> drop-down menu and choose the option that best describes the nature of the print jobs (for example, <span class="guilabel"><strong>confidential</strong></span>).
- </div><div class="section" id="sec-Sharing_Printers"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.3.10.2.1. Sharing Printers</h5></div></div></div><a id="idm225464045040" class="indexterm"></a><div class="para">
+ </div><div class="section" id="sec-Sharing_Printers"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.3.10.2.1. Sharing Printers</h5></div></div></div><a id="idm261753843648" class="indexterm"></a><div class="para">
On the <span class="guilabel"><strong>Policies</strong></span> page, you can mark a printer as shared: if a printer is shared, users published on the network can use it. To allow the sharing function for printers, go to <span class="guimenu"><strong>Server</strong></span> → <span class="guimenuitem"><strong>Settings</strong></span> and select <span class="guilabel"><strong>Publish shared printers connected to this system</strong></span>.
</div><div class="figure" id="fig-printconf-config2"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-config2.png" alt="Policies page" /><div class="longdesc"><div class="para">
Policies Page
@@ -6466,7 +6584,7 @@ Press enter to see a dump of your service definitions
The <span class="guilabel"><strong>Ink/Toner Levels</strong></span> page contains details on toner status if available and printer status messages. Click the <span class="guilabel"><strong>Ink/Toner Levels</strong></span> label on the left to display the page.
</div><div class="figure" id="mediaobj-printconf-config6"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-config6.png" alt="Ink/Toner Levels page" /><div class="longdesc"><div class="para">
Ink/Toner Levels Page
- </div></div></div></div><h6>Figure 12.16. Ink/Toner Levels page</h6></div><br class="figure-break" /></div></div><div class="section" id="s1-printing-managing"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.3.10.3. Managing Print Jobs</h4></div></div></div><a id="idm225471899376" class="indexterm"></a><div class="para">
+ </div></div></div></div><h6>Figure 12.16. Ink/Toner Levels page</h6></div><br class="figure-break" /></div></div><div class="section" id="s1-printing-managing"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.3.10.3. Managing Print Jobs</h4></div></div></div><a id="idm261735177712" class="indexterm"></a><div class="para">
When you send a print job to the printer daemon, such as printing a text file from <span class="application"><strong>Emacs</strong></span> or printing an image from <span class="application"><strong>GIMP</strong></span>, the print job is added to the print spool queue. The print spool queue is a list of print jobs that have been sent to the printer and information about each print request, such as the status of the request, the job number, and more.
</div><div class="para">
During the printing process, messages informing about the process appear in the notification area.
@@ -6488,9 +6606,9 @@ Ben-62 root 1024 Tue 08 Feb 2011 16:45:42 GMT</p
</div><div class="section" id="s2-printing-additional-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.3.11.1. Installed Documentation</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="command">man lp</code></span></dt><dd><div class="para">
The manual page for the <code class="command">lpr</code> command that allows you to print files from the command line.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">man cancel</code></span></dt><dd><div class="para">
- The manual page for the command line utility to remove print jobs from the print queue.
+ The manual page for the command-line utility to remove print jobs from the print queue.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">man mpage</code></span></dt><dd><div class="para">
- The manual page for the command line utility to print multiple pages on one sheet of paper.
+ The manual page for the command-line utility to print multiple pages on one sheet of paper.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">man cupsd</code></span></dt><dd><div class="para">
The manual page for the CUPS printer daemon.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">man cupsd.conf</code></span></dt><dd><div class="para">
@@ -7243,7 +7361,7 @@ manycastclient 239.255.254.254 key 30</pre>
<pre class="screen">~]# <code class="command">hwclock --systohc</code></pre>
</div><div class="para">
- When the system clock is being synchronized by <code class="systemitem">ntpd</code>, the kernel will in turn update the RTC every 11 minutes automatically.
+ When the system clock is being synchronized by <code class="systemitem">ntpd</code> or <code class="systemitem">chronyd</code>, the kernel will in turn update the RTC every 11 minutes automatically.
</div></div><div class="section" id="s1-Configuring_Clock_Sources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">14.19. Configuring Clock Sources</h2></div></div></div><div class="para">
To list the available clock sources on your system, issue the following commands:
<pre class="screen">~]$ <code class="command">cd /sys/devices/system/clocksource/clocksource0/</code>
@@ -7304,7 +7422,7 @@ kvm-clock</pre>
Network Time Synchronization Research Project.
</div></dd><dt class="varlistentry"><span class="term"><a href="http://www.eecis.udel.edu/~mills/ntp/html/manyopt.html">http://www.eecis.udel.edu/~mills/ntp/html/manyopt.html</a></span></dt><dd><div class="para">
Information on Automatic Server Discovery in <code class="systemitem">NTPv4</code>.
- </div></dd></dl></div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-Configuring_PTP_Using_ptp4l" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 15. Configuring PTP Using ptp4l</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sec-Introduction_to_PTP">15.1. Introduction to PTP</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Understanding_PTP">15.1.1. Understanding PTP</a></span></dt><dt><span class="section"><a href="#sec-Advantages_of_PTP">15.1.2. Advantages of PTP</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_PTP">15.2. Using PTP</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_for_Driver_and_Hardware_Support">15.2.1. Checking for Driver and Hardware Support</a></span></dt><dt><span class="section"><a href="#sec-Installing_PTP">15.2.2. Installing PTP</a></span></dt><dt><span class="section"><a href="#sec-Starting_ptp4l">15
.2.3. Starting ptp4l</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Specifying_a_Configuration_File">15.3. Specifying a Configuration File</a></span></dt><dt><span class="section"><a href="#sec-Using_the_PTP_Management_Client">15.4. Using the PTP Management Client</a></span></dt><dt><span class="section"><a href="#sec-Synchronizing_the_Clocks">15.5. Synchronizing the Clocks</a></span></dt><dt><span class="section"><a href="#sec-Verifying_Time_Synchronization">15.6. Verifying Time Synchronization</a></span></dt><dt><span class="section"><a href="#sec-Serving_PTP_Time_with_NTP">15.7. Serving PTP Time with NTP</a></span></dt><dt><span class="section"><a href="#sec-Serving_NTP_Time_with_PTP">15.8. Serving NTP Time with PTP</a></span></dt><dt><span class="section"><a href="#sec-Improving_Accuracy">15.9. Improving Accuracy</a></span></dt><dt><span class="section"><a href="#sec-PTP_additional_resources">15.10. Additional Resources</a></span></dt><dd><dl><dt><span
class="section"><a href="#sec-PTP-docs-inst">15.10.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-PTP_useful-websites">15.10.2. Useful Websites</a></span></dt></dl></dd></dl></div><div class="section" id="sec-Introduction_to_PTP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.1. Introduction to PTP</h2></div></div></div><div class="para">
+ </div></dd></dl></div></div></div></div><div xml:lang="en-US" class="chapter" id="ch-Configuring_PTP_Using_ptp4l" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 15. Configuring PTP Using ptp4l</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sec-Introduction_to_PTP">15.1. Introduction to PTP</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Understanding_PTP">15.1.1. Understanding PTP</a></span></dt><dt><span class="section"><a href="#sec-Advantages_of_PTP">15.1.2. Advantages of PTP</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Using_PTP">15.2. Using PTP</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Checking_for_Driver_and_Hardware_Support">15.2.1. Checking for Driver and Hardware Support</a></span></dt><dt><span class="section"><a href="#sec-Installing_PTP">15.2.2. Installing PTP</a></span></dt><dt><span class="section"><a href="#sec-Starting_ptp4l">15
.2.3. Starting ptp4l</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Specifying_a_Configuration_File">15.3. Specifying a Configuration File</a></span></dt><dt><span class="section"><a href="#sec-Using_the_PTP_Management_Client">15.4. Using the PTP Management Client</a></span></dt><dt><span class="section"><a href="#sec-Synchronizing_the_Clocks">15.5. Synchronizing the Clocks</a></span></dt><dt><span class="section"><a href="#sec-Verifying_Time_Synchronization">15.6. Verifying Time Synchronization</a></span></dt><dt><span class="section"><a href="#sec-Serving_PTP_Time_with_NTP">15.7. Serving PTP Time with NTP</a></span></dt><dt><span class="section"><a href="#sec-Serving_NTP_Time_with_PTP">15.8. Serving NTP Time with PTP</a></span></dt><dt><span class="section"><a href="#sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster">15.9. Synchronize to PTP or NTP Time Using timemaster</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Starting_timemaster_a
s_a_Service">15.9.1. Starting timemaster as a Service</a></span></dt><dt><span class="section"><a href="#sec-Understanding_the_timemaster_Configuration_File">15.9.2. Understanding the timemaster Configuration File</a></span></dt><dt><span class="section"><a href="#sec-Configuring_timemaster_Options">15.9.3. Configuring timemaster Options</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Improving_Accuracy">15.10. Improving Accuracy</a></span></dt><dt><span class="section"><a href="#sec-PTP_additional_resources">15.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-PTP-docs-inst">15.11.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="#sec-PTP_useful-websites">15.11.2. Useful Websites</a></span></dt></dl></dd></dl></div><div class="section" id="sec-Introduction_to_PTP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.1. Introduction to PTP</h2></div></div>
</div><div class="para">
The <em class="firstterm">Precision Time Protocol</em> (<acronym class="acronym">PTP</acronym>) is a protocol used to synchronize clocks in a network. When used in conjunction with hardware support, <code class="systemitem">PTP</code> is capable of sub-microsecond accuracy, which is far better than is normally obtainable with <code class="systemitem">NTP</code>. <code class="systemitem">PTP</code> support is divided between the kernel and user space. The kernel in Fedora includes support for <code class="systemitem">PTP</code> clocks, which are provided by network drivers. The actual implementation of the protocol is known as <span class="application"><strong>linuxptp</strong></span>, a <code class="systemitem">PTPv2</code> implementation according to the IEEE standard 1588 for Linux.
</div><div class="para">
The <span class="package">linuxptp</span> package includes the <span class="application"><strong>ptp4l</strong></span> and <span class="application"><strong>phc2sys</strong></span> programs for clock synchronization. The <span class="application"><strong>ptp4l</strong></span> program implements the <code class="systemitem">PTP</code> boundary clock and ordinary clock. With hardware time stamping, it is used to synchronize the <code class="systemitem">PTP</code> hardware clock to the master clock, and with software time stamping it synchronizes the system clock to the master clock. The <span class="application"><strong>phc2sys</strong></span> program is needed only with hardware time stamping, for synchronizing the system clock to the <code class="systemitem">PTP</code> hardware clock on the <em class="firstterm">network interface card</em> (<acronym class="acronym">NIC</acronym>).
@@ -7336,7 +7454,7 @@ Hardware Transmit Timestamp Modes:
Hardware Receive Filter Modes:
none (HWTSTAMP_FILTER_NONE)
all (HWTSTAMP_FILTER_ALL)</pre>
- Where <em class="replaceable"><code>eth3</code></em> is the interface you want to check.
+ Where <em class="replaceable"><code>em3</code></em> is the interface you want to check.
</div><div class="para">
For software time stamping support, the parameters list should include:
<div class="itemizedlist"><ul><li class="listitem"><div class="para">
@@ -7367,6 +7485,12 @@ Hardware Receive Filter Modes:
</div><div class="para">
Do not run more than one service to set the system clock's time at the same time. If you intend to serve <code class="systemitem">PTP</code> time using <code class="systemitem">NTP</code>, see <a class="xref" href="#sec-Serving_PTP_Time_with_NTP">Section 15.7, “Serving PTP Time with NTP”</a>.
</div></div><div class="section" id="sec-Starting_ptp4l"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.2.3. Starting ptp4l</h3></div></div></div><div class="para">
+ The <span class="application"><strong>ptp4l</strong></span> program can be started from the command line or it can be started as a service. When running as a service, options are specified in the <code class="filename">/etc/sysconfig/ptp4l</code> file. Options required for use both by the service and on the command line should be specified in the <code class="filename">/etc/ptp4l.conf</code> file. The <code class="filename">/etc/sysconfig/ptp4l</code> file includes the <code class="command">-f /etc/ptp4l.conf</code> command line option, which causes the <code class="systemitem">ptp4l</code> program to read the <code class="filename">/etc/ptp4l.conf</code> file and process the options it contains. The use of the <code class="filename">/etc/ptp4l.conf</code> is explained in <a class="xref" href="#sec-Specifying_a_Configuration_File">Section 15.3, “Specifying a Configuration File”</a>. More information on the different <span class="application"><strong>ptp4l</strong></
span> options and the configuration file settings can be found in the <code class="filename">ptp4l(8)</code> man page.
+ </div><h4 id="bh-Starting_ptp4l_as_a_Service">Starting ptp4l as a Service</h4><div class="para">
+ To start <span class="application"><strong>ptp4l</strong></span> as a service, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl start ptp4l</code></pre>
+
+ </div><h4 id="bh-Using_ptp4l_From_The_Command_Line">Using ptp4l From The Command Line</h4><div class="para">
The <span class="application"><strong>ptp4l</strong></span> program tries to use hardware time stamping by default. To use <span class="application"><strong>ptp4l</strong></span> with hardware time stamping capable drivers and NICs, you must provide the network interface to use with the <code class="option">-i</code> option. Enter the following command as <code class="systemitem">root</code>:
<pre class="screen">~]# <code class="command">ptp4l -i <em class="replaceable"><code>em3</code></em> -m</code></pre>
Where <em class="replaceable"><code>em3</code></em> is the interface you want to configure. Below is example output from <span class="application"><strong>ptp4l</strong></span> when the <code class="systemitem">PTP</code> clock on the NIC is synchronized to a master:
@@ -7476,7 +7600,17 @@ sending: GET TIME_STATUS_NP
<pre class="screen">~]# <code class="command">pmc help</code></pre>
Additional information is available in the <code class="filename">pmc(8)</code> man page.
</div></div><div class="section" id="sec-Synchronizing_the_Clocks"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.5. Synchronizing the Clocks</h2></div></div></div><div class="para">
- The <span class="application"><strong>phc2sys</strong></span> program is used to synchronize the system clock to the <code class="systemitem">PTP</code> hardware clock (<acronym class="acronym">PHC</acronym>) on the NIC. To start <span class="application"><strong>phc2sys</strong></span>, where <em class="replaceable"><code>em3</code></em> is the interface with the <code class="systemitem">PTP</code> hardware clock, enter the following command as <code class="systemitem">root</code>:
+ The <span class="application"><strong>phc2sys</strong></span> program is used to synchronize the system clock to the <code class="systemitem">PTP</code> hardware clock (<acronym class="acronym">PHC</acronym>) on the NIC. The <span class="application"><strong>phc2sys</strong></span> service is configured in the <code class="filename">/etc/sysconfig/phc2sys</code> configuration file. The default setting in the <code class="filename">/etc/sysconfig/phc2sys</code> file is as follows: <pre class="synopsis">OPTIONS="-a -r"</pre> The <code class="option">-a</code> option causes <span class="application"><strong>phc2sys</strong></span> to read the clocks to be synchronized from the <span class="application"><strong>ptp4l</strong></span> application. It will follow changes in the <code class="systemitem">PTP</code> port states, adjusting the synchronization between the NIC hardware clocks accordingly. The system clock is not synchronized, unless the <code class="option">-r</code>
option is also specified. If you want the system clock to be eligible to become a time source, specify the <code class="option">-r</code> option twice.
+ </div><div class="para">
+ After making changes to <code class="filename">/etc/sysconfig/phc2sys</code>, restart the <span class="application"><strong>phc2sys</strong></span> service from the command line by issuing a command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl restart phc2sys</code></pre>
+ Under normal circumstances, use <code class="command">systemctl</code> commands to start, stop, and restart the <span class="application"><strong>phc2sys</strong></span> service.
+ </div><div class="para">
+ When you do not want to start <span class="application"><strong>phc2sys</strong></span> as a service, you can start it from the command line. For example, enter the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">phc2sys -a -r</code></pre>
+ The <code class="option">-a</code> option causes <span class="application"><strong>phc2sys</strong></span> to read the clocks to be synchronized from the <span class="application"><strong>ptp4l</strong></span> application. If you want the system clock to be eligible to become a time source, specify the <code class="option">-r</code> option twice.
+ </div><div class="para">
+ Alternately, use the <code class="option">-s</code> option to synchronize the system clock to a specific interface's <code class="systemitem">PTP</code> hardware clock. For example:
<pre class="screen">~]# <code class="command">phc2sys -s <em class="replaceable"><code>em3</code></em> -w</code></pre>
The <code class="option">-w</code> option waits for the running <span class="application"><strong>ptp4l</strong></span> application to synchronize the <code class="systemitem">PTP</code> clock and then retrieves the <acronym class="acronym">TAI</acronym> to <acronym class="acronym">UTC</acronym> offset from <span class="application"><strong>ptp4l</strong></span>.
</div><div class="para">
@@ -7594,35 +7728,155 @@ priority1 127
[em3]
# ptp4l -f /etc/ptp4l.conf</pre>
</div><div class="para">
- With hardware time stamping, <span class="application"><strong>phc2sys</strong></span> needs to be used to synchronize the <code class="systemitem">PTP</code> hardware clock to the system clock:
-<pre class="screen">~]# <code class="command">phc2sys -c <em class="replaceable"><code>em3</code></em> -s CLOCK_REALTIME -w</code></pre>
-
+ With hardware time stamping, <span class="application"><strong>phc2sys</strong></span> needs to be used to synchronize the <code class="systemitem">PTP</code> hardware clock to the system clock. If running <span class="application"><strong>phc2sys</strong></span> as a service, edit the <code class="filename">/etc/sysconfig/phc2sys</code> configuration file. The default setting in the <code class="filename">/etc/sysconfig/phc2sys</code> file is as follows: <pre class="synopsis">OPTIONS="-a -r"</pre> As <code class="systemitem">root</code>, edit that line as follows:
+<pre class="screen">~]# <code class="command">vi /etc/sysconfig/phc2sys</code>
+OPTIONS="-a -r -r"</pre>
+ The <code class="option">-r</code> option is used twice here to allow synchronization of the <code class="systemitem">PTP</code> hardware clock on the NIC from the system clock. Restart the <span class="application"><strong>phc2sys</strong></span> service for the changes to take effect:
+<pre class="screen">~]# <code class="command">systemctl restart phc2sys</code></pre>
</div><div class="para">
- To prevent quick changes in the <code class="systemitem">PTP</code> clock's frequency, the synchronization to the system clock can be loosened by using smaller <code class="option">P</code> (proportional) and <code class="option">I</code> (integral) constants of the PI servo:
-<pre class="screen">~]# <code class="command">phc2sys -c <em class="replaceable"><code>em3</code></em> -s CLOCK_REALTIME -w -P 0.01 -I 0.0001</code></pre>
+ To prevent quick changes in the <code class="systemitem">PTP</code> clock's frequency, the synchronization to the system clock can be loosened by using smaller <code class="option">P</code> (proportional) and <code class="option">I</code> (integral) constants for the PI servo:
+<pre class="screen">~]# <code class="command">phc2sys -a -r -r -P 0.01 -I 0.0001</code></pre>
+
+ </div></div><div class="section" id="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.9. Synchronize to PTP or NTP Time Using timemaster</h2></div></div></div><div class="para">
+ When there are multiple <code class="systemitem">PTP</code> domains available on the network, or fallback to <code class="systemitem">NTP</code> is needed, the <span class="application"><strong>timemaster</strong></span> program can be used to synchronize the system clock to all available time sources. The <code class="systemitem">PTP</code> time is provided by <span class="application"><strong>phc2sys</strong></span> and <span class="application"><strong>ptp4l</strong></span> via <em class="firstterm">shared memory driver</em> (<acronym class="acronym">SHM</acronym> reference clocks to <code class="systemitem">chronyd</code> or <code class="systemitem">ntpd</code> (depending on the <code class="systemitem">NTP</code> daemon that has been configured on the system). The <code class="systemitem">NTP</code> daemon can then compare all time sources, both <code class="systemitem">PTP</code> and <code class="systemitem">NTP</code>, and use the best sources to synchronize the sy
stem clock.
+ </div><div class="para">
+ On start, <span class="application"><strong>timemaster</strong></span> reads a configuration file that specifies the <code class="systemitem">NTP</code> and <code class="systemitem">PTP</code> time sources, checks which network interfaces have their own or share a <code class="systemitem">PTP</code> hardware clock (PHC), generates configuration files for <span class="application"><strong>ptp4l</strong></span> and <code class="systemitem">chronyd</code> or <code class="systemitem">ntpd</code>, and starts the <span class="application"><strong>ptp4l</strong></span>, <span class="application"><strong>phc2sys</strong></span>, and <code class="systemitem">chronyd</code> or <code class="systemitem">ntpd</code> processes as needed. It will remove the generated configuration files on exit. It writes configuration files for <code class="systemitem">chronyd</code>, <code class="systemitem">ntpd</code>, and <span class="application"><strong>ptp4l</strong></span> to <code class="filen
ame">/var/run/timemaster/</code>.
+ </div><div class="section" id="sec-Starting_timemaster_as_a_Service"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.9.1. Starting timemaster as a Service</h3></div></div></div><div class="para">
+ To start <span class="application"><strong>timemaster</strong></span> as a service, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl start timemaster</code></pre>
+ This will read the options in <code class="filename"> /etc/timemaster.conf</code>.
+ </div></div><div class="section" id="sec-Understanding_the_timemaster_Configuration_File"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.9.2. Understanding the timemaster Configuration File</h3></div></div></div><div class="para">
+ Fedora provides a default <code class="filename">/etc/timemaster.conf</code> file with a number of sections containing default options. The section headings are enclosed in brackets.
+ </div><div class="para">
+ To view the default configuration, issue a command as follows:
+<pre class="screen">~]$ <code class="command">less /etc/timemaster.conf</code>
+# Configuration file for timemaster
+
+#[ntp_server ntp-server.local]
+#minpoll 4
+#maxpoll 4
+
+#[ptp_domain 0]
+#interfaces eth0
+
+[timemaster]
+ntp_program chronyd
+
+[chrony.conf]
+include /etc/chrony.conf
+
+[ntp.conf]
+includefile /etc/ntp.conf
+
+[ptp4l.conf]
+
+[chronyd]
+path /usr/sbin/chronyd
+options -u chrony
+
+[ntpd]
+path /usr/sbin/ntpd
+options -u ntp:ntp -g
+
+[phc2sys]
+path /usr/sbin/phc2sys
+
+[ptp4l]
+path /usr/sbin/ptp4l</pre>
+ </div><div class="para">
+ Notice the section named as follows: <pre class="synopsis">[ntp_server <em class="replaceable"><code>address</code></em>]</pre> This is an example of an <code class="systemitem">NTP</code> server section, <span class="quote">“<span class="quote">ntp-server.local</span>”</span> is an example of a host name for an <code class="systemitem">NTP</code> server on the local LAN. Add more sections as required using a host name or <code class="systemitem">IP</code> address as part of the section name. Note that the short polling values in that example section are not suitable for a public server, see <a class="xref" href="#ch-Configuring_NTP_Using_ntpd">Chapter 14, <em>Configuring NTP Using ntpd</em></a> for an explanation of suitable <code class="option">minpoll</code> and <code class="option">maxpoll</code> values.
+ </div><div class="para">
+ Notice the section named as follows: <pre class="synopsis">[ptp_domain <em class="replaceable"><code>number</code></em>]</pre> A <span class="quote">“<span class="quote">PTP domain</span>”</span> is a group of one or more <code class="systemitem">PTP</code> clocks that synchronize to each other. They may or may not be synchronized to clocks in another domain. Clocks that are configured with the same domain number make up the domain. This includes a <code class="systemitem">PTP</code> grandmaster clock. The domain number in each <span class="quote">“<span class="quote">PTP domain</span>”</span> section needs to correspond to one of the <code class="systemitem">PTP</code> domains configured on the network.
+ </div><div class="para">
+ An instance of <span class="application"><strong>ptp4l</strong></span> is started for every interface which has its own <code class="systemitem">PTP</code> clock and hardware time stamping is enabled automatically. Interfaces that support hardware time stamping have a <code class="systemitem">PTP</code> clock (PHC) attached, however it is possible for a group of interfaces on a NIC to share a PHC. A separate <span class="application"><strong>ptp4l</strong></span> instance will be started for each group of interfaces sharing the same PHC and for each interface that supports only software time stamping. All <span class="application"><strong>ptp4l</strong></span> instances are configured to run as a slave. If an interface with hardware time stamping is specified in more than one <code class="systemitem">PTP</code> domain, then only the first <span class="application"><strong>ptp4l</strong></span> instance created will have hardware time stamping enabled.
+ </div><div class="para">
+ Notice the section named as follows: <pre class="synopsis">[timemaster]</pre> The default <span class="application"><strong>timemaster</strong></span> configuration includes the system <code class="systemitem">ntpd</code> and chrony configuration (<code class="filename">/etc/ntp.conf</code> or <code class="filename">/etc/chronyd.conf</code>) in order to include the configuration of access restrictions and authentication keys. That means any <code class="systemitem">NTP</code> servers specified there will be used with <span class="application"><strong>timemaster</strong></span> too.
+ </div><div class="para">
+ The section headings are as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">[ntp_server ntp-server.local]</code> — Specify polling intervals for this server. Create additional sections as required. Include the host name or <code class="systemitem">IP</code> address in the section heading.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[ptp_domain 0]</code> — Specify interfaces that have <code class="systemitem">PTP</code> clocks configured for this domain. Create additional sections with, the appropriate domain number, as required.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[timemaster]</code> — Specify the <code class="systemitem">NTP</code> daemon to be used. Possible values are <code class="systemitem">chronyd</code> and <code class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[chrony.conf]</code> — Specify any additional settings to be copied to the configuration file generated for <code class="systemitem">chronyd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[ntp.conf]</code> — Specify any additional settings to be copied to the configuration file generated for <code class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[ptp4l.conf]</code> — Specify options to be copied to the configuration file generated for <span class="application"><strong>ptp4l</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[chronyd]</code> — Specify any additional settings to be passed on the command line to <code class="systemitem">chronyd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[ntpd]</code> — Specify any additional settings to be passed on the command line to <code class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[phc2sys]</code> — Specify any additional settings to be passed on the command line to <span class="application"><strong>phc2sys</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[ptp4l]</code> — Specify any additional settings to be passed on the command line to all instances of <span class="application"><strong>ptp4l</strong></span>.
+ </div></li></ul></div><div class="para">
+ The section headings and there contents are explained in detail in the <code class="filename">timemaster(8)</code> manual page.
+ </div></div><div class="section" id="sec-Configuring_timemaster_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.9.3. Configuring timemaster Options</h3></div></div></div><div class="procedure" id="proc-Editing_the_timemaster_Configuration_File"><h6>Procedure 15.1. Editing the timemaster Configuration File</h6><ol class="1"><li class="step"><div class="para">
+ To change the default configuration, open the <code class="filename">/etc/timemaster.conf</code> file for editing as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">vi /etc/timemaster.conf</code></pre>
+ </div></li><li class="step"><div class="para">
+ For each <code class="systemitem">NTP</code> server you want to control using <span class="application"><strong>timemaster</strong></span>, create <code class="computeroutput">[ntp_server <em class="replaceable"><code>address</code></em>]</code> sections . Note that the short polling values in the example section are not suitable for a public server, see <a class="xref" href="#ch-Configuring_NTP_Using_ntpd">Chapter 14, <em>Configuring NTP Using ntpd</em></a> for an explanation of suitable <code class="option">minpoll</code> and <code class="option">maxpoll</code> values.
+ </div></li><li class="step"><div class="para">
+ To add interfaces that should be used in a domain, edit the <code class="computeroutput">#[ptp_domain 0]</code> section and add the interfaces. Create additional domains as required. For example:
+<pre class="screen">[ptp_domain 0]
+ interfaces eth0
+
+ [ptp_domain 1]
+ interfaces eth1</pre>
+ </div></li><li class="step"><div class="para">
+ If required to use <code class="systemitem">ntpd</code> as the <code class="systemitem">NTP</code> daemon on this system, change the default entry in the <code class="computeroutput">[timemaster]</code> section from <code class="systemitem">chronyd</code> to <code class="systemitem">ntpd</code>. See <a class="xref" href="#ch-Configuring_NTP_Using_the_chrony_Suite">Chapter 13, <em>Configuring NTP Using the chrony Suite</em></a> for information on the differences between ntpd and chronyd.
+ </div></li><li class="step"><div class="para">
+ If using <code class="systemitem">chronyd</code> as the <code class="systemitem">NTP</code> server on this system, add any additional options below the default <code class="option">include /etc/chrony.conf</code> entry in the <code class="computeroutput">[chrony.conf]</code> section. Edit the default <code class="option">include</code> entry if the path to <code class="filename">/etc/chrony.conf</code> is known to have changed.
+ </div></li><li class="step"><div class="para">
+ If using <code class="systemitem">ntpd</code> as the <code class="systemitem">NTP</code> server on this system, add any additional options below the default <code class="option">include /etc/ntp.conf</code> entry in the <code class="computeroutput">[ntp.conf]</code> section. Edit the default <code class="option">include</code> entry if the path to <code class="filename">/etc/ntp.conf</code> is known to have changed.
+ </div></li><li class="step"><div class="para">
+ In the <code class="computeroutput">[ptp4l.conf]</code> section, add any options to be copied to the configuration file generated for <span class="application"><strong>ptp4l</strong></span>. This chapter documents common options and more information is available in the <code class="filename">ptp4l(8)</code> manual page.
+ </div></li><li class="step"><div class="para">
+ In the <code class="computeroutput">[chronyd]</code> section, add any command line options to be passed to <code class="systemitem">chronyd</code> when called by <span class="application"><strong>timemaster</strong></span>. See <a class="xref" href="#ch-Configuring_NTP_Using_the_chrony_Suite">Chapter 13, <em>Configuring NTP Using the chrony Suite</em></a> for information on using <code class="systemitem">chronyd</code>.
+ </div></li><li class="step"><div class="para">
+ In the <code class="computeroutput">[ntpd]</code> section, add any command line options to be passed to <code class="systemitem">ntpd</code> when called by <span class="application"><strong>timemaster</strong></span>. See <a class="xref" href="#ch-Configuring_NTP_Using_ntpd">Chapter 14, <em>Configuring NTP Using ntpd</em></a> for information on using <code class="systemitem">ntpd</code>.
+ </div></li><li class="step"><div class="para">
+ In the <code class="computeroutput">[phc2sys]</code> section, add any command line options to be passed to <span class="application"><strong>phc2sys</strong></span> when called by <span class="application"><strong>timemaster</strong></span>. This chapter documents common options and more information is available in the <code class="filename">phy2sys(8)</code> manual page.
+ </div></li><li class="step"><div class="para">
+ In the <code class="computeroutput">[ptp4l]</code> section, add any command line options to be passed to <span class="application"><strong>ptp4l</strong></span> when called by <span class="application"><strong>timemaster</strong></span>. This chapter documents common options and more information is available in the <code class="filename">ptp4l(8)</code> manual page.
+ </div></li><li class="step"><div class="para">
+ Save the configuration file and restart <span class="application"><strong>timemaster</strong></span> by issuing the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl restart timemaster</code></pre>
- </div></div><div class="section" id="sec-Improving_Accuracy"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.9. Improving Accuracy</h2></div></div></div><div class="para">
- Test results indicate that disabling the tickless kernel capability can significantly improve the stability of the system clock, and thus improve the <code class="systemitem">PTP</code> synchronization accuracy (at the cost of increased power consumption). The kernel tickless mode can be disabled by adding <code class="option">nohz=off</code> to the kernel boot option parameters.
- </div></div><div class="section" id="sec-PTP_additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.10. Additional Resources</h2></div></div></div><div class="para">
+ </div></li></ol></div></div></div><div class="section" id="sec-Improving_Accuracy"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.10. Improving Accuracy</h2></div></div></div><div class="para">
+ Previously, test results indicated that disabling the tickless kernel capability could significantly improve the stability of the system clock, and thus improve the <code class="systemitem">PTP</code> synchronization accuracy (at the cost of increased power consumption). The kernel tickless mode can be disabled by adding <code class="option">nohz=off</code> to the kernel boot option parameters. However, recent improvements applied to <code class="filename">kernel-3.10.0-197.fc21</code> have greatly improved the stability of the system clock and the difference in stability of the clock with and without <code class="option">nohz=off</code> should be much smaller now for most users.
+ </div><div class="para">
+ The <span class="application"><strong>ptp4l</strong></span> and <span class="application"><strong>phc2sys</strong></span> applications can be configured to use a new adaptive servo. The advantage over the PI servo is that it does not require configuration of the PI constants to perform well. To make use of this for <span class="application"><strong>ptp4l</strong></span>, add the following line to the <code class="filename">/etc/ptp4l.conf</code> file: <pre class="synopsis">clock_servo linreg</pre> After making changes to <code class="filename">/etc/ptp4l.conf</code>, restart the <span class="application"><strong>ptp4l</strong></span> service from the command line by issuing the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl restart ptp4l</code></pre>
+ </div><div class="para">
+ To make use of this for <span class="application"><strong>phc2sys</strong></span>, add the following line to the <code class="filename">/etc/sysconfig/phc2sys</code> file: <pre class="synopsis">-E linreg</pre> After making changes to <code class="filename">/etc/sysconfig/phc2sys</code>, restart the <span class="application"><strong>phc2sys</strong></span> service from the command line by issuing the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl restart phc2sys</code></pre>
+ </div></div><div class="section" id="sec-PTP_additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.11. Additional Resources</h2></div></div></div><div class="para">
The following sources of information provide additional resources regarding <code class="systemitem">PTP</code> and the <span class="application"><strong>ptp4l</strong></span> tools.
- </div><div class="section" id="sec-PTP-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.10.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><div class="section" id="sec-PTP-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.11.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="filename">ptp4l(8)</code> man page — Describes <span class="application"><strong>ptp4l</strong></span> options including the format of the configuration file.
</div></li><li class="listitem"><div class="para">
<code class="filename">pmc(8)</code> man page — Describes the <code class="systemitem">PTP</code> management client and its command options.
</div></li><li class="listitem"><div class="para">
<code class="filename">phc2sys(8)</code> man page — Describes a tool for synchronizing the system clock to a <code class="systemitem">PTP</code> hardware clock (PHC).
- </div></li></ul></div></div><div class="section" id="sec-PTP_useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.10.2. Useful Websites</h3></div></div></div><div class="para">
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">timemaster(8)</code> man page — Describes a program that uses <span class="application"><strong>ptp4l</strong></span> and <span class="application"><strong>phc2sys</strong></span> to synchronize the system clock using <code class="systemitem">chronyd</code> or <code class="systemitem">ntpd</code>.
+ </div></li></ul></div></div><div class="section" id="sec-PTP_useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.11.2. Useful Websites</h3></div></div></div><div class="para">
<div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://linuxptp.sourceforge.net/">http://linuxptp.sourceforge.net/</a></span></dt><dd><div class="para">
The Linux PTP project.
</div></dd><dt class="varlistentry"><span class="term"><a href="http://www.nist.gov/el/isd/ieee/ieee1588.cfm">http://www.nist.gov/el/isd/ieee/ieee1588.cfm</a></span></dt><dd><div class="para">
The IEEE 1588 Standard.
</div></dd></dl></div>
- </div></div></div></div></div><div class="part" id="part-Monitoring_and_Automation"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part V. Monitoring and Automation</h1></div></div></div><div class="partintro" id="idm225437610112"><div></div><div class="para">
+ </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 V. Monitoring and Automation</h1></div></div></div><div class="partintro" id="idm261763669392"><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 class="toc"><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. Viewing System Processes</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-system-processes-ps">16.1.1. Using the ps Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-system-processes-top">16.1.2. Using the top Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-system-processes-system_monitor">16.1.3. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-memory-usage">16.2. Viewing Memory Usage</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-memory-usage-free">16.2.1. Using the free Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-memory-usage-system_monitor">16.2
.2. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-cpu">16.3. Viewing CPU Usage</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-cpu-system_monitor">16.3.1. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-filesystems">16.4. Viewing Block Devices and File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-filesystems-lsblk">16.4.1. Using the lsblk Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-blkid">16.4.2. Using the blkid Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-partx">16.4.3. Using the partx Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-findmnt">16.4.4. Using the findmnt Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-df">16.4.5. Using the df Command</a></span></dt><dt><span
class="section"><a href="#s2-sysinfo-filesystems-du">16.4.6. Using the du Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-system_monitor">16.4.7. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-hardware">16.5. Viewing Hardware Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-hardware-lspci">16.5.1. Using the lspci Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lsusb">16.5.2. Using the lsusb Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lspcmcia">16.5.3. Using the lspcmcia Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lscpu">16.5.4. Using the lscpu Command</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP">16.6. Monitoring Performance with Net-SNMP</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-S
ystem_Monitoring_Tools-Net-SNMP-Installing">16.6.1. Installing Net-SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Running">16.6.2. Running the Net-SNMP Daemon</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Configuring">16.6.3. Configuring Net-SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Retrieving">16.6.4. Retrieving Performance Data over SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Extending">16.6.5. Extending Net-SNMP</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-additional-resources">16.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-installed-docs">16.7.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 File
s</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 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 cla
ss="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="#sect-Cron-Installing">18.1.1. Installing Cron and Anacron</a></span></dt><dt><span class="section"><a href="#sect-Cron-Running">18.1.2. Running the Crond Service</a></span></dt><dt><span class="section"><a href="#s2-configuring-anacron-jobs">18.1.3. Configuring Anacron Jobs</a></spa
n></dt><dt><span class="section"><a href="#s2-configuring-cron-jobs">18.1.4. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-cron-access">18.1.5. Controlling Access to Cron</a></span></dt><dt><span class="section"><a href="#s2-black-white-listing-of-cron-jobs">18.1.6. Black and 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="#sect-At_and_Batch_Installation">18.2.1. Installing At and Batch</a></span></dt><dt><span class="section"><a href="#sect-Atd-Running">18.2.2. Running the At Service</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-configuring">18.2.3. Configuring an At Job</a></span></dt><dt><span class="section"><a href="#s2-autotasks-batch-configuring">18.2.4. Configuring a Batch Job</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-viewing">18.2.5. View
ing Pending Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-commandline-options">18.2.6. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-controlling-access">18.2.7. Controlling Access to At and Batch</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-autotasks-additional-resources">18.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-OProfile">19. OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-overview-tools">19.1. Overview of Tools</a></span></dt><dt><span class="section"><a href="#s1-oprofile-configuring">19.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-kernel">19.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="#s2-oprofile-events">19.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="#s2-oprofile-starting-s
eparate">19.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-starting">19.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="#s1-oprofile-saving-data">19.4. Saving Data</a></span></dt><dt><span class="section"><a href="#s1-oprofile-analyzing-data">19.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-reading-opreport">19.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opreport-single">19.5.2. Using opreport on a Single Executable</a></span></dt><dt><span class="section"><a href="#s2-oprofile-module-output">19.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opannotate">19.5.4. Using <code class="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-opro
file-dev-oprofile">19.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="#s1-oprofile-example-usage">19.7. Example Usage</a></span></dt><dt><span class="section"><a href="#s1-oprofile-java-support">19.8. OProfile Support for Java</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-java-profiling">19.8.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-gui">19.9. Graphical Interface</a></span></dt><dt><span class="section"><a href="#s1-oprofile-and-systemtap">19.10. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="#s1-oprofile-additional-resources">19.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-installed-docs">19.11.1. Installed Docs</a></span></dt><dt><span class="section"><a href="#s2-oprofile-useful-websites">19.11.2. Useful Websites</a></span></dt></dl></dd></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 class="toc"><dt><span class="section"><a href="#s1-sysinfo-system-processes">16.1. Viewing System Processes</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-system-processes-ps">16.1.1. Using the ps Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-system-processes-top">16.1.2. Using the top Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-system-processes-system_monitor">16.1.3. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-memory-usage">16.2. Viewing Memory Usage</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-memory-usage-free">16.2.1. Using the free Command</a></span></dt><dt><span class="section"><a href="#s2-s
ysinfo-memory-usage-system_monitor">16.2.2. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-cpu">16.3. Viewing CPU Usage</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-cpu-system_monitor">16.3.1. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-filesystems">16.4. Viewing Block Devices and File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-filesystems-lsblk">16.4.1. Using the lsblk Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-blkid">16.4.2. Using the blkid Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-partx">16.4.3. Using the partx Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-findmnt">16.4.4. Using the findmnt Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-df">16.4.5. Using
the df Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-du">16.4.6. Using the du Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-system_monitor">16.4.7. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-hardware">16.5. Viewing Hardware Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-hardware-lspci">16.5.1. Using the lspci Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lsusb">16.5.2. Using the lsusb Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lspcmcia">16.5.3. Using the lspcmcia Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lscpu">16.5.4. Using the lscpu Command</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP">16.6. Monitoring Performance with Net-SNMP</a></span></dt><dd><dl><d
t><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Installing">16.6.1. Installing Net-SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Running">16.6.2. Running the Net-SNMP Daemon</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Configuring">16.6.3. Configuring Net-SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Retrieving">16.6.4. Retrieving Performance Data over SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Extending">16.6.5. Extending Net-SNMP</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-additional-resources">16.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-installed-docs">16.7.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="idm225439185488" class="indexterm"></a><a id="idm2254446
97152" class="indexterm"></a><div class="para">
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><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. Viewing System Processes</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-system-processes-ps">16.1.1. Using the ps Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-system-processes-top">16.1.2. Using the top Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-system-processes-system_monitor">16.1.3. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-memory-usage">16.2. Viewing Memory Usage</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-memory-usage-free">16.2.1. Using the free Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-memory-usage-system_monitor">16.2
.2. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-cpu">16.3. Viewing CPU Usage</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-cpu-system_monitor">16.3.1. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-filesystems">16.4. Viewing Block Devices and File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-filesystems-lsblk">16.4.1. Using the lsblk Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-blkid">16.4.2. Using the blkid Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-partx">16.4.3. Using the partx Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-findmnt">16.4.4. Using the findmnt Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-df">16.4.5. Using the df Command</a></span></dt><dt><span
class="section"><a href="#s2-sysinfo-filesystems-du">16.4.6. Using the du Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-system_monitor">16.4.7. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-hardware">16.5. Viewing Hardware Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-hardware-lspci">16.5.1. Using the lspci Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lsusb">16.5.2. Using the lsusb Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lspcmcia">16.5.3. Using the lspcmcia Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lscpu">16.5.4. Using the lscpu Command</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP">16.6. Monitoring Performance with Net-SNMP</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-S
ystem_Monitoring_Tools-Net-SNMP-Installing">16.6.1. Installing Net-SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Running">16.6.2. Running the Net-SNMP Daemon</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Configuring">16.6.3. Configuring Net-SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Retrieving">16.6.4. Retrieving Performance Data over SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Extending">16.6.5. Extending Net-SNMP</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-additional-resources">16.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-installed-docs">16.7.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 File
s</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-logfiles-locating">17.1. Locating Log Files</a></span></dt><dt><span class="section"><a href="#s1-basic_configuration_of_rsyslog">17.2. Basic Configuration of Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Filters">17.2.1. Filters</a></span></dt><dt><span class="section"><a href="#s2-Actions">17.2.2. Actions</a></span></dt><dt><span class="section"><a href="#s2-Templates">17.2.3. Templates</a></span></dt><dt><span class="section"><a href="#s2-global_directives">17.2.4. Global Directives</a></span></dt><dt><span class="section"><a href="#s2-log_rotation">17.2.5. Log Rotation</a></span></dt><dt><span class="section"><a href="#s2-using_the_new_configuration_format">17.2.6. Using the New Configuration Format</a></span></dt><dt><span class="section"><a href="#s2-Rulesets">17.2.7. Rulesets</a></span></dt><dt><span class="section"><a href="#s2-compatibility_with_syslogd">17.2.8. Compatibility wit
h syslogd</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-working_with_queues_in_rsyslog">17.3. Working with Queues in Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-defining_queues">17.3.1. Defining Queues</a></span></dt><dt><span class="section"><a href="#s2-managing_queues">17.3.2. Managing Queues</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-using_rsyslog_modules">17.4. Using Rsyslog Modules</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-importing_text_files">17.4.1. Importing Text Files</a></span></dt><dt><span class="section"><a href="#s2-exporting_messages_to_a_database">17.4.2. Exporting Messages to a Database</a></span></dt><dt><span class="section"><a href="#s2-enabling_encrypted_transport">17.4.3. Enabling Encrypted Transport</a></span></dt><dt><span class="section"><a href="#s2-using_RELP">17.4.4. Using RELP</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-interaction_of_rsyslo
g_and_journal">17.5. Interaction of Rsyslog and Journal</a></span></dt><dt><span class="section"><a href="#s1-structured_logging_with_rsyslog">17.6. Structured Logging with Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-importing_data_from_journal">17.6.1. Importing Data from Journal</a></span></dt><dt><span class="section"><a href="#s2-filtering_structured_messages">17.6.2. Filtering Structured Messages</a></span></dt><dt><span class="section"><a href="#s2-parsing_JSON">17.6.3. Parsing JSON</a></span></dt><dt><span class="section"><a href="#s2-storing_messages_in_the_mongodb">17.6.4. Storing Messages in the MongoDB</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-debugging_rsyslog">17.7. Debugging Rsyslog</a></span></dt><dt><span class="section"><a href="#s1-Using_the_Journal">17.8. Using the Journal</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Viewing_Log_Files">17.8.1. Viewing Log Files</a></span></dt><dt><span class=
"section"><a href="#s2-Access_Control">17.8.2. Access Control</a></span></dt><dt><span class="section"><a href="#s2-Using_The_Live_View">17.8.3. Using The Live View</a></span></dt><dt><span class="section"><a href="#s2-Filtering_Messages">17.8.4. Filtering Messages</a></span></dt><dt><span class="section"><a href="#s2-Enabling_Persistent_Storage">17.8.5. Enabling Persistent Storage</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-managing_log_files_in_a_graphical_environment">17.9. Managing Log Files in a Graphical Environment</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-logfiles-viewing">17.9.1. Viewing Log Files</a></span></dt><dt><span class="section"><a href="#s2-logfiles-adding">17.9.2. Adding a Log File</a></span></dt><dt><span class="section"><a href="#s2-logfiles-examining">17.9.3. Monitoring Log Files</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-log-files-additional-resources">17.10. Additional Resources</a></span><
/dt></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="#sect-Cron-Installing">18.1.1. Installing Cron and Anacron</a></span></dt><dt><span class="section"><a href="#sect-Cron-Running">18.1.2. Running the Crond Service</a></span></dt><dt><span class="section"><a href="#s2-configuring-anacron-jobs">18.1.3. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="#s2-configuring-cron-jobs">18.1.4. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-cron-access">18.1.5. Controlling Access to Cron</a></span></dt><dt><span class="section"><a href="#s2-black-white-listing-of-cron-jobs">18.1.6. Black and 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="#sect-At_and_Batch_Installation">18.2.1. Installing At and Batch</a></span></dt><dt><span class="section"><a href="#sect-Atd-Running">18.2.2. Running the At Service</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-configuring">18.2.3. Configuring an At Job</a></span></dt><dt><span class="section"><a href="#s2-autotasks-batch-configuring">18.2.4. Configuring a Batch Job</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-viewing">18.2.5. Viewing Pending Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-commandline-options">18.2.6. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-controlling-access">18.2.7. Controlling Access to At and Batch</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-autotasks-additional-resources">18.3. Additional Resources</a></span></dt></dl></dd><dt><s
pan class="chapter"><a href="#ch-OProfile">19. OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-overview-tools">19.1. Overview of Tools</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-operf_vs_opcontrol">19.1.1. operf vs. opcontrol</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-using-operf">19.2. Using operf</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-operf-kernel">19.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="#s2-operf-events">19.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="#s2-operf-categorization">19.2.3. Categorization of Samples</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-configuring">19.3. Configuring OProfile Using Legacy Mode</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-kernel">19.3.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="#s2-oprof
ile-events">19.3.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="#s2-oprofile-starting-separate">19.3.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-starting">19.4. Starting and Stopping OProfile Using Legacy Mode</a></span></dt><dt><span class="section"><a href="#s1-oprofile-saving-data">19.5. Saving Data in Legacy Mode</a></span></dt><dt><span class="section"><a href="#s1-oprofile-analyzing-data">19.6. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-reading-opreport">19.6.1. Using <code class="command">opreport</code></a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opreport-single">19.6.2. Using opreport on a Single Executable</a></span></dt><dt><span class="section"><a href="#s2-oprofile-module-output">19.6.3. Getting More Detailed Output on the Modules</a></span></dt><dt><span class="section"><a href="#s2-o
profile-reading-opannotate">19.6.4. Using <code class="command">opannotate</code></a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-dev-oprofile">19.7. Understanding the /dev/oprofile/ directory </a></span></dt><dt><span class="section"><a href="#s1-oprofile-example-usage">19.8. Example Usage</a></span></dt><dt><span class="section"><a href="#s1-oprofile-java-support">19.9. OProfile Support for Java</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-java-profiling">19.9.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-gui">19.10. Graphical Interface</a></span></dt><dt><span class="section"><a href="#s1-oprofile-and-systemtap">19.11. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="#s1-oprofile_additional_resources">19.12. Additional Resources</a></span></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" id="ch-System_Monitoring_Tools" lang="en-U
S"><div class="titlepage"><div><div><h2 class="title">Chapter 16. System Monitoring Tools</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-sysinfo-system-processes">16.1. Viewing System Processes</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-system-processes-ps">16.1.1. Using the ps Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-system-processes-top">16.1.2. Using the top Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-system-processes-system_monitor">16.1.3. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-memory-usage">16.2. Viewing Memory Usage</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-memory-usage-free">16.2.1. Using the free Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-memory-usage-system_monitor">16.2.2. Using the System Monitor Tool</a></span></dt></
dl></dd><dt><span class="section"><a href="#s1-sysinfo-cpu">16.3. Viewing CPU Usage</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-cpu-system_monitor">16.3.1. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-filesystems">16.4. Viewing Block Devices and File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-filesystems-lsblk">16.4.1. Using the lsblk Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-blkid">16.4.2. Using the blkid Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-partx">16.4.3. Using the partx Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-findmnt">16.4.4. Using the findmnt Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-df">16.4.5. Using the df Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-du
">16.4.6. Using the du Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-filesystems-system_monitor">16.4.7. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-hardware">16.5. Viewing Hardware Information</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-hardware-lspci">16.5.1. Using the lspci Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lsusb">16.5.2. Using the lsusb Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lspcmcia">16.5.3. Using the lspcmcia Command</a></span></dt><dt><span class="section"><a href="#s2-sysinfo-hardware-lscpu">16.5.4. Using the lscpu Command</a></span></dt></dl></dd><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP">16.6. Monitoring Performance with Net-SNMP</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Installing">16.6.1.
Installing Net-SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Running">16.6.2. Running the Net-SNMP Daemon</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Configuring">16.6.3. Configuring Net-SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Retrieving">16.6.4. Retrieving Performance Data over SNMP</a></span></dt><dt><span class="section"><a href="#sect-System_Monitoring_Tools-Net-SNMP-Extending">16.6.5. Extending Net-SNMP</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-sysinfo-additional-resources">16.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-sysinfo-installed-docs">16.7.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="idm261714424288" class="indexterm"></a><a id="idm261754601296" class="indexterm"></a><div class="para">
In order to configure the system, system administrators often need to determine the amount of free memory, how much free disk space is available, how the hard drive is partitioned, or what processes are running.
- </div><div class="section" id="s1-sysinfo-system-processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.1. Viewing System Processes</h2></div></div></div><a id="idm225439438416" class="indexterm"></a><a id="idm225443174864" class="indexterm"></a><div class="section" id="s2-sysinfo-system-processes-ps"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.1.1. Using the ps Command</h3></div></div></div><a id="idm225445573136" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s1-sysinfo-system-processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.1. Viewing System Processes</h2></div></div></div><a id="idm261740288656" class="indexterm"></a><a id="idm261653143104" class="indexterm"></a><div class="section" id="s2-sysinfo-system-processes-ps"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.1.1. Using the ps Command</h3></div></div></div><a id="idm261752577504" class="indexterm"></a><div class="para">
The <code class="command">ps</code> command allows you to display information about running processes. It produces a static list, that is, a snapshot of what is running when you execute the command. If you want a constantly updated list of running processes, use the <code class="command">top</code> command or the <span class="application"><strong>System Monitor</strong></span> application instead.
</div><div class="para">
To list all processes that are currently running on the system including processes owned by other users, type the following at a shell prompt:
@@ -7651,7 +7905,7 @@ root 6 0.0 0.0 0 0 ? S 13:28 0:00 [migration/0]
</div><pre class="screen">~]$ <code class="command">ps ax | grep emacs</code>
2625 ? Sl 0:00 emacs</pre><div class="para">
For a complete list of available command line options, refer to the <span class="bold bold"><strong>ps</strong></span>(1) manual page.
- </div></div><div class="section" id="s2-sysinfo-system-processes-top"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.1.2. Using the top Command</h3></div></div></div><a id="idm225500238464" class="indexterm"></a><a id="idm225436253152" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-sysinfo-system-processes-top"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.1.2. Using the top Command</h3></div></div></div><a id="idm261721919728" class="indexterm"></a><a id="idm261650345696" class="indexterm"></a><div class="para">
The <code class="command">top</code> command displays a real-time list of processes that are running on the system. It also displays additional information about the system uptime, current CPU and memory usage, or total number of running processes, and allows you to perform actions such as sorting the list or killing a process.
</div><div class="para">
To run the <code class="command">top</code> command, type the following at a shell prompt:
@@ -7719,7 +7973,7 @@ Swap: 1540092k total, 55780k used, 1484312k free, 256408k cached
<span class="keycap"><strong>q</strong></span>
</td><td class="">
Terminates the utility and returns to the shell prompt.
- </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="s2-sysinfo-system-processes-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.1.3. Using the System Monitor Tool</h3></div></div></div><a id="idm225442946048" class="indexterm"></a><a id="idm225473416400" class="indexterm"></a><div class="para">
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="s2-sysinfo-system-processes-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.1.3. Using the System Monitor Tool</h3></div></div></div><a id="idm261725106992" class="indexterm"></a><a id="idm261737938480" class="indexterm"></a><div class="para">
The <span class="guilabel"><strong>Processes</strong></span> tab of the <span class="application"><strong>System Monitor</strong></span> tool allows you to view, search for, change the priority of, and kill processes from the graphical user interface.
</div><div class="para">
To start the <span class="application"><strong>System Monitor</strong></span> tool, either select <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Monitor</strong></span> from the <span class="guimenu"><strong>Activities</strong></span> menu, or type <code class="command">gnome-system-monitor</code> at a shell prompt. Then click the <span class="guilabel"><strong>Processes</strong></span> tab to view the list of running processes.
@@ -7759,7 +8013,7 @@ Swap: 1540092k total, 55780k used, 1484312k free, 256408k cached
edit the <span class="application"><strong>System Monitor</strong></span> preferences, such as the refresh interval for the list of processes, or what information to show.
</div></li></ul></div><div class="para">
You can also end a process by selecting it from the list and clicking the <span class="guibutton"><strong>End Process</strong></span> button.
- </div></div></div><div class="section" id="s1-sysinfo-memory-usage"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.2. Viewing Memory Usage</h2></div></div></div><a id="idm225444465808" class="indexterm"></a><a id="idm225444464368" class="indexterm"></a><a id="idm225479283776" class="indexterm"></a><div class="section" id="s2-sysinfo-memory-usage-free"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.2.1. Using the free Command</h3></div></div></div><a id="idm225479281856" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s1-sysinfo-memory-usage"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.2. Viewing Memory Usage</h2></div></div></div><a id="idm261712027472" class="indexterm"></a><a id="idm261733826320" class="indexterm"></a><a id="idm261733825360" class="indexterm"></a><div class="section" id="s2-sysinfo-memory-usage-free"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.2.1. Using the free Command</h3></div></div></div><a id="idm261758089152" class="indexterm"></a><div class="para">
The <code class="command">free</code> command allows you to display the amount of free and used memory on the system. To do so, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">free</code></pre><div class="para">
The <code class="command">free</code> command provides information about both the physical memory (<code class="computeroutput">Mem</code>) and swap space (<code class="computeroutput">Swap</code>). It displays the total amount of memory (<code class="computeroutput">total</code>), as well as the amount of memory that is in use (<code class="computeroutput">used</code>), free (<code class="computeroutput">free</code>), shared (<code class="computeroutput">shared</code>), in kernel buffers (<code class="computeroutput">buffers</code>), and cached (<code class="computeroutput">cached</code>). For example:
@@ -7777,7 +8031,7 @@ Mem: 744 593 150 0 36 152
-/+ buffers/cache: 404 339
Swap: 1503 82 1421</pre><div class="para">
For a complete list of available command line options, refer to the <span class="bold bold"><strong>free</strong></span>(1) manual page.
- </div></div><div class="section" id="s2-sysinfo-memory-usage-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.2.2. Using the System Monitor Tool</h3></div></div></div><a id="idm225455355840" class="indexterm"></a><a id="idm225455354720" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-sysinfo-memory-usage-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.2.2. Using the System Monitor Tool</h3></div></div></div><a id="idm261747198112" class="indexterm"></a><a id="idm261747196992" class="indexterm"></a><div class="para">
The <span class="guilabel"><strong>Resources</strong></span> tab of the <span class="application"><strong>System Monitor</strong></span> tool allows you to view the amount of free and used memory on the system.
</div><div class="para">
To start the <span class="application"><strong>System Monitor</strong></span> tool, either select <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Monitor</strong></span> from the <span class="guimenu"><strong>Activities</strong></span> menu, or type <code class="command">gnome-system-monitor</code> at a shell prompt. Then click the <span class="guilabel"><strong>Resources</strong></span> tab to view the system's memory usage.
@@ -7785,7 +8039,7 @@ Swap: 1503 82 1421</pre><div class="para">
The <span class="guilabel"><strong>Resources</strong></span> tab of the <span class="application"><strong>System Monitor</strong></span> application.
</div></div></div></div><h6>Figure 16.2. System Monitor — Resources</h6></div><br class="figure-break" /><div class="para">
In the <span class="guilabel"><strong>Memory and Swap History</strong></span> section, the <span class="application"><strong>System Monitor</strong></span> tool displays a graphical representation of the memory and swap usage history, as well as the total amount of the physical memory (<span class="guilabel"><strong>Memory</strong></span>) and swap space (<span class="guilabel"><strong>Swap</strong></span>) and how much of it is in use.
- </div></div></div><div class="section" id="s1-sysinfo-cpu"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.3. Viewing CPU Usage</h2></div></div></div><a id="idm225480886064" class="indexterm"></a><a id="idm225480884624" class="indexterm"></a><div class="section" id="s2-sysinfo-cpu-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.3.1. Using the System Monitor Tool</h3></div></div></div><a id="idm225445955072" class="indexterm"></a><a id="idm225445953952" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s1-sysinfo-cpu"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.3. Viewing CPU Usage</h2></div></div></div><a id="idm261751106448" class="indexterm"></a><a id="idm261751105008" class="indexterm"></a><div class="section" id="s2-sysinfo-cpu-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.3.1. Using the System Monitor Tool</h3></div></div></div><a id="idm261714346288" class="indexterm"></a><a id="idm261714345168" class="indexterm"></a><div class="para">
The <span class="guilabel"><strong>Resources</strong></span> tab of the <span class="application"><strong>System Monitor</strong></span> tool allows you to view the current CPU usage on the system.
</div><div class="para">
To start the <span class="application"><strong>System Monitor</strong></span> tool, either select <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Monitor</strong></span> from the <span class="guimenu"><strong>Activities</strong></span> menu, or type <code class="command">gnome-system-monitor</code> at a shell prompt. Then click the <span class="guilabel"><strong>Resources</strong></span> tab to view the system's CPU usage.
@@ -7793,7 +8047,7 @@ Swap: 1503 82 1421</pre><div class="para">
The <span class="guilabel"><strong>Resources</strong></span> tab of the <span class="application"><strong>System Monitor</strong></span> application.
</div></div></div></div><h6>Figure 16.3. System Monitor — Resources</h6></div><br class="figure-break" /><div class="para">
In the <span class="guilabel"><strong>CPU History</strong></span> section, the <span class="application"><strong>System Monitor</strong></span> tool displays a graphical representation of the CPU usage history and shows the percentage of how much CPU is currently in use.
- </div></div></div><div class="section" id="s1-sysinfo-filesystems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.4. Viewing Block Devices and File Systems</h2></div></div></div><a id="idm225460981104" class="indexterm"></a><a id="idm225460979664" class="indexterm"></a><div class="section" id="s2-sysinfo-filesystems-lsblk"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.1. Using the lsblk Command</h3></div></div></div><a id="idm225424035984" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s1-sysinfo-filesystems"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.4. Viewing Block Devices and File Systems</h2></div></div></div><a id="idm261692108720" class="indexterm"></a><a id="idm261692107280" class="indexterm"></a><div class="section" id="s2-sysinfo-filesystems-lsblk"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.1. Using the lsblk Command</h3></div></div></div><a id="idm261740281120" class="indexterm"></a><div class="para">
The <code class="command">lsblk</code> command allows you to display a list of available block devices. To do so, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">lsblk</code></pre><div class="para">
For each listed block device, the <code class="command">lsblk</code> command displays the device name (<code class="computeroutput">NAME</code>), major and minor device number (<code class="computeroutput">MAJ:MIN</code>), if the device is removable (<code class="computeroutput">RM</code>), what is its size (<code class="computeroutput">SIZE</code>), if the device is read-only (<code class="computeroutput">RO</code>), what type is it (<code class="computeroutput">TYPE</code>), and where the device is mounted (<code class="computeroutput">MOUNTPOINT</code>). For example:
@@ -7817,7 +8071,7 @@ vda2 252:2 0 19.5G 0 part
vg_fedora-lv_swap (dm-0) 253:0 0 1.5G 0 lvm [SWAP]
vg_fedora-lv_root (dm-1) 253:1 0 18G 0 lvm /</pre><div class="para">
For a complete list of available command line options, refer to the <span class="bold bold"><strong>lsblk</strong></span>(8) manual page.
- </div></div><div class="section" id="s2-sysinfo-filesystems-blkid"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.2. Using the blkid Command</h3></div></div></div><a id="idm225439857776" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-sysinfo-filesystems-blkid"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.2. Using the blkid Command</h3></div></div></div><a id="idm261724822912" class="indexterm"></a><div class="para">
The <code class="command">blkid</code> command allows you to display information about available block devices. To do so, type the following at a shell prompt as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">blkid</code></pre><div class="para">
For each listed block device, the <code class="command">blkid</code> command displays available attributes such as its <em class="firstterm">universally unique identifier</em> (<code class="computeroutput">UUID</code>), file system type (<code class="computeroutput">TYPE</code>), or volume label (<code class="computeroutput">LABEL</code>). For example:
@@ -7848,7 +8102,7 @@ ID_PART_ENTRY_OFFSET=2048
ID_PART_ENTRY_SIZE=1024000
ID_PART_ENTRY_DISK=252:0</pre><div class="para">
For a complete list of available command line options, refer to the <span class="bold bold"><strong>blkid</strong></span>(8) manual page.
- </div></div><div class="section" id="s2-sysinfo-filesystems-partx"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.3. Using the partx Command</h3></div></div></div><a id="idm225477424880" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-sysinfo-filesystems-partx"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.3. Using the partx Command</h3></div></div></div><a id="idm261761609312" class="indexterm"></a><div class="para">
The <code class="command">partx</code> command allows you to display a list of disk partitions. To list the partition table of a particular disk, as <code class="systemitem">root</code>, run this command with the <code class="option">-s</code> option followed by the device name:
</div><pre class="synopsis"><code class="command">partx</code> <code class="option">-s</code> <em class="replaceable"><code>device_name</code></em></pre><div class="para">
For example, to list partitions on <code class="filename">/dev/vda</code>, type:
@@ -7857,7 +8111,7 @@ NR START END SECTORS SIZE NAME UUID
1 2048 1026047 1024000 500M
2 1026048 41943039 40916992 19.5G</pre><div class="para">
For a complete list of available command line options, refer to the <span class="bold bold"><strong>partx</strong></span>(8) manual page.
- </div></div><div class="section" id="s2-sysinfo-filesystems-findmnt"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.4. Using the findmnt Command</h3></div></div></div><a id="idm225455967776" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-sysinfo-filesystems-findmnt"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.4. Using the findmnt Command</h3></div></div></div><a id="idm261692103136" class="indexterm"></a><div class="para">
The <code class="command">findmnt</code> command allows you to display a list of currently mounted file systems. To do so, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">findmnt</code></pre><div class="para">
For each listed file system, the <code class="command">findmnt</code> command displays the target mount point (<code class="computeroutput">TARGET</code>), source device (<code class="computeroutput">SOURCE</code>), file system type (<code class="computeroutput">FSTYPE</code>), and relevant mount options (<code class="computeroutput">OPTIONS</code>). For example:
@@ -7909,7 +8163,7 @@ TARGET SOURCE FSTYPE OPTIONS
/ /dev/mapper/vg_fedora-lv_root ext4 rw,relatime,seclabel,data=ordered
/boot /dev/vda1 ext4 rw,relatime,seclabel,data=ordered</pre><div class="para">
For a complete list of available command line options, refer to the <span class="bold bold"><strong>findmnt</strong></span>(8) manual page.
- </div></div><div class="section" id="s2-sysinfo-filesystems-df"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.5. Using the df Command</h3></div></div></div><a id="idm225477848304" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-sysinfo-filesystems-df"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.5. Using the df Command</h3></div></div></div><a id="idm261788141216" class="indexterm"></a><div class="para">
The <code class="command">df</code> command allows you to display a detailed report on the system's disk space usage. To do so, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">df</code></pre><div class="para">
For each listed file system, the <code class="command">df</code> command displays its name (<code class="computeroutput">Filesystem</code>), size (<code class="computeroutput">1K-blocks</code> or <code class="computeroutput">Size</code>), how much space is used (<code class="computeroutput">Used</code>), how much space is still available (<code class="computeroutput">Available</code>), the percentage of space usage (<code class="computeroutput">Use%</code>), and where is the file system mounted (<code class="computeroutput">Mounted on</code>). For example:
@@ -7935,11 +8189,11 @@ tmpfs 373M 3.0M 370M 1% /run
/dev/mapper/vg_fedora-lv_root 19G 4.4G 14G 25% /
tmpfs 373M 0 373M 0% /sys/fs/cgroup
tmpfs 373M 0 373M 0% /media
-/dev/vda1 497M 84M 389M 18% /boot</pre><a id="idm225442731552" class="indexterm"></a><a id="idm225442729472" class="indexterm"></a><a id="idm225442728352" class="indexterm"></a><a id="idm225452076592" class="indexterm"></a><a id="idm225452075472" class="indexterm"></a><a id="idm225504747872" class="indexterm"></a><div class="para">
+/dev/vda1 497M 84M 389M 18% /boot</pre><a id="idm261744404608" class="indexterm"></a><a id="idm261744402528" class="indexterm"></a><a id="idm261744401408" class="indexterm"></a><a id="idm261711876000" class="indexterm"></a><a id="idm261711874880" class="indexterm"></a><a id="idm261746299552" class="indexterm"></a><div class="para">
Note that the <code class="filename">/dev/shm</code> entry represents the system's virtual memory file system, <code class="filename">/sys/fs/cgroup</code> is a cgroup file system, and <code class="filename">/run</code> contains information about the running system.
</div><div class="para">
For a complete list of available command line options, refer to the <span class="bold bold"><strong>df</strong></span>(1) manual page.
- </div></div><div class="section" id="s2-sysinfo-filesystems-du"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.6. Using the du Command</h3></div></div></div><a id="idm225478265296" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-sysinfo-filesystems-du"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.6. Using the du Command</h3></div></div></div><a id="idm261735514624" class="indexterm"></a><div class="para">
The <code class="command">du</code> command allows you to displays the amount of space that is being used by files in a directory. To display the disk usage for each of the subdirectories in the current working directory, run the command with no additional command line options:
</div><pre class="synopsis"><code class="command">du</code></pre><div class="para">
For example:
@@ -7966,7 +8220,7 @@ tmpfs 373M 0 373M 0% /media
</div><pre class="screen">~]$ <code class="command">du -sh</code>
68M .</pre><div class="para">
For a complete list of available command line options, refer to the <span class="bold bold"><strong>du</strong></span>(1) manual page.
- </div></div><div class="section" id="s2-sysinfo-filesystems-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.7. Using the System Monitor Tool</h3></div></div></div><a id="idm225446711520" class="indexterm"></a><a id="idm225446710400" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-sysinfo-filesystems-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.7. Using the System Monitor Tool</h3></div></div></div><a id="idm261724813424" class="indexterm"></a><a id="idm261724812304" class="indexterm"></a><div class="para">
The <span class="guilabel"><strong>File Systems</strong></span> tab of the <span class="application"><strong>System Monitor</strong></span> tool allows you to view file systems and disk space usage in the graphical user interface.
</div><div class="para">
To start the <span class="application"><strong>System Monitor</strong></span> tool, either select <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Monitor</strong></span> from the <span class="guimenu"><strong>Activities</strong></span> menu, or type <code class="command">gnome-system-monitor</code> at a shell prompt. Then click the <span class="guilabel"><strong>File Systems</strong></span> tab to view a list of file systems.
@@ -7974,7 +8228,7 @@ tmpfs 373M 0 373M 0% /media
The <span class="guilabel"><strong>File Systems</strong></span> tab of the <span class="application"><strong>System Monitor</strong></span> application.
</div></div></div></div><h6>Figure 16.4. System Monitor — File Systems</h6></div><br class="figure-break" /><div class="para">
For each listed file system, the <span class="application"><strong>System Monitor</strong></span> tool displays the source device (<span class="guilabel"><strong>Device</strong></span>), target mount point (<span class="guilabel"><strong>Directory</strong></span>), and file system type (<span class="guilabel"><strong>Type</strong></span>), as well as its size (<span class="guilabel"><strong>Total</strong></span>) and how much space is free (<span class="guilabel"><strong>Free</strong></span>), available (<span class="guilabel"><strong>Available</strong></span>), and used (<span class="guilabel"><strong>Used</strong></span>).
- </div></div></div><div class="section" id="s1-sysinfo-hardware"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.5. Viewing Hardware Information</h2></div></div></div><a id="idm225469274272" class="indexterm"></a><a id="idm225474677200" class="indexterm"></a><div class="section" id="s2-sysinfo-hardware-lspci"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.1. Using the lspci Command</h3></div></div></div><a id="idm225474674688" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s1-sysinfo-hardware"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.5. Viewing Hardware Information</h2></div></div></div><a id="idm261788120864" class="indexterm"></a><a id="idm261725861072" class="indexterm"></a><div class="section" id="s2-sysinfo-hardware-lspci"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.1. Using the lspci Command</h3></div></div></div><a id="idm261725858672" class="indexterm"></a><div class="para">
The <code class="command">lspci</code> command lists all PCI devices that are present in the system:
</div><pre class="synopsis"><code class="command">lspci</code></pre><div class="para">
For example:
@@ -8006,7 +8260,7 @@ tmpfs 373M 0 373M 0% /media
<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em></pre><div class="para">
For a complete list of available command line options, refer to the <span class="bold bold"><strong>lspci</strong></span>(8) manual page.
- </div></div><div class="section" id="s2-sysinfo-hardware-lsusb"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.2. Using the lsusb Command</h3></div></div></div><a id="idm225374399120" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-sysinfo-hardware-lsusb"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.2. Using the lsusb Command</h3></div></div></div><a id="idm261777449056" class="indexterm"></a><div class="para">
The <code class="command">lsusb</code> command allows you to display information about USB buses and devices that are attached to them. To list all USB devices that are in the system, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">lsusb</code></pre><div class="para">
This displays a simple list of devices, for example:
@@ -8044,7 +8298,7 @@ Device Descriptor:
bDescriptorType 2
<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em></pre><div class="para">
For a complete list of available command line options, refer to the <span class="bold bold"><strong>lsusb</strong></span>(8) manual page.
- </div></div><div class="section" id="s2-sysinfo-hardware-lspcmcia"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.3. Using the lspcmcia Command</h3></div></div></div><a id="idm225462546640" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-sysinfo-hardware-lspcmcia"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.3. Using the lspcmcia Command</h3></div></div></div><a id="idm261727600064" class="indexterm"></a><div class="para">
The <code class="command">lspcmcia</code> command allows you to list all PCMCIA devices that are present in the system. To do so, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">lspcmcia</code></pre><div class="para">
For example:
@@ -8057,7 +8311,7 @@ Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:15:00.0)</pre><div
Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:15:00.0)
Configuration: state: on ready: unknown</pre><div class="para">
For a complete list of available command line options, refer to the <span class="bold bold"><strong>pccardctl</strong></span>(8) manual page.
- </div></div><div class="section" id="s2-sysinfo-hardware-lscpu"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.4. Using the lscpu Command</h3></div></div></div><a id="idm225457670320" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-sysinfo-hardware-lscpu"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.4. Using the lscpu Command</h3></div></div></div><a id="idm261724742768" class="indexterm"></a><div class="para">
The <code class="command">lscpu</code> command allows you to list information about CPUs that are present in the system, including the number of CPUs, their architecture, vendor, family, model, CPU caches, etc. To do so, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">lscpu</code></pre><div class="para">
For example:
@@ -8541,312 +8795,329 @@ NET-SNMP-MIB::netSnmpPlaypen.1.1 = INTEGER: 8675309</pre></div></div></div><div
<span class="bold bold"><strong>snmpd</strong></span>(8) — The manual page for the <code class="systemitem">snmpd</code> service.
</div></li><li class="listitem"><div class="para">
<span class="bold bold"><strong>snmpd.conf</strong></span>(5) — The manual page for the <code class="filename">/etc/snmp/snmpd.conf</code> file containing full documentation of available configuration directives.
- </div></li></ul></div></div></div></div><div xml:lang="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 class="toc"><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 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="idm225461398480" class="indexterm"></a><a id="idm225481277504" 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></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 class="toc"><dt><span class="section"><a href="#s1-logfiles-locating">17.1. Locating Log Files</a></span></dt><dt><span class="section"><a href="#s1-basic_configuration_of_rsyslog">17.2. Basic Configuration of Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Filters">17.2.1. Filters</a></span></dt><dt><span class="section"><a href="#s2-Actions">17.2.2. Actions</a></span></dt><dt><span class="section"><a href="#s2-Templates">17.2.3. Templates</a></span></dt><dt><span class="section"><a href="#s2-global_directives">17.2.4. Global Directives</a></span></dt><dt><span class="section"><a href="#s2-log_rotation">17.2.5. Log Rotation</a></span></dt><dt><span class="section"><a href="#s2-using_
the_new_configuration_format">17.2.6. Using the New Configuration Format</a></span></dt><dt><span class="section"><a href="#s2-Rulesets">17.2.7. Rulesets</a></span></dt><dt><span class="section"><a href="#s2-compatibility_with_syslogd">17.2.8. Compatibility with syslogd</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-working_with_queues_in_rsyslog">17.3. Working with Queues in Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-defining_queues">17.3.1. Defining Queues</a></span></dt><dt><span class="section"><a href="#s2-managing_queues">17.3.2. Managing Queues</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-using_rsyslog_modules">17.4. Using Rsyslog Modules</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-importing_text_files">17.4.1. Importing Text Files</a></span></dt><dt><span class="section"><a href="#s2-exporting_messages_to_a_database">17.4.2. Exporting Messages to a Database</a></span></dt><dt><span class
="section"><a href="#s2-enabling_encrypted_transport">17.4.3. Enabling Encrypted Transport</a></span></dt><dt><span class="section"><a href="#s2-using_RELP">17.4.4. Using RELP</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-interaction_of_rsyslog_and_journal">17.5. Interaction of Rsyslog and Journal</a></span></dt><dt><span class="section"><a href="#s1-structured_logging_with_rsyslog">17.6. Structured Logging with Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-importing_data_from_journal">17.6.1. Importing Data from Journal</a></span></dt><dt><span class="section"><a href="#s2-filtering_structured_messages">17.6.2. Filtering Structured Messages</a></span></dt><dt><span class="section"><a href="#s2-parsing_JSON">17.6.3. Parsing JSON</a></span></dt><dt><span class="section"><a href="#s2-storing_messages_in_the_mongodb">17.6.4. Storing Messages in the MongoDB</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-debugging_rsyslog
">17.7. Debugging Rsyslog</a></span></dt><dt><span class="section"><a href="#s1-Using_the_Journal">17.8. Using the Journal</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-Viewing_Log_Files">17.8.1. Viewing Log Files</a></span></dt><dt><span class="section"><a href="#s2-Access_Control">17.8.2. Access Control</a></span></dt><dt><span class="section"><a href="#s2-Using_The_Live_View">17.8.3. Using The Live View</a></span></dt><dt><span class="section"><a href="#s2-Filtering_Messages">17.8.4. Filtering Messages</a></span></dt><dt><span class="section"><a href="#s2-Enabling_Persistent_Storage">17.8.5. Enabling Persistent Storage</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-managing_log_files_in_a_graphical_environment">17.9. Managing Log Files in a Graphical Environment</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-logfiles-viewing">17.9.1. Viewing Log Files</a></span></dt><dt><span class="section"><a href="#s2-logfiles-adding">17.
9.2. Adding a Log File</a></span></dt><dt><span class="section"><a href="#s2-logfiles-examining">17.9.3. Monitoring Log Files</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-log-files-additional-resources">17.10. Additional Resources</a></span></dt></dl></div><a id="idm261758397936" class="indexterm"></a><a id="idm261757577632" class="indexterm"></a><div class="para">
+ <em class="firstterm">Log files</em> are files that contain messages about the system, including the kernel, services, and applications running on it. There are several types of log files for storing various information. For example, there is a default system log file, a log file just for security messages, and a log file for cron tasks. Log files can be very useful in many situations, for instance to troubleshoot a problem with the system, when trying to load a kernel driver, or when looking for unauthorized login attempts to the system.
+ </div><a id="idm261719793216" class="indexterm"></a><a id="idm261746541792" class="indexterm"></a><div class="para">
+ Some log files are controlled by a daemon called <code class="systemitem">rsyslogd</code>. The <code class="systemitem">rsyslogd</code> daemon is an enhanced replacement for <span class="application"><strong>syslogd</strong></span>, and provides extended filtering, various configuration options, input and output modules, support for transportation via the <code class="systemitem">TCP</code> or <code class="systemitem">UDP</code> protocols. A list of log files maintained by <code class="systemitem">rsyslogd</code> can be found in the <code class="filename">/etc/rsyslog.conf</code> configuration file. Most log files are located in the <code class="filename">/var/log/</code> directory.
</div><div class="para">
- Log files can 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="idm225401448768" class="indexterm"></a><a id="idm225433149136" 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.
+ Log files can also be managed by the <code class="systemitem">journald</code> daemon – a component of <code class="systemitem">systemd</code>. The <code class="systemitem">journald</code> daemon captures Syslog messages, kernel log messages, initial RAM disk and early boot messages as well as messages written to standard output and standard error output of all services, indexes them and makes this available to the user. The native journal file format, which is a structured and indexed binary file, improves searching and provides faster operation, and it also stores meta data information like time stamps or user IDs. Log files produced by <code class="systemitem">journald</code> are by default not persistent, log files are stored only in memory or a small ring-buffer in the <code class="filename">/run/log/journal/</code> directory. The amount of logged data depends on free memory, when you reach the capacity limit, the oldest entries are deleted. However, this setting can
be altered – see <a class="xref" href="#s2-Enabling_Persistent_Storage">Section 17.8.5, “Enabling Persistent Storage”</a>. For more information on Journal see <a class="xref" href="#s1-Using_the_Journal">Section 17.8, “Using the Journal”</a>.
</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">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">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
+ By default, these two logging tools coexist on your system. The <code class="systemitem">journald</code> daemon is the primary tool for troubleshooting. It also provides additional data necessary for creating structured log messages. Data acquired by <code class="systemitem">journald</code> is forwarded into the <code class="systemitem">/run/systemd/journal/syslog</code> socket that may be used by <code class="systemitem">rsyslogd</code> to process the data further. However, <span class="application"><strong>rsyslog</strong></span> does the actual integration by default via the <code class="systemitem">imjournal</code> input module, thus avoiding the aforementioned socket. You can also transfer data in the opposite direction, from <code class="systemitem">rsyslogd</code> to <code class="systemitem">journald</code> with use of <code class="systemitem">omjournal</code> module. See <a class="xref" href="#s1-interaction_of_rsyslog_and_journal">Section 17.5, “Interaction of
Rsyslog and Journal”</a> for further information. The integration enables maintaining text-based logs in a consistent format to ensure compatibility with possible applications or configurations dependent on <code class="systemitem">rsyslogd</code>. Also, you can maintain rsyslog messages in a structured format (see <a class="xref" href="#s1-structured_logging_with_rsyslog">Section 17.6, “Structured Logging with Rsyslog”</a>).
+ </div><div class="section" id="s1-logfiles-locating"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.1. Locating Log Files</h2></div></div></div><a id="idm261714598560" 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="idm261782052720" class="indexterm"></a><a id="idm261742998224" class="indexterm"></a><div class="para">
+ You may notice multiple files in the <code class="filename">/var/log/</code> directory with numbers after them (for example, <code class="filename">cron-20100906</code>). These numbers represent a time stamp that has been added to a rotated log file. Log files are rotated so their file sizes do not become too large. The <code class="filename">logrotate</code> package contains a cron task that automatically rotates log files according to the <code class="filename">/etc/logrotate.conf</code> configuration file and the configuration files in the <code class="filename">/etc/logrotate.d/</code> directory.
+ </div></div><div class="section" id="s1-basic_configuration_of_rsyslog"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.2. Basic Configuration of Rsyslog</h2></div></div></div><div class="para">
+ The main configuration file for <span class="application"><strong>rsyslog</strong></span> is <code class="filename">/etc/rsyslog.conf</code>. Here, you can specify <em class="firstterm">global directives</em>, <em class="firstterm">modules</em>, and <em class="firstterm">rules</em> that consist of <em class="firstterm">filter</em> and <em class="firstterm">action</em> parts. Also, you can add comments in the form of text following a hash sign (<code class="literal">#</code>).
+ </div><div class="section" id="s2-Filters"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.1. Filters</h3></div></div></div><div class="para">
+ A rule is specified by a <span class="emphasis"><em>filter</em></span> part, which selects a subset of syslog messages, and an <span class="emphasis"><em>action</em></span> part, which specifies what to do with the selected messages. To define a rule in your <code class="filename">/etc/rsyslog.conf</code> configuration file, define both, a filter and an action, on one line and separate them with one or more spaces or tabs.
+ </div><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> offers various ways to filter syslog messages according to selected properties. The available filtering methods can be divided into <span class="emphasis"><em>Facility/Priority-based</em></span>, <span class="emphasis"><em>Property-based</em></span>, and <span class="emphasis"><em>Expression-based</em></span> filters.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">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> separated by a dot. To create a selector, use the following syntax:
+ </div><pre class="screen">
+<em class="replaceable"><code>FACILITY</code></em>.<em class="replaceable"><code>PRIORITY</code></em>
</pre><div class="para">
- 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/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">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>
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="replaceable"><code>FACILITY</code></em> specifies the subsystem that produces a specific syslog message. For example, the <code class="command">mail</code> subsystem handles all mail-related syslog messages. <em class="replaceable"><code>FACILITY</code></em> can be represented by one of the following keywords (or by a numerical code): <code class="command">kern</code> (0), <code class="command">user</code> (1), <code class="command">mail</code> (2), <code class="command">daemon</code> (3), <code class="command">auth</code> (4), <code class="command">syslog</code> (5), <code class="command">lpr</code> (6), <code class="command">news</code> (7), <code class="command">uucp</code> (8), <code class="command">cron</code> (9), <code class="command">authpriv</code> (10), <code class="command">ftp</code> (11), <code class="command">ntp</code> (12), <code class="command">logaudit</code> (13), <code class="command">logalert</code> (14), <code class="command">clock</
code> (15), and <code class="command">local0</code> through <code class="command">local7</code> (16 - 23).
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code>PRIORITY</code></em> specifies a priority of a syslog message. <em class="replaceable"><code>PRIORITY</code></em> can be represented by one of the following keywords (or by a number): <code class="command">debug</code> (7), <code class="command">info</code> (6), <code class="command">notice</code> (5), <code class="command">warning</code> (4), <code class="command">err</code> (3), <code class="command">crit</code> (2), <code class="command">alert</code> (1), and <code class="command">emerg</code> (0).
+ </div><div class="para">
+ The aforementioned syntax selects syslog messages with the defined or <span class="emphasis"><em>higher</em></span> priority. By preceding any priority keyword with an equal sign (<code class="literal">=</code>), you specify that only syslog messages with the specified priority will be selected. All other priorities will be ignored. Conversely, preceding a priority keyword with an exclamation mark (<code class="literal">!</code>) selects all syslog messages except those with the defined priority.
+ </div></li></ul></div><div class="para">
+ In addition to the keywords specified above, you may also use an asterisk (<code class="literal">*</code>) to define all facilities or priorities (depending on where you place the asterisk, before or after the comma). Specifying the priority keyword <code class="literal">none</code> serves for facilities with no given priorities. Both facility and priority conditions are case-insensitive.
+ </div><div class="para">
+ To define multiple facilities and priorities, separate them with a comma (<code class="literal">,</code>). To define multiple selectors on one line, separate them with a semi-colon (<code class="literal">;</code>). Note that each selector in the selector field is capable of overwriting the preceding ones, which can exclude some priorities from the pattern.
+ </div><div class="example" id="ex-facility_priority-based_filters"><h6>Example 17.1. Facility/Priority-based Filters</h6><div class="example-contents"><div class="para">
+ The following are a few examples of simple facility/priority-based filters that can be specified in <code class="filename">/etc/rsyslog.conf</code>. To select all kernel syslog messages with any priority, add the following text into the configuration file:
+ </div><pre class="screen">
+kern.*
</pre><div class="para">
- 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
+ To select all mail syslog messages with priority <code class="command">crit</code> and higher, use this form:
+ </div><pre class="screen">
+mail.crit
</pre><div class="para">
- <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/">http://www.rsyslog.com/doc/rsyslog_conf_modules.html</a>
- </div><div class="warning"><div class="admonition_header"><h2>Make sure you use trustworthy modules only</h2></div><div class="admonition"><div class="para">
- Note that when <span class="application"><strong>rsyslog</strong></span> loads any modules, it provides them with access to some of its functions and data. This poses a possible security threat. To minimize security risks, use trustworthy modules only.
- </div></div></div></div><div class="section" id="s2-rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">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">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 class="variablelist"><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:
+ To select all cron syslog messages except those with the <code class="command">info</code> or <code class="command">debug</code> priority, set the configuration in the following form:
+ </div><pre class="screen">
+cron.!info,!debug
+</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">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, see <a class="xref" href="#brid-properties">the section called “Properties”</a>. You can compare each of the specified properties to a particular value using one of the compare-operations listed in <a class="xref" href="#table-compare-operations">Table 17.1, “Property-based compare-operations”</a>. Both property names and compare operations are case-sensitive.
+ </div><div class="para">
+ Property-based filter must start with a colon (<code class="literal">:</code>). To define the filter, use the following syntax:
+ </div><pre class="screen">:<em class="replaceable"><code>PROPERTY</code></em>, [!]<em class="replaceable"><code>COMPARE_OPERATION</code></em>, "<em class="replaceable"><code>STRING</code></em>"</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>PROPERTY</code></em> attribute specifies the desired property.
+ </div></li><li class="listitem"><div class="para">
+ The optional exclamation point (<code class="literal">!</code>) negates the output of the compare-operation. Other Boolean operators are currently not supported in property-based filters.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>COMPARE_OPERATION</code></em> attribute specifies one of the compare-operations listed in <a class="xref" href="#table-compare-operations">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. This value must be enclosed in quotation marks. To escape certain character inside the string (for example a quotation mark (<code class="literal">"</code>)), use the backslash character (<code class="literal">\</code>).
+ </div></li></ul></div><div class="table" id="table-compare-operations"><h6>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 class="">
+ Compare-operation
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <em class="parameter"><code>contains</code></em>
+ </td><td class="">
+ Checks whether the provided string matches any part of the text provided by the property. To perform case-insensitive comparisons, use <em class="parameter"><code>contains_i</code></em>.
+ </td></tr><tr><td class="">
+ <em class="parameter"><code>isequal</code></em>
+ </td><td class="">
+ Compares the provided string against all of the text provided by the property. These two values must be exactly equal to match.
+ </td></tr><tr><td class="">
+ <em class="parameter"><code>startswith</code></em>
+ </td><td class="">
+ Checks whether the provided string is found exactly at the beginning of the text provided by the property. To perform case-insensitive comparisons, use <em class="parameter"><code>startswith_i</code></em>.
+ </td></tr><tr><td class="">
+ <em class="parameter"><code>regex</code></em>
+ </td><td class="">
+ Compares the provided POSIX BRE (Basic Regular Expression) against the text provided by the property.
+ </td></tr><tr><td class="">
+ <em class="parameter"><code>ereregex</code></em>
+ </td><td class="">
+ Compares the provided POSIX ERE (Extended Regular Expression) regular expression against the text provided by the property.
+ </td></tr><tr><td class="">
+ <em class="parameter"><code>isempty</code></em>
+ </td><td class="">
+ Checks if the property is empty. The value is discarded. This is especially useful when working with normalized data, where some fields may be populated based on normalization result.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="ex-property-based_filters"><h6>Example 17.2. Property-based Filters</h6><div class="example-contents"><div class="para">
+ The following are a few examples of property-based filters that can be specified in <code class="filename">/etc/rsyslog.conf</code>. To select syslog messages which contain the string <code class="literal">error</code> in their message text, use:
+ </div><pre class="screen">:msg, contains, "error"</pre><div class="para">
+ The following filter selects syslog messages received from the host name <code class="literal">host1</code>:
+ </div><pre class="screen">:hostname, isequal, "host1"</pre><div class="para">
+ To select syslog messages which do not contain any mention of the words <code class="literal">fatal</code> and <code class="literal">error</code> with any or no text between them (for example, <code class="literal">fatal lib error</code>), type:
+ </div><pre class="screen">:msg, !regex, "fatal .* error"</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">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 called <span class="emphasis"><em>RainerScript</em></span> to build complex filters. See <a class="xref" href="#brid-Log_Files-Resources-Online">the section called “Online Documentation”</a> for the syntax definition of this script along with examples of various expression-based filters. Also RainerScript is a basis for <span class="application"><strong>rsyslog</strong></span>'s new configuration format, see <a class="xref" href="#s2-using_the_new_configuration_format">Section 17.2.6, “Using the New Configuration Format”</a>
+ </div><div class="para">
+ The basic syntax of expression-based filter looks as follows:
+ </div><pre class="screen">
+if <em class="replaceable"><code>EXPRESSION</code></em> then <em class="replaceable"><code>ACTION</code></em> else <em class="replaceable"><code>ACTION</code></em>
+</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>EXPRESSION</code></em> attribute represents an expression to be evaluated, for example: <code class="literal">$msg startswith 'DEVNAME'</code> or <code class="literal">$syslogfacility-text == 'local0'</code>. You can specify more than one expression in a single filter by using <code class="function">and</code> and <code class="function">or</code> operators.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>action</code></em> attribute represents an action to be performed if the expression returns the value <code class="literal">true</code>. this can be a single action, or an arbitrary complex script enclosed in curly braces.
+ </div></li><li class="listitem"><div class="para">
+ Expression-based filters are indicated by the keyword <span class="emphasis"><em>if</em></span> at the start of a new line. the <span class="emphasis"><em>then</em></span> keyword separates the <em class="replaceable"><code>expression</code></em> from the <em class="replaceable"><code>action</code></em>. optionally, you can employ the <span class="emphasis"><em>else</em></span> keyword to specify what action is to be performed in case the condition is not met.
+ </div></li></ul></div><div class="para">
+ With expression-based filters, you can nest the conditions by using a script enclosed in curly braces as in <a class="xref" href="#ex-expression-based_filters">Example 17.3, “Expression-based Filters”</a>. the script allows you to use <span class="emphasis"><em>facility/priority-based</em></span> filters inside the expression. on the other hand, <span class="emphasis"><em>property-based</em></span> filters are not recommended here. RainerScript supports regular expressions with specialized functions <code class="function">re_match()</code> and <code class="function">re_extract()</code>.
+ </div><div class="example" id="ex-expression-based_filters"><h6>Example 17.3. Expression-based Filters</h6><div class="example-contents"><div class="para">
+ The following expression contains two nested conditions. The log files created by a program called <span class="emphasis"><em>prog1</em></span> are split into two files based on the presence of the "test" string in the message.
</div><pre class="screen">
-<em class="replaceable"><code><FACILITY></code></em>.<em class="replaceable"><code><PRIORITY></code></em>
+if $programname == 'prog1' then {
+ action(type="omfile" file="/var/log/prog1.log")
+ if $msg contains 'test' then
+ action(type="omfile" file="/var/log/prog1test.log")
+ else
+ action(type="omfile" file="/var/log/prog1notest.log")
+}
+</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="s2-Actions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.2. Actions</h3></div></div></div><div class="para">
+ Actions specify what is to be done with the messages filtered out by an already-defined selector. The following are some of the actions you can define in your rule:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">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:
+ </div><pre class="synopsis"><em class="replaceable"><code>FILTER</code></em> <em class="replaceable"><code>PATH</code></em></pre><div class="para">
+ where <em class="replaceable"><code>FILTER</code></em> stands for user-specified selector and <em class="replaceable"><code>PATH</code></em> is a path of a target file.
+ </div><div class="para">
+ For instance, the following rule is comprised of a selector that selects all <span class="application"><strong>cron</strong></span> syslog messages and an action that saves them into the <code class="filename">/var/log/cron.log</code> log file:
+ </div><pre class="synopsis">cron.* /var/log/cron.log</pre><div class="para">
+ By default, the log file is synchronized every time a syslog message is generated. Use a dash mark (<code class="literal">-</code>) as a prefix of the file path you specified to omit syncing:
+ </div><pre class="synopsis"><em class="replaceable"><code>FILTER</code></em> -<em class="replaceable"><code>PATH</code></em></pre><div class="para">
+ Note that you might lose information if the system terminates right after a write attempt. However, this setting can improve performance, especially if you run programs that produce very verbose log messages.
+ </div><div class="para">
+ Your specified file path can be either <span class="emphasis"><em>static</em></span> or <span class="emphasis"><em>dynamic</em></span>. Static files are represented by a fixed file path as shown in the example above. Dynamic file paths can differ according to the received message. Dynamic file paths are represented by a template and a question mark (<code class="literal">?</code>) prefix:
+ </div><pre class="synopsis"><em class="replaceable"><code>FILTER</code></em> ?<em class="replaceable"><code>DynamicFile</code></em></pre><div class="para">
+ where <em class="replaceable"><code>DynamicFile</code></em> is a name of a predefined template that modifies output paths. You can use the dash prefix (<code class="literal">-</code>) to disable syncing, also you can use multiple templates separated by a colon (<code class="literal">;</code>). For more information on templates, see <a class="xref" href="#brid-generating-dynamic-fnames">the section called “Generating Dynamic File Names”</a>.
+ </div><div class="para">
+ If the file you specified is an existing <span class="application"><strong>terminal</strong></span> or <code class="filename">/dev/console</code> device, syslog messages are sent to standard output (using special <span class="application"><strong>terminal</strong></span>-handling) or your console (using special <code class="filename">/dev/console</code>-handling) when using the X Window System, respectively.
+ </div></dd><dt class="varlistentry"><span class="term">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 you to administer syslog messages of multiple hosts on one machine. To forward syslog messages to a remote machine, use the following syntax:
+ </div><pre class="screen">@[<span class="optional">(<code class="command">z<em class="replaceable"><code>NUMBER</code></em></code>)</span>]<em class="replaceable"><code>HOST</code></em>:[<span class="optional"><em class="replaceable"><code>PORT</code></em></span>]
</pre><div class="para">
- where:
- </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <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:
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The at sign (<code class="literal">@</code>) indicates that the syslog messages are forwarded to a host using the <code class="systemitem">UDP</code> protocol. To use the <code class="systemitem">TCP</code> protocol, use two at signs with no space between them (<code class="literal">@@</code>).
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="command">z<em class="replaceable"><code>NUMBER</code></em></code> setting enables <span class="application"><strong>zlib</strong></span> compression for syslog messages. The <em class="replaceable"><code>NUMBER</code></em> attribute specifies the level of compression (from 1 – lowest to 9 – maximum). Compression gain is automatically checked by <code class="systemitem">rsyslogd</code>, messages are compressed only if there is any compression gain and messages below 60 bytes are never compressed.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>HOST</code></em> attribute specifies the host which receives the selected syslog messages.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>PORT</code></em> attribute specifies the host machine's port.
+ </div></li></ul></div><div class="para">
+ When specifying an <code class="systemitem">IPv6</code> address as the host, enclose the address in square brackets (<code class="literal">[</code>, <code class="literal">]</code>).
+ </div><div class="example" id="ex-logging_over_the_network"><h6>Example 17.4. Sending syslog Messages over the Network</h6><div class="example-contents"><div class="para">
+ The following are some examples of actions that forward syslog messages over the network (note that all actions are preceded with a selector that selects all messages with any priority). To forward messages to <code class="systemitem">192.168.0.1</code> via the <code class="systemitem">UDP</code> protocol, type:
</div><pre class="screen">
-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 class="">
- Compare-operation
- </th><th class="">
- Description
- </th></tr></thead><tbody><tr><td class="">
- <em class="parameter"><code>contains</code></em>
- </td><td class="">
- Checks whether the provided string matches any part of the text provided by the property.
- </td></tr><tr><td class="">
- <em class="parameter"><code>isequal</code></em>
- </td><td class="">
- Compares the provided string against all of the text provided by the property.
- </td></tr><tr><td class="">
- <em class="parameter"><code>startswith</code></em>
- </td><td class="">
- Checks whether the provided string matches a prefix of the text provided by the property.
- </td></tr><tr><td class="">
- <em class="parameter"><code>regex</code></em>
- </td><td class="">
- Compares the provided POSIX BRE (Basic Regular Expression) regular expression against the text provided by the property.
- </td></tr><tr><td class="">
- <em class="parameter"><code>ereregex</code></em>
- </td><td class="">
- 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/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>
+*.* @192.168.0.1
</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">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 class="variablelist"><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
+ To forward messages to "example.com" using port 18 and the <code class="systemitem">TCP</code> protocol, use:
+ </div><pre class="screen">
+*.* @@example.com:18
</pre><div class="para">
- 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>]
+ The following compresses messages with <span class="application"><strong>zlib</strong></span> (level 9 compression) and forwards them to <code class="systemitem">2001:db8::1</code> using the <code class="systemitem">UDP</code> protocol
+ </div><pre class="screen">
+*.* @(z9)[2001:db8::1]
+</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">Output channels</span></dt><dd><div class="para">
+ Output channels are primarily used to specify the maximum size a log file can grow to. This is very useful for log file rotation (for more information see <a class="xref" href="#s2-log_rotation">Section 17.2.5, “Log Rotation”</a>). An output channel is basically a collection of information about the output action. Output channels are defined by the <code class="literal">$outchannel</code> directive. To define an output channel in <code class="filename">/etc/rsyslog.conf</code>, use the following syntax:
+ </div><pre class="screen">$outchannel <em class="replaceable"><code>NAME</code></em>, <em class="replaceable"><code>FILE_NAME</code></em>, <em class="replaceable"><code>MAX_SIZE</code></em>, <em class="replaceable"><code>ACTION</code></em></pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>NAME</code></em> attribute specifies the name of the output channel.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>FILE_NAME</code></em> attribute specifies the name of the output file. Output channels can write only into files, not pipes, terminal, or other kind of output.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>MAX_SIZE</code></em> attribute represents the maximum size the specified file (in <em class="replaceable"><code>FILE_NAME</code></em>) can grow to. This value is specified in <span class="emphasis"><em>bytes</em></span>.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>ACTION</code></em> attribute specifies the action that is taken when the maximum size, defined in <em class="replaceable"><code>MAX_SIZE</code></em>, is hit.
+ </div></li></ul></div><div class="para">
+ To use the defined output channel as an action inside a rule, type:
+ </div><pre class="synopsis"><em class="replaceable"><code>FILTER</code></em> :omfile:$<em class="replaceable"><code>NAME</code></em></pre><div class="example" id="example-log-rotation"><h6>Example 17.5. Output channel log rotation</h6><div class="example-contents"><div class="para">
+ The following output shows a simple log rotation through the use of an output channel. First, the output channel is defined via the <em class="parameter"><code>$outchannel</code></em> directive:
+ </div><pre class="screen">
+ $outchannel log_rotation, /var/log/test_log.log, 104857600, /home/joe/log_rotation_script
</pre><div class="para">
- 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/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">
+ and then it is used in a rule that selects every syslog message with any priority and executes the previously-defined output channel on the acquired syslog messages:
+ </div><pre class="screen">
+*.* :omfile:$log_rotation
+</pre><div class="para">
+ Once the limit (in the example <code class="constant">100 MB</code>) is hit, the <code class="filename">/home/joe/log_rotation_script</code> is executed. This script can contain anything from moving the file into a different folder, editing specific content out of it, or simply removing it.
+ </div></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">Sending syslog messages to specific users</span></dt><dd><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> can send syslog messages to specific users by specifying a user name of the user you want to send the messages to (as in <a class="xref" href="#ex-multiple_actions">Example 17.7, “Specifying Multiple Actions”</a>). To specify more than one user, separate each user name with a comma (<code class="literal">,</code>). To send messages to every user that is currently logged on, use an asterisk (<code class="literal">*</code>).
+ </div></dd><dt class="varlistentry"><span class="term">Executing a program</span></dt><dd><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> lets you execute a program for selected syslog messages and uses the <code class="systemitem">system()</code> call to execute the program in shell. To specify a program to be executed, prefix it with a caret character (<code class="literal">^</code>). Consequently, specify a template that formats the received message and passes it to the specified executable as a one line parameter (for more information on templates, see <a class="xref" href="#s2-Templates">Section 17.2.3, “Templates”</a>).
+ </div><pre class="synopsis"><em class="replaceable"><code>FILTER</code></em> ^<em class="replaceable"><code>EXECUTABLE</code></em>; <em class="replaceable"><code>TEMPLATE</code></em></pre><div class="para">
+ Here an output of the <em class="replaceable"><code>FILTER</code></em> condition is processed by a program represented by <em class="replaceable"><code>EXECUTABLE</code></em>. This program can be any valid executable. Replace <em class="replaceable"><code>TEMPLATE</code></em> with the name of the formatting template.
+ </div><div class="example" id="ex-esecuting_a_program"><h6>Example 17.6. Executing a Program</h6><div class="example-contents"><div class="para">
+ In the following example, any syslog message with any priority is selected, formatted with the <em class="parameter"><code>template</code></em> template and passed as a parameter to the <span class="application"><strong>test-program</strong></span> program, which is then executed with the provided parameter:
+ </div><pre class="screen">*.* ^test-program;template</pre></div></div><br class="example-break" /><div class="warning"><div class="admonition_header"><h2>Be careful when using the shell execute action</h2></div><div class="admonition"><div class="para">
+ When accepting messages from any host, and using the shell execute action, you may be vulnerable to command injection. An attacker may try to inject and execute commands in the program you specified to be executed in your action. To avoid any possible security threats, thoroughly consider the use of the shell execute action.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Storing syslog messages in a database</span></dt><dd><div class="para">
+ Selected syslog messages can be directly written into a database table using the <span class="emphasis"><em>database writer</em></span> action. The database writer uses the following syntax:
+ </div><pre class="screen">:<em class="replaceable"><code>PLUGIN</code></em>:<em class="replaceable"><code>DB_HOST</code></em>,<em class="replaceable"><code>DB_NAME</code></em>,<em class="replaceable"><code>DB_USER</code></em>,<em class="replaceable"><code>DB_PASSWORD</code></em>;[<span class="optional"><em class="replaceable"><code>TEMPLATE</code></em></span>]</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>PLUGIN</code></em> calls the specified plug-in that handles the database writing (for example, the <code class="systemitem">ommysql</code> plug-in).
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>DB_HOST</code></em> attribute specifies the database host name.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>DB_NAME</code></em> attribute specifies the name of the database.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>DB_USER</code></em> attribute specifies the database user.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>DB_PASSWORD</code></em> attribute specifies the password used with the aforementioned database user.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>TEMPLATE</code></em> attribute specifies an optional use of a template that modifies the syslog message. For more information on templates, see <a class="xref" href="#s2-Templates">Section 17.2.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> and <code class="systemitem">PostgreSQL</code> databases only. In order to use the <code class="systemitem">MySQL</code> and <code class="systemitem">PostgreSQL</code> database writer functionality, install the <span class="package">rsyslog-mysql</span> and <span class="package">rsyslog-pgsql</span> packages, respectively. Also, make sure you load the appropriate modules in your <code class="filename">/etc/rsyslog.conf</code> configuration file:
+ </div><pre class="screen">
$ModLoad ommysql # 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:
+ For more information on <span class="application"><strong>rsyslog</strong></span> modules, see <a class="xref" href="#s1-using_rsyslog_modules">Section 17.4, “Using Rsyslog Modules”</a>.
+ </div><div class="para">
+ Alternatively, you may use a generic database interface provided by the <code class="systemitem">omlibdb</code> module (supports: Firebird/Interbase, MS SQL, Sybase, SQLLite, Ingres, Oracle, mSQL).
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Discarding syslog messages</span></dt><dd><div class="para">
+ To discard your selected messages, use the tilde character (<code class="literal">~</code>).
+ </div><pre class="synopsis"><em class="replaceable"><code>FILTER</code></em> ~</pre><div class="para">
+ The discard action is mostly used to filter out messages before carrying on any further processing. It can be effective if you want to omit some repeating messages that would otherwise fill the log files. The results of discard action depend on where in the configuration file it is specified, for the best results place these actions on top of the actions list. Please note that once a message has been discarded there is no way to retrieve it in later configuration file lines.
+ </div><div class="para">
+ For instance, the following rule discards any cron syslog messages:
+ </div><pre class="screen">cron.* ~</pre></dd></dl></div><h4 id="idm261777615424">Specifying Multiple Actions</h4><div class="para">
+ For each selector, you are allowed to specify multiple actions. To specify multiple actions for one selector, write each action on a separate line and precede it with an ampersand character (&):
+ </div><pre class="screen">
+<em class="replaceable"><code>FILTER</code></em> <em class="replaceable"><code>ACTION</code></em>
+& <em class="replaceable"><code>ACTION</code></em>
+& <em class="replaceable"><code>ACTION</code></em>
+</pre><div class="para">
+ Specifying multiple actions improves the overall performance of the desired outcome since the specified selector has to be evaluated only once.
+ </div><div class="example" id="ex-multiple_actions"><h6>Example 17.7. Specifying Multiple Actions</h6><div class="example-contents"><div class="para">
+ In the following example, all kernel syslog messages with the critical priority (<em class="parameter"><code>crit</code></em>) are sent to user <code class="systemitem">user1</code>, processed by the template <em class="parameter"><code>temp</code></em> and passed on to the <em class="parameter"><code>test-program</code></em> executable, and forwarded to <code class="systemitem">192.168.0.1</code> via the <code class="systemitem">UDP</code> protocol.
</div><pre class="screen">
-kern.=crit joe
+kern.=crit user1
& ^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">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.
+</pre></div></div><br class="example-break" /><div class="para">
+ Any action can be followed by a template that formats the message. To specify a template, suffix an action with a semicolon (<code class="literal">;</code>) and specify the name of the template. For more information on templates, see <a class="xref" href="#s2-Templates">Section 17.2.3, “Templates”</a>.
+ </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. In other words, template definitions should always precede rule definitions in <code class="filename">/etc/rsyslog.conf</code>.
+ </div></div></div></div><div class="section" id="s2-Templates"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.3. Templates</h3></div></div></div><div class="para">
+ Any output that is generated by <span class="application"><strong>rsyslog</strong></span> can be modified and formatted according to your needs with the use of <span class="emphasis"><em>templates</em></span>. To create a template use the following syntax in <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">$template <em class="replaceable"><code>TEMPLATE_NAME</code></em>,"<em class="replaceable"><code>text %PROPERTY% more text</code></em>", [<span class="optional"><em class="replaceable"><code>OPTION</code></em></span>]</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>$template</code></em> 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, special characters, such as <code class="literal">\n</code> for new line or <code class="literal">\r</code> for carriage return, can be used. Other characters, such as <code class="literal">%</code> or <code class="literal">"</code>, have to be escaped if you want to use those characters literally.
+ </div></li><li class="listitem"><div class="para">
+ The text specified between two percent signs (<code class="literal">%</code>) specifies a <em class="firstterm">property</em> that allows you to access specific contents of a syslog message. For more information on properties, see <a class="xref" href="#brid-properties">the section called “Properties”</a>.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="parameter"><code>OPTION</code></em> attribute specifies any options that modify the template functionality. The currently supported template options are <em class="parameter"><code>sql</code></em> and <em class="parameter"><code>stdsql</code></em>, which are used for formatting the text as an SQL query.
+ </div><div class="note"><div class="admonition_header"><h2>The sql and stdsql options</h2></div><div class="admonition"><div class="para">
+ Note that the database writer checks whether the <em class="parameter"><code>sql</code></em> or <em class="parameter"><code>stdsql</code></em> options are specified in the template. If they are not, the database writer does not perform any action. This is to prevent any possible security threats, such as SQL injection.
</div><div class="para">
- 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">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">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/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/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">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 class="variablelist"><dt class="varlistentry"><span class="term"><em class="parameter"><code>RSYSLOG_DebugFormat</code></em></span></dt><dd><pre class="screen">"Debug line with all properties:\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-co
lumn="always"><h3 class="title">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">17.2. Locating Log Files</h2></div></div></div><a id="idm225436288384" 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="idm225443053264" class="indexterm"></a><a id="idm225443051520" 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">17.2.1. Configuring logrotate</h3></div></div></div><div class="para">
+ See section <em class="citetitle">Storing syslog messages in a database</em> in <a class="xref" href="#s2-Actions">Section 17.2.2, “Actions”</a> for more information.
+ </div></div></div></li></ul></div><h4 id="brid-generating-dynamic-fnames">Generating Dynamic File Names</h4><div class="para">
+ Templates can be used to generate dynamic file names. By specifying a property as a part of the file path, a new file will be created for each unique property, which is a convenient way to classify syslog messages.
+ </div><div class="para">
+ For example, use the <em class="parameter"><code>timegenerated</code></em> property, which extracts a time stamp from the message, to generate a unique file name for each syslog message:
+ </div><pre class="screen">$template DynamicFile,"/var/log/test_logs/%timegenerated%-test.log"</pre><div class="para">
+ Keep in mind that the <em class="parameter"><code>$template</code></em> directive only specifies the template. You must use it inside a rule for it to take effect. In <code class="filename">/etc/rsyslog.conf</code>, use the question mark (<code class="literal">?</code>) in an action definition to mark the dynamic file name template:
+ </div><pre class="screen">*.* ?DynamicFile</pre><h4 id="brid-properties">Properties</h4><div class="para">
+ Properties defined inside a template (between two percent signs (<code class="literal">%</code>)) enable access various contents of a syslog message through the use of a <em class="firstterm">property replacer</em>. To define a property inside a template (between the two quotation marks (<code class="literal">"</code>…<code class="literal">"</code>)), use the following syntax:
+ </div><pre class="screen">%<em class="replaceable"><code>PROPERTY_NAME</code></em>[<span class="optional">:<em class="replaceable"><code>FROM_CHAR</code></em>:<em class="replaceable"><code>TO_CHAR</code></em>:<em class="replaceable"><code>OPTION</code></em></span>]%</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>PROPERTY_NAME</code></em> attribute specifies the name of a property. A list of all available properties and their detailed description can be found in the <code class="filename">rsyslog.conf(5)</code> manual page under the section <span class="emphasis"><em>Available Properties</em></span>.
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code>FROM_CHAR</code></em> and <em class="replaceable"><code>TO_CHAR</code></em> attributes denote a range of characters that the specified property will act upon. Alternatively, regular expressions can be used to specify a range of characters. To do so, set the letter <code class="literal">R</code> as the <em class="replaceable"><code>FROM_CHAR</code></em> attribute and specify your desired regular expression as the <em class="replaceable"><code>TO_CHAR</code></em> attribute.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>OPTION</code></em> attribute specifies any property options, such as the <code class="option">lowercase</code> option to convert the input to lowercase. A list of all available property options and their detailed description can be found in the <code class="filename">rsyslog.conf(5)</code> manual page under the section <span class="emphasis"><em>Property Options</em></span>.
+ </div></li></ul></div><div class="para">
+ The following are some examples of simple properties:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The following property obtains the whole message text of a syslog message:
+ </div><pre class="screen">%msg%</pre></li><li class="listitem"><div class="para">
+ 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 time stamp that is generated when the syslog message is received and formats it according to the <a href="http://www.rfc-editor.org/info/rfc3999"><em class="citetitle">RFC 3999</em></a> date standard.
+ </div><pre class="screen">%timegenerated:1:10:date-rfc3339%</pre></li></ul></div><h4 id="brid-template-examples">Template Examples</h4><div class="para">
+ This section presents a few examples of <span class="application"><strong>rsyslog</strong></span> templates.
+ </div><div class="para">
+ <a class="xref" href="#example-temp1">Example 17.8, “A verbose syslog message template”</a> shows a template that formats a syslog message so that it outputs the message's severity, facility, the time stamp of when the message was received, the host name, the message tag, the message text, and ends with a new line.
+ </div><div class="example" id="example-temp1"><h6>Example 17.8. 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.9, “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 host name, message tag and a time stamp, on a new line (using <code class="literal">\r</code> and <code class="literal">\n</code>) and rings the bell (using <code class="literal">\7</code>).
+ </div><div class="example" id="example-temp2"><h6>Example 17.9. 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.10, “A database formatted message template”</a> shows a template that formats a syslog message so that it can be used as a database query. Notice the use of the <em class="parameter"><code>sql</code></em> option at the end of the template specified as the template option. It tells the database writer to format the message as an MySQL <code class="systemitem">SQL</code> query.
+ </div><div class="example" id="example-temp3"><h6>Example 17.10. A database formatted message template</h6><div class="example-contents"><pre class="screen">$template dbFormat,"insert into SystemEvents (Message, Facility, FromHost, Priority, DeviceReportedTime, ReceivedAt, InfoUnitID, SysLogTag) values ('%msg%', %syslogfacility%, '%HOSTNAME%', %syslogpriority%, '%timereported:::date-mysql%', '%timegenerated:::date-mysql%', %iut%, '%syslogtag%')", sql</pre></div></div><br class="example-break" /><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> also contains a set of predefined templates identified by the <code class="literal">RSYSLOG_</code> prefix. These are reserved for the syslog's use and it is advisable to not create a template using this prefix to avoid conflicts. The following list shows these predefined templates along with their definitions.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><em class="parameter"><code>RSYSLOG_DebugFormat</code></em></span></dt><dd><div class="para">
+ A special format used for troubleshooting property problems.
+ </div><pre class="screen">"Debug line with all properties:\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><div class="para">
+ The format specified in IETF's internet-draft ietf-syslog-protocol-23, which is assumed to become the new syslog standard RFC.
+ </div><pre class="screen">"%PRI%1 %TIMESTAMP:::date-rfc3339% %HOSTNAME% %APP-NAME% %PROCID% %MSGID% %STRUCTURED-DATA% %msg%\n\"</pre></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>RSYSLOG_FileFormat</code></em></span></dt><dd><div class="para">
+ A modern-style logfile format similar to TraditionalFileFormat, but with high-precision time stamps and time zone information.
+ </div><pre class="screen">"%TIMESTAMP:::date-rfc3339% %HOSTNAME% %syslogtag%%msg:::sp-if-no-1st-sp%%msg:::drop-last-lf%\n\"</pre></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>RSYSLOG_TraditionalFileFormat</code></em></span></dt><dd><div class="para">
+ The older default log file format with low-precision time stamps.
+ </div><pre class="screen">"%TIMESTAMP% %HOSTNAME% %syslogtag%%msg:::sp-if-no-1st-sp%%msg:::drop-last-lf%\n\"</pre></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>RSYSLOG_ForwardFormat</code></em></span></dt><dd><div class="para">
+ A forwarding format with high-precision time stamps and time zone information.
+ </div><pre class="screen">"%PRI%%TIMESTAMP:::date-rfc3339% %HOSTNAME% %syslogtag:1:32%%msg:::sp-if-no-1st-sp%%msg%\"</pre></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>RSYSLOG_TraditionalForwardFormat</code></em></span></dt><dd><div class="para">
+ The traditional forwarding format with low-precision time stamps.
+ </div><pre class="screen">"%PRI%%TIMESTAMP% %HOSTNAME% %syslogtag:1:32%%msg:::sp-if-no-1st-sp%%msg%\"</pre></dd></dl></div></div><div class="section" id="s2-global_directives"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.4. Global Directives</h3></div></div></div><div class="para">
+ Global directives are configuration options that apply to the <code class="systemitem">rsyslogd</code> daemon. They usually specify a value for a specific predefined variable that affects the behavior of the <code class="systemitem">rsyslogd</code> daemon or a rule that follows. All of the global directives must start with a dollar sign (<code class="literal">$</code>). Only one directive can be specified per line. The following is an example of a global directive that specifies the maximum size of the syslog message queue:
+ </div><pre class="screen">
+$MainMsgQueueSize 50000
+</pre><div class="para">
+ The default size defined for this directive (<code class="constant">10,000</code> messages) can be overridden by specifying a different value (as shown in the example above).
+ </div><div class="para">
+ You may define multiple directives in your <code class="filename">/etc/rsyslog.conf</code> configuration file. A directive affects the behavior of all configuration options until another occurrence of that same directive is detected. Global directives can be used to configure actions, queues and for debugging. A comprehensive list of all available configuration directives can be found in <a class="xref" href="#brid-Log_Files-Resources-Online">the section called “Online Documentation”</a>. Currently, a new configuration format has been developed that replaces the $-based syntax (see <a class="xref" href="#s2-using_the_new_configuration_format">Section 17.2.6, “Using the New Configuration Format”</a>). However, classic global directives remain supported as a legacy format.
+ </div></div><div class="section" id="s2-log_rotation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.5. Log Rotation</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
@@ -8856,7 +9127,7 @@ 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
+ All of the lines in the sample configuration file define global options that apply to every log file. In our example, log files are rotated weekly, rotated log files are kept for four weeks, and all rotated log files are compressed by <span class="application"><strong>gzip</strong></span> into the <code class="literal">.gz</code> format. Any lines that begin with a hash sign (#) are comments and are not processed.
</div><div class="para">
You may define configuration options for a specific log file and place it under the global options. However, it is advisable to create a separate configuration file for any specific log file in the <code class="filename">/etc/logrotate.d/</code> directory and define any configuration options there.
</div><div class="para">
@@ -8874,7 +9145,7 @@ compress
</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:
+ <em class="parameter"><code>weekly</code></em> — Specifies the rotation of log files to be done weekly. Similar directives include:
<div class="itemizedlist"><ul><li class="listitem"><div class="para">
<em class="parameter"><code>daily</code></em>
</div></li><li class="listitem"><div class="para">
@@ -8900,112 +9171,676 @@ compress
</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.
+ <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:
+ <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.
+ <em class="parameter"><code>maillast</code></em> — Specifies that the about-to-expire log files are to be mailed, instead of the just-rotated log files. This is the default option when <em class="parameter"><code>mail</code></em> is enabled.
</div></li></ul></div></li></ul></div><div class="para">
- For the full list of directives and various configuration options, 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">17.3. Viewing Log Files</h2></div></div></div><a id="idm225477999904" 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="idm225447601664" 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 5.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="idm225446334464" class="indexterm"></a><a id="idm225422783728" 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="idm225500137472" 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">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">17.5. Monitoring Log Files</h2></div></div></div><a id="idm225437972784" class="indexterm"></a><a id="idm225437971040" 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">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">17.6.1. Installed Documentation</h3></div></div></div><a id="idm225478132224" 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/ </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">17.6.2. Useful Websites</h3></div></div></div><a id="idm225463546432" 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://wiki.rsyslog.com/index.php/Main_Page</a> — 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 class="toc"><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="#sect-Cron-Installing">18.1.1. Installing Cron and Anacron</a></span></dt><dt><span class="section"><a href="#sect-Cron-Running">18.1.2. Running the Crond Service</a></span></dt><dt><span class="section"><a href="#s2-configuring-anacron-jobs">18.1.3. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="#s2-configuring-cron-jobs">18.1.4. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-cron-access">18.1.5. Controlling Access to Cron</a></span></dt><dt><span class="section"><a href="#s2-black-white-listing-of-c
ron-jobs">18.1.6. Black and 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="#sect-At_and_Batch_Installation">18.2.1. Installing At and Batch</a></span></dt><dt><span class="section"><a href="#sect-Atd-Running">18.2.2. Running the At Service</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-configuring">18.2.3. Configuring an At Job</a></span></dt><dt><span class="section"><a href="#s2-autotasks-batch-configuring">18.2.4. Configuring a Batch Job</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-viewing">18.2.5. Viewing Pending Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-commandline-options">18.2.6. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-controlling-access">18.2.7. Controlling Access to At and Batch</a></span><
/dt></dl></dd><dt><span class="section"><a href="#s1-autotasks-additional-resources">18.3. Additional Resources</a></span></dt></dl></div><a id="idm225445585952" class="indexterm"></a><div class="para">
- Tasks, also known as <em class="firstterm">jobs</em>, can be configured to run automatically within a specified period of time, on a specified date, or when the system load average decreases below 0.8.
- </div><div class="para">
- Fedora is pre-configured to run important system tasks to keep the system updated. For example, the <span class="database">slocate</span> database used by the <code class="command">locate</code> command is updated daily. A system administrator can use automated tasks to perform periodic backups, monitor the system, run custom scripts, and so on.
- </div><div class="para">
- Fedora comes with the following automated task utilities: <code class="command">cron</code>, <code class="command">anacron</code>, <code class="command">at</code>, and <code class="command">batch</code>.
- </div><div class="para">
- Every utility is intended for scheduling a different job type: while Cron and Anacron schedule recurring jobs, At and Batch schedule one-time jobs (refer to <a class="xref" href="#s1-autotasks-cron-anacron">Section 18.1, “Cron and Anacron”</a> and <a class="xref" href="#s1-autotasks-at-batch">Section 18.2, “At and Batch”</a> respectively).
- </div><div class="para">
- Fedora supports the use of <code class="systemitem">systemd.timer</code> for executing a job at a specific time. See man <code class="filename">systemd.timer(5)</code> for more information.
- </div><div class="section" id="s1-autotasks-cron-anacron"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.1. Cron and Anacron</h2></div></div></div><a id="idm225355428192" class="indexterm"></a><a id="idm225462117504" class="indexterm"></a><div class="para">
- Both Cron and Anacron are daemons that can schedule execution of recurring tasks to a certain point in time defined by the exact time, day of the month, month, day of the week, and week.
- </div><div class="para">
- Cron jobs can run as often as every minute. However, the utility assumes that the system is running continuously and if the system is not on at the time when a job is scheduled, the job is not executed.
- </div><div class="para">
- On the other hand, Anacron remembers the scheduled jobs if the system is not running at the time when the job is scheduled. The job is then executed as soon as the system is up. However, Anacron can only run a job once a day.
- </div><div class="section" id="sect-Cron-Installing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.1. Installing Cron and Anacron</h3></div></div></div><div class="para">
- To install Cron and Anacron, you need to install the <span class="package">cronie</span> package with Cron and the <span class="package">cronie-anacron</span> package with Anacron (<span class="package">cronie-anacron</span> is a sub-package of <span class="package">cronie</span>).
+ For the full list of directives and various configuration options, see the <code class="filename">logrotate(5)</code> manual page.
+ </div></div><div class="section" id="s2-using_the_new_configuration_format"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.6. Using the New Configuration Format</h3></div></div></div><div class="para">
+ In <span class="application"><strong>rsyslog</strong></span> version 6, a new configuration syntax has been introduced. This new configuration format aims to be more powerful, more intuitive, and to prevent common mistakes by not permitting certain invalid constructs. The syntax enhancement is enabled by the new configuration processor that relies on RainerScript. The legacy format is still fully supported and it is used by default in the <code class="filename">/etc/rsyslog.conf</code> configuration file.
</div><div class="para">
- To determine if the packages are already installed on your system, issue the following command:
- </div><pre class="synopsis"><code class="command">rpm -q cronie cronie-anacron</code></pre><div class="para">
- The command returns full names of the <span class="package">cronie</span> and <span class="package">cronie-anacron</span> packages if already installed, or notifies you that the packages are not available.
+ RainerScript is a scripting language designed for processing network events and configuring event processors such as <span class="application"><strong>rsyslog</strong></span>. RainerScript was primarily used to define expression-based filters, see <a class="xref" href="#ex-expression-based_filters">Example 17.3, “Expression-based Filters”</a>. The newest version of RainerScript implements the <code class="function">input()</code> and <code class="function">ruleset()</code> statements, which permit the <code class="filename">/etc/rsyslog.conf</code> configuration file to be written in the new style only.
</div><div class="para">
- To install these packages, use the <code class="command">yum</code> command in the following form as <code class="systemitem">root</code>:
- </div><pre class="synopsis"><code class="command">yum install <em class="replaceable"><code>package</code></em></code></pre><div class="para">
- For example, to install both Cron and Anacron, type the following at a shell prompt:
- </div><pre class="screen">~]# <code class="command">yum install cronie cronie-anacron</code></pre><div class="para">
- For more information on how to install new packages in Fedora, see <a class="xref" href="#sec-Installing">Section 5.2.4, “Installing Packages”</a>.
- </div></div><div class="section" id="sect-Cron-Running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.2. Running the Crond Service</h3></div></div></div><div class="para">
+ In the following examples you can compare the configuration written with legacy-style parameters:
+ </div><pre class="screen">
+$InputFileName /tmp/inputfile
+$InputFileTag tag1:
+$InputFileStateFile inputfile-state
+$InputRunFileMonitor
+</pre><div class="para">
+ and the same configuration with use of the new format statement:
+ </div><pre class="screen">
+input(type="imfile" file="/tmp/inputfile" tag="tag1:" statefile="inputfile-state")
+</pre><div class="para">
+ This significantly reduces the number of parameters used in configuration, improves readability, and also provides higher execution speed. For more information on RainerScript statements and parameters see <a class="xref" href="#brid-Log_Files-Resources-Online">the section called “Online Documentation”</a>.
+ </div></div><div class="section" id="s2-Rulesets"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.7. Rulesets</h3></div></div></div><div class="para">
+ Leaving special directives aside, <span class="application"><strong>rsyslog</strong></span> handles messages as defined by <span class="emphasis"><em>rules</em></span> that consist of a filter condition and an action to be performed if the condition is true. With a traditionally written <code class="filename">/etc/rsyslog.conf</code> file, all rules are evaluated in order of appearance for every input message. This process starts with the first rule and continues until all rules have been processed or until the message is discarded by one of the rules.
+ </div><div class="para">
+ However, rules can be grouped into sequences called <em class="firstterm">rulesets</em>. With rulesets, you can limit the effect of certain rules only to selected inputs or enhance the performance of <span class="application"><strong>rsyslog</strong></span> by defining a distinct set of actions bound to a specific input. In other words, filter conditions that will be inevitably evaluated as false for certain types of messages can be skipped. With the new configuration format, the <code class="function">input()</code> and <code class="function">ruleset()</code> statements are reserved for this operation. The ruleset definition in <code class="filename">/etc/rsyslog.conf</code> can look as follows:
+ </div><pre class="screen">
+ruleset(name="<em class="replaceable"><code>rulesetname</code></em>") {
+ <em class="replaceable"><code>rule</code></em>
+ <em class="replaceable"><code>rule2</code></em>
+ call <em class="replaceable"><code>rulesetname2</code></em>
+ …
+}
+</pre><div class="para">
+ Replace <em class="replaceable"><code>rulesetname</code></em> with an identifier for your ruleset. The ruleset name cannot start with <code class="literal">RSYSLOG_</code> since this namespace is reserved for use by <span class="application"><strong>rsyslog</strong></span>. <code class="literal">RSYSLOG_DefaultRuleset</code> then defines the default set of rules to be performed if the message has no other ruleset assigned. With <em class="replaceable"><code>rule</code></em> and <em class="replaceable"><code>rule2</code></em> you can define rules in filter-action format mentioned above. With the <em class="parameter"><code>call</code></em> parameter, you can nest rulesets by calling them from inside other ruleset blocks.
+ </div><div class="para">
+ After creating a ruleset, you need to specify what input it will apply to:
+ </div><pre class="synopsis">input(type="<em class="replaceable"><code>input_type</code></em>" port="<em class="replaceable"><code>port_num</code></em>" ruleset="<em class="replaceable"><code>rulesetname</code></em>");</pre><div class="para">
+ Here you can identify an input message by <em class="replaceable"><code>input_type</code></em>, which is an input module that gathered the message, or by <em class="replaceable"><code>port_num</code></em> – the port number. Other parameters such as <span class="emphasis"><em>file</em></span> or <span class="emphasis"><em>tag</em></span> can be specified for <code class="function">input()</code>. Replace <em class="replaceable"><code>rulesetname</code></em> with a name of the ruleset to be evaluated against the message. In case an input message is not explicitly bound to a ruleset, the default ruleset is triggered.
+ </div><div class="para">
+ You can also use the legacy format to define rulesets, for more information see <a class="xref" href="#brid-Log_Files-Resources-Online">the section called “Online Documentation”</a>.
+ </div><div class="example" id="ex-using_rulesets"><h6>Example 17.11. Using rulesets</h6><div class="example-contents"><div class="para">
+ The following rulesets ensure different handling of remote messages coming from different ports. Add the following into <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+ruleset(name="remote-10514") {
+ action(type="omfile" file="/var/log/remote-10514")
+}
+
+ruleset(name="remote-10515") {
+ cron.* action(type="omfile" file="/var/log/remote-10515-cron")
+ mail.* action(type="omfile" file="/var/log/remote-10515-mail")
+}
+
+input(type="imtcp" port="10514" ruleset="remote-10514");
+input(type="imtcp" port="10515" ruleset="remote-10515");
+</pre><div class="para">
+ Rulesets shown in the above example define log destinations for the remote input from two ports, in case of 10515, messages are sorted according to the facility. Then, the TCP input is enabled and bound to rulesets. Note that you must load the required modules (imtcp) for this configuration to work.
+ </div></div></div><br class="example-break" /></div><div class="section" id="s2-compatibility_with_syslogd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.8. Compatibility with syslogd</h3></div></div></div><div class="para">
+ From <span class="application"><strong>rsyslog</strong></span> version 6, compatibility mode specified via the <code class="option">-c</code> option has been removed. Also, the syslogd-style command line options are deprecated and configuring <span class="application"><strong>rsyslog</strong></span> through these command line options should be avoided. However, you can use several templates and directives to configure <code class="systemitem">rsyslogd</code> to emulate syslogd-like behavior.
+ </div><div class="para">
+ For more information on various <code class="systemitem">rsyslogd</code> options, see the <code class="filename">rsyslogd(8)</code>manual page.
+ </div></div></div><div class="section" id="s1-working_with_queues_in_rsyslog"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.3. Working with Queues in Rsyslog</h2></div></div></div><div class="para">
+ Queues are used to pass content, mostly syslog messages, between components of <span class="application"><strong>rsyslog</strong></span>. With queues, rsyslog is capable of processing multiple messages simultaneously and to apply several actions to a single message at once. The data flow inside <span class="application"><strong>rsyslog</strong></span> can be illustrated as follows:
+ </div><div class="figure" id="fig-message_flow_in_rsyslog"><div class="figure-contents"><div class="mediaobject"><img src="images/rsyslog_message_flow.png" width="444" alt="Message Flow in Rsyslog" /><div class="longdesc"><div class="para">
+ Message Flow in Rsyslog
+ </div></div></div></div><h6>Figure 17.1. Message Flow in Rsyslog</h6></div><br class="figure-break" /><div class="para">
+ Whenever <span class="application"><strong>rsyslog</strong></span> receives a message, it passes this message to the preprocessor and then places it into the <em class="firstterm">main message queue</em>. Messages wait there to be dequeued and passed to the <em class="firstterm">rule processor</em>.
+ </div><div class="para">
+ The <span class="emphasis"><em>rule processor</em></span> is a parsing and filtering engine. Here, the rules defined in <code class="filename">/etc/rsyslog.conf</code> are applied. Based on these rules, the rule processor evaluates which actions are to be performed. Each action has its own action queue. Messages are passed through this queue to the respective action processor which creates the final output. Note that at this point, several actions can run simultaneously on one message. For this purpose, a message is duplicated and passed to multiple action processors.
+ </div><div class="para">
+ Only one queue per action is possible. Depending on configuration, the messages can be sent right to the action processor without action queuing. This is the behavior of <span class="emphasis"><em>direct queues</em></span> (see below). In case the output action fails, the action processor notifies the action queue, which then takes an unprocessed element back and after some time interval, the action is attempted again.
+ </div><div class="para">
+ To sum up, there are two positions where queues stand in <span class="application"><strong>rsyslog</strong></span>: either in front of the rule processor as a single <span class="emphasis"><em>main message queue</em></span> or in front of various types of output actions as <span class="emphasis"><em>action queues</em></span>. Queues provide two main advantages that both lead to increased performance of message processing:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ they serve as buffers that <span class="emphasis"><em>decouple</em></span> producers and consumers in the structure of <span class="application"><strong>rsyslog</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ they allow for <span class="emphasis"><em>parallelization</em></span> of actions performed on messages
+ </div></li></ul></div><div class="para">
+ Apart from this, queues can be configured with several directives to provide optimal performance for your system. These configuration options are covered in the following sections.
+ </div><div class="section" id="s2-defining_queues"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.3.1. Defining Queues</h3></div></div></div><div class="para">
+ Based on where the messages are stored, there are several types of queues: <span class="emphasis"><em>direct</em></span>, <span class="emphasis"><em>in-memory</em></span>, <span class="emphasis"><em>disk</em></span>, and <span class="emphasis"><em>disk-assisted in-memory</em></span> queues that are most widely used. You can choose one of these types for the main message queue and also for action queues. Add the following into <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueType <em class="replaceable"><code>queue_type</code></em></pre><div class="para">
+ Here, you can apply the setting for the main message queue (replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code>) or for an action queue (replace <em class="replaceable"><code>object</code></em> with <code class="option">Action</code>). Replace <em class="replaceable"><code>queue_type</code></em> with one of <code class="literal">direct</code>, <code class="literal">linkedlist</code> or <code class="literal">fixedarray</code> (which are in-memory queues), or <code class="literal">disk</code>.
+ </div><div class="para">
+ The default setting for a main message queue is the FixedArray queue with a limit of 10,000 messages. Action queues are by default set as Direct queues.
+ </div><h4 id="br-direct_queues">Direct Queues</h4><div class="para">
+ For many simple operations, such as when writing output to a local file, building a queue in front of an action is not needed. To avoid queuing, use:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueType Direct</pre><div class="para">
+ Replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code> or with <code class="option">Action</code> to use this option to the main message queue or for an action queue respectively. With direct queue, messages are passed directly and immediately from the producer to the consumer.
+ </div><h4 id="br-disk_queues">Disk Queues</h4><div class="para">
+ Disk queues store messages strictly on a hard drive, which makes them highly reliable but also the slowest of all possible queuing modes. This mode can be used to prevent the loss of highly important log data. However, disk queues are not recommended in most use cases. To set a disk queue, type the following into <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueType Disk</pre><div class="para">
+ Replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code> or with <code class="option">Action</code> to use this option to the main message queue or for an action queue respectively. Disk queues are written in parts, with a default size 10 Mb. This default size can be modified with the following configuration directive:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueMaxFileSize <em class="replaceable"><code>size</code></em></pre><div class="para">
+ where <em class="replaceable"><code>size</code></em> represents the specified size of disk queue part. The defined size limit is not restrictive, <span class="application"><strong>rsyslog</strong></span> always writes one complete queue entry, even if it violates the size limit. Each part of a disk queue matches with an individual file. The naming directive for these files looks as follows:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueFilename <em class="replaceable"><code>name</code></em></pre><div class="para">
+ This sets a <em class="replaceable"><code>name</code></em> prefix for the file followed by a 7-digit number starting at one and incremented for each file.
+ </div><h4 id="br-in-memory_queues">In-memory Queues</h4><div class="para">
+ With in-memory queue, the enqueued messages are held in memory which makes the process very fast. The queued data is lost if the computer is power cycled or shut down. However, you can use the <code class="option">$ActionQueueSaveOnShutdown</code> setting to save the data before shutdown. There are two types of in-memory queues:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>FixedArray</em></span> queue — the default mode for the main message queue, with a limit of 10,000 elements. This type of queue uses a fixed, pre-allocated array that holds pointers to queue elements. Due to these pointers, even if the queue is empty a certain amount of memory is consumed. However, FixedArray offers the best run time performance and is optimal when you expect a relatively low number of queued messages and high performance.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>LinkedList</em></span> queue — here, all structures are dynamically allocated in a linked list, thus the memory is allocated only when needed. LinkedList queues handle occasional message bursts very well.
+ </div></li></ul></div><div class="para">
+ In general, use LinkedList queues when in doubt. Compared to FixedArray, it consumes less memory and lowers the processing overhead.
+ </div><div class="para">
+ Use the following syntax to configure in-memory queues:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueType LinkedList</pre><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueType FixedArray</pre><div class="para">
+ Replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code> or with <code class="option">Action</code> to use this option to the main message queue or for an action queue respectively.
+ </div><h4 id="br-disk-assisted_in-memory_queues">Disk-Assisted In-memory Queues</h4><div class="para">
+ Both disk and in-memory queues have their advantages and <span class="application"><strong>rsyslog</strong></span> lets you combine them in <span class="emphasis"><em>disk-assisted in-memory queues</em></span>. To do so, configure a normal in-memory queue and then add the <code class="option">$objectQueueFileName</code> directive to define a file name for disk assistance. This queue then becomes <span class="emphasis"><em>disk-assisted</em></span>, which means it couples an in-memory queue with a disk queue to work in tandem.
+ </div><div class="para">
+ The disk queue is activated if the in-memory queue is full or needs to persist after shutdown. With a disk-assisted queue, you can set both disk-specific and in-memory specific configuration parameters. This type of queue is probably the most commonly used, it is especially useful for potentially long-running and unreliable actions.
+ </div><div class="para">
+ To specify the functioning of a disk-assisted in-memory queue, use the so-called <span class="emphasis"><em>watermarks</em></span>:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueHighWatermark <em class="replaceable"><code>number</code></em></pre><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueLowWatermark <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code> or with <code class="option">Action</code> to use this option to the main message queue or for an action queue respectively. Replace <em class="replaceable"><code>number</code></em> with a number of enqueued messages. When an in-memory queue reaches the number defined by the high watermark, it starts writing messages to disk and continues until the in-memory queue size drops to the number defined with the low watermark. Correctly set watermarks minimize unnecessary disk writes, but also leave memory space for message bursts since writing to disk files is rather lengthy. Therefore, the high watermark must be lower than the whole queue capacity set with <span class="emphasis"><em>$objectQueueSize</em></span>. The difference between the high watermark and the overall queue size is a spare memory buffer reserved for message bursts. On the other hand, setting the high watermark t
oo low will turn on disk assistance unnecessarily often.
+ </div><div class="example" id="ex-net_forwarding_with_queue"><h6>Example 17.12. Reliable Forwarding of Log Messages to a Server</h6><div class="example-contents"><div class="para">
+ Rsyslog is often used to maintain a centralized logging system, where log messages are forwarded to a server over the network. To avoid message loss when the server is not available, it is advisable to configure an action queue for the forwarding action. This way, messages that failed to be sent are stored locally until the server is reachable again. Note that such queues are not configurable for connections using the <code class="systemitem">UDP</code> protocol. To establish a fully reliable connection, for example when your logging server is outside of your private network, consider using the RELP protocol described in <a class="xref" href="#s2-using_RELP">Section 17.4.4, “Using RELP”</a>.
+ </div><div class="procedure" id="proc-net_forwarding_with_queue"><h6>Procedure 17.1. Forwarding To a Single Server</h6><div class="para">
+ Suppose the task is to forward log messages from the system to a server with host name <span class="emphasis"><em>example.com</em></span>, and to configure an action queue to buffer the messages in case of a server outage. To do so, perform the following steps:
+ </div><ol class="1"><li class="step"><div class="para">
+ Create a working directory to store the queue files. For example:
+ </div><pre class="synopsis">~]# <code class="command">mkdir</code> <code class="filename">/rsyslog/work/</code></pre></li><li class="step"><div class="para">
+ Use the following configuration in <code class="filename">/etc/rsyslog.conf</code> or create a file with the following content in the <code class="filename">/etc/rsyslog.d/</code> directory:
+ </div><pre class="screen">$WorkDirectory /rsyslog/work
+
+$ActionQueueType LinkedList
+$ActionQueueFileName example_fwd
+$ActionResumeRetryCount -1
+$ActionQueueSaveOnShutdown on
+*.* @@example.com:18</pre><div class="itemizedlist"><div class="para">
+ Where:
+ </div><ul><li class="listitem"><div class="para">
+ the <code class="filename">/rsyslog/work/</code> directory created in the previous step is marked as a working directory,
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">$ActionQueueType</code> enables a LinkedList in-memory queue,
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">$ActionFileName</code> defines a disk storage, in this case the backup files are created in the <code class="filename">/rsyslog/work/</code> directory with the <span class="emphasis"><em>example_fwd</em></span> prefix,
+ </div></li><li class="listitem"><div class="para">
+ the <code class="option">$ActionResumeRetryCount -1</code> setting prevents rsyslog form dropping messages when retrying to connect if server is not responding,
+ </div></li><li class="listitem"><div class="para">
+ enabled <code class="option">$ActionQueueSaveOnShutdown</code> saves in-memory data if rsyslog shuts down,
+ </div></li><li class="listitem"><div class="para">
+ the last line forwards all received messages to the logging server, port specification is optional.
+ </div></li></ul></div><div class="para">
+ With the above configuration, rsyslog keeps messages in memory if the remote server is not reachable. A file on disk is created only if rsyslog runs out of the configured memory queue space or needs to shut down, which benefits the system performance.
+ </div></li></ol></div><div class="procedure" id="proc-net_forwarding_two_servers"><h6>Procedure 17.2. Forwarding To Multiple Servers</h6><div class="para">
+ The process of forwarding log messages to multiple servers is similar to the previous procedure:
+ </div><ol class="1"><li class="step"><div class="para">
+ Create a working directory for rsyslog to store the queue files. For example:
+ </div><pre class="synopsis">~]# <code class="command">mkdir</code> <code class="filename">/rsyslog/work/</code></pre></li><li class="step"><div class="para">
+ Each destination server requires a separate forwarding rule, action queue specification, and backup file on disk. For example, use the following configuration in <code class="filename">/etc/rsyslog.conf</code> or create a file with the following content in the <code class="filename">/etc/rsyslog.d/</code> directory:
+ </div><pre class="screen">$WorkDirectory /rsyslog/work
+
+$ActionQueueType LinkedList
+$ActionQueueFileName example_fwd1
+$ActionResumeRetryCount -1
+$ActionQueueSaveOnShutdown on
+*.* @@example1.com
+
+$ActionQueueType LinkedList
+$ActionQueueFileName example_fwd2
+$ActionResumeRetryCount -1
+$ActionQueueSaveOnShutdown on
+*.* @@example2.com</pre></li></ol></div></div></div><br class="example-break" /></div><div class="section" id="s2-managing_queues"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.3.2. Managing Queues</h3></div></div></div><div class="para">
+ All types of queues can be further configured to match your requirements. You can use several directives to modify both action queues and the main message queue. Currently, there are more than 20 queue parameters available, see <a class="xref" href="#brid-Log_Files-Resources-Online">the section called “Online Documentation”</a>. Some of these settings are used commonly, others, such as worker thread management, provide closer control over the queue behavior and are reserved for advanced users. With advanced settings, you can optimize <span class="application"><strong>rsyslog</strong></span>'s performance, schedule queuing, or modify the behavior of queue on system shutdown.
+ </div><h4 id="br-limiting_queue_size">Limiting Queue Size</h4><div class="para">
+ You can limit the number of messages that queue can contain with the following setting:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueHighWatermark <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code> or with <code class="option">Action</code> to use this option to the main message queue or for an action queue respectively. Replace <em class="replaceable"><code>number</code></em> with a number of enqueued messages. You can set the queue size only as the number of messages, not as their actual memory size. The default queue size is 10,000 messages for the main message queue and ruleset queues, and 1000 for action queues.
+ </div><div class="para">
+ Disk assisted queues are unlimited by default and can not be restricted with this directive, but you can reserve them physical disk space in bytes with the following settings:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueMaxDiscSpace <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code> or with <code class="option">Action</code>. When the size limit specified by <em class="replaceable"><code>number</code></em> is hit, messages are discarded until sufficient amount of space is freed by dequeued messages.
+ </div><h4 id="br-discarding_messages">Discarding Messages</h4><div class="para">
+ When a queue reaches a certain number of messages, you can discard less important messages in order to save space in the queue for entries of higher priority. The threshold that launches the discarding process can be set with the so-called <span class="emphasis"><em>discard mark</em></span>:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueDiscardMark <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code> or with <code class="option">Action</code> to use this option to the main message queue or for an action queue respectively. Here, <em class="replaceable"><code>number</code></em> stands for a number of messages that have to be in the queue to start the discarding process. To define which messages to discard, use:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueDiscardSeverity <em class="replaceable"><code>priority</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>priority</code></em> with one of the following keywords (or with a number): <code class="command">debug</code> (7), <code class="command">info</code> (6), <code class="command">notice</code> (5), <code class="command">warning</code> (4), <code class="command">err</code> (3), <code class="command">crit</code> (2), <code class="command">alert</code> (1), and <code class="command">emerg</code> (0). With this setting, both newly incoming and already queued messages with lower than defined priority are erased from the queue immediately after the discard mark is reached.
+ </div><h4 id="br-using_timeframes">Using Timeframes</h4><div class="para">
+ You can configure <span class="application"><strong>rsyslog</strong></span> to process queues during a specific time period. With this option you can, for example, transfer some processing into off-peak hours. To define a time frame, use the following syntax:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueDequeueTimeBegin <em class="replaceable"><code>hour</code></em></pre><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueDequeueTimeEnd <em class="replaceable"><code>hour</code></em></pre><div class="para">
+ With <em class="replaceable"><code>hour</code></em> you can specify hours that bound your time frame. Use the 24-hour format without minutes.
+ </div><h4 id="br-configuring_worker_threads">Configuring Worker Threads</h4><div class="para">
+ A <em class="firstterm">worker thread</em> performs a specified action on the enqueued message. For example, in the main message queue, a worker task is to apply filter logic to each incoming message and enqueue them to the relevant action queues. When a message arrives, a worker thread is started automatically. When the number of messages reaches a certain number, another worker thread is turned on. To specify this number, use:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueWorkerThreadMinimumMessages <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>number</code></em> with a number of messages that will trigger a supplemental worker thread. For example, with <em class="replaceable"><code>number</code></em> set to 100, a new worker thread is started when more than 100 messages arrive. When more than 200 messages arrive, the third worker thread starts and so on. However, too many working threads running in parallel becomes ineffective, so you can limit the maximum number of them by using:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueWorkerThreads <em class="replaceable"><code>number</code></em></pre><div class="para">
+ where <em class="replaceable"><code>number</code></em> stands for a maximum number of working threads that can run in parallel. For the main message queue, the default limit is 1 thread. Once a working thread has been started, it keeps running until an inactivity timeout appears. To set the length of timeout, type:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueWorkerTimeoutThreadShutdown <em class="replaceable"><code>time</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>time</code></em> with the duration set in milliseconds. Without this setting, a zero timeout is applied and a worker thread is terminated immediately when it runs out of messages. If you specify <em class="replaceable"><code>time</code></em> as <code class="literal">-1</code>, no thread will be closed.
+ </div><h4 id="br-batch_dequeuing">Batch Dequeuing</h4><div class="para">
+ To increase performance, you can configure <span class="application"><strong>rsyslog</strong></span> to dequeue multiple messages at once. To set the upper limit for such dequeueing, use:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueDequeueBatchSize <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>number</code></em> with the maximum number of messages that can be dequeued at once. Note that a higher setting combined with a higher number of permitted working threads results in greater memory consumption.
+ </div><h4 id="br-terminating_queues">Terminating Queues</h4><div class="para">
+ When terminating a queue that still contains messages, you can try to minimize the data loss by specifying a time interval for worker threads to finish the queue processing:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueTimeoutShutdown <em class="replaceable"><code>time</code></em></pre><div class="para">
+ Specify <em class="replaceable"><code>time</code></em> in milliseconds. If after that period there are still some enqueued messages, workers finish the current data element and then terminate. Unprocessed messages are therefore lost. Another time interval can be set for workers to finish the final element:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueTimeoutActionCompletion <em class="replaceable"><code>time</code></em></pre><div class="para">
+ In case this timeout expires, any remaining workers are shut down. To save data at shutdown, use:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueTimeoutSaveOnShutdown <em class="replaceable"><code>time</code></em></pre><div class="para">
+ If set, all queue elements are saved to disk before <span class="application"><strong>rsyslog</strong></span> terminates.
+ </div></div></div><div class="section" id="s1-using_rsyslog_modules"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.4. Using Rsyslog Modules</h2></div></div></div><div class="para">
+ Due to its modular design, <span class="application"><strong>rsyslog</strong></span> offers a variety of <em class="firstterm">modules</em> which provide additional functionality. Note that modules can be written by third parties. Most modules provide additional inputs (see <span class="emphasis"><em>Input Modules</em></span> below) or outputs (see <span class="emphasis"><em>Output Modules</em></span> below). Other modules provide special functionality specific to each module. The modules may provide additional configuration directives that become available after a module is loaded. To load a module, use the following syntax:
+ </div><pre class="screen">
+$ModLoad <em class="replaceable"><code>MODULE</code></em>
+</pre><div class="para">
+ where <code class="option">$ModLoad</code> is the global directive that loads the specified module and <em class="replaceable"><code>MODULE</code></em> represents your desired module. For example, if you want to load the Text File Input Module (<code class="command">imfile</code>) that enables <span class="application"><strong>rsyslog</strong></span> to convert any standard text files into syslog messages, specify the following line in the <code class="filename">/etc/rsyslog.conf</code> configuration file:
+ </div><pre class="screen">
+$ModLoad imfile
+</pre><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> offers a number of modules which are split into the following main categories:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Input Modules — Input modules gather messages from various sources. The name of an input module always starts with the <code class="literal">im</code> prefix, such as <code class="command">imfile</code>, <code class="command">imjournal</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Output Modules — Output modules provide a facility to issue message to various targets such as sending across a network, storing in a database, or encrypting. The name of an output module always starts with the <code class="literal">om</code> prefix, such as <code class="command">omsnmp</code>, <code class="command">omrelp</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Parser Modules — These modules are useful in creating custom parsing rules or to parse malformed messages. With moderate knowledge of the C programming language, you can create your own message parser. The name of a parser module always starts with the <code class="literal">pm</code> prefix, such as <code class="command">pmrfc5424</code>, <code class="command">pmrfc3164</code>, and so on.
+ </div></li><li class="listitem"><div class="para">
+ Message Modification Modules — Message modification modules change content of syslog messages. Names of these modules start with the <code class="literal">mm</code> prefix. Message Modification Modules such as <code class="command">mmanon</code>, <code class="command">mmnormalize</code>, or <code class="command">mmjsonparse</code> are used for anonymization or normalization of messages.
+ </div></li><li class="listitem"><div class="para">
+ String Generator Modules — String generator modules generate strings based on the message content and strongly cooperate with the template feature provided by <span class="application"><strong>rsyslog</strong></span>. For more information on templates, see <a class="xref" href="#s2-Templates">Section 17.2.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> or <code class="command">smtradfile</code>.
+ </div></li><li class="listitem"><div class="para">
+ Library Modules — Library modules provide functionality for other loadable modules. These modules are loaded automatically by <span class="application"><strong>rsyslog</strong></span> when needed and cannot be configured by the user.
+ </div></li></ul></div><div class="para">
+ A comprehensive list of all available modules and their detailed description can be found at <a href="http://www.rsyslog.com/doc/rsyslog_conf_modules.html/">http://www.rsyslog.com/doc/rsyslog_conf_modules.html</a>.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Note that when <span class="application"><strong>rsyslog</strong></span> loads any modules, it provides them with access to some of its functions and data. This poses a possible security threat. To minimize security risks, use trustworthy modules only.
+ </div></div></div><div class="section" id="s2-importing_text_files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.4.1. Importing Text Files</h3></div></div></div><div class="para">
+ The Text File Input Module, abbreviated as <code class="command">imfile</code>, enables <span class="application"><strong>rsyslog</strong></span> to convert any text file into a stream of syslog messages. You can use <code class="command">imfile</code> to import log messages from applications that create their own text file logs. To load <code class="command">imfile</code>, add the following into <code class="filename">etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imfile
+$InputFilePollInterval <em class="replaceable"><code>int</code></em>
+</pre><div class="para">
+ It is sufficient to load <code class="command">imfile</code> once, even when importing multiple files. The <span class="emphasis"><em>$InputFilePollInterval</em></span> global directive specifies how often <span class="application"><strong>rsyslog</strong></span> checks for changes in connected text files. The default interval is 10 seconds, to change it, replace <em class="replaceable"><code>int</code></em> with a time interval specified in seconds.
+ </div><div class="para">
+ To identify the text files to import, use the following syntax in <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+# File 1
+$InputFileName <em class="replaceable"><code>path_to_file</code></em>
+$InputFileTag <em class="replaceable"><code>tag:</code></em>
+$InputFileStateFile <em class="replaceable"><code>state_file_name</code></em>
+$InputFileSeverity <em class="replaceable"><code>severity</code></em>
+$InputFileFacility <em class="replaceable"><code>facility</code></em>
+$InputRunFileMonitor
+
+# File 2
+$InputFileName <em class="replaceable"><code>path_to_file2</code></em>
+...
+</pre><div class="para">
+ Four settings are required to specify an input text file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ replace <em class="replaceable"><code>path_to_file</code></em> with a path to the text file.
+ </div></li><li class="listitem"><div class="para">
+ replace <em class="replaceable"><code>tag:</code></em> with a tag name for this message.
+ </div></li><li class="listitem"><div class="para">
+ replace <em class="replaceable"><code>state_file_name</code></em> with a unique name for the <span class="emphasis"><em>state file</em></span>. <span class="emphasis"><em>State files</em></span>, which are stored in the rsyslog working directory, keep cursors for the monitored files, marking what partition has already been processed. If you delete them, whole files will be read in again. Make sure that you specify a name that does not already exist.
+ </div></li><li class="listitem"><div class="para">
+ add the <span class="emphasis"><em>$InputRunFileMonitor</em></span> directive that enables the file monitoring. Without this setting, the text file will be ignored.
+ </div></li></ul></div><div class="para">
+ Apart from the required directives, there are several other settings that can be applied on the text input. Set the severity of imported messages by replacing <em class="replaceable"><code>severity</code></em> with an appropriate keyword. Replace <em class="replaceable"><code>facility</code></em> with a keyword to define the subsystem that produced the message. The keywords for severity and facility are the same as those used in facility/priority-based filters, see <a class="xref" href="#s2-Filters">Section 17.2.1, “Filters”</a>.
+ </div><div class="example" id="ex-importing_text_files"><h6>Example 17.13. Importing Text Files</h6><div class="example-contents"><div class="para">
+ The Apache HTTP server creates log files in text format. To apply the processing capabilities of <span class="application"><strong>rsyslog</strong></span> to apache error messages, first use the <code class="command">imfile</code> module to import the messages. Add the following into <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imfile
+
+$InputFileName /var/log/httpd/error_log
+$InputFileTag apache-error:
+$InputFileStateFile state-apache-error
+$InputRunFileMonitor
+</pre></div></div><br class="example-break" /></div><div class="section" id="s2-exporting_messages_to_a_database"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.4.2. Exporting Messages to a Database</h3></div></div></div><div class="para">
+ Processing of log data can be faster and more convenient when performed in a database rather than with text files. Based on the type of DBMS used, choose from various output modules such as <code class="command">ommysql</code>, <code class="command">ompgsql</code>, <code class="command">omoracle</code>, or <code class="command">ommongodb</code>. As an alternative, use the generic <code class="command">omlibdbi</code> output module that relies on the <code class="systemitem">libdbi</code> library. The <code class="command">omlibdbi</code> module supports database systems Firebird/Interbase, MS SQL, Sybase, SQLite, Ingres, Oracle, mSQL, MySQL, and PostgreSQL.
+ </div><div class="example" id="ex-exporting_rsyslog_messages_to_a_database"><h6>Example 17.14. Exporting Rsyslog Messages to a Database</h6><div class="example-contents"><div class="para">
+ To store the rsyslog messages in a MySQL database, add the following into <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad ommysql
+
+$ActionOmmysqlServerPort 1234
+*.* :ommysql:database-server,database-name,database-userid,database-password
+</pre><div class="para">
+ First, the output module is loaded, then the communication port is specified. Additional information, such as name of the server and the database, and authentication data, is specified on the last line of the above example.
+ </div></div></div><br class="example-break" /></div><div class="section" id="s2-enabling_encrypted_transport"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.4.3. Enabling Encrypted Transport</h3></div></div></div><div class="para">
+ Confidentiality and integrity in network transmissions can be provided by either the <span class="emphasis"><em>TLS</em></span> or <span class="emphasis"><em>GSSAPI</em></span> encryption protocol.
+ </div><div class="para">
+ <span class="emphasis"><em>Transport Layer Security</em></span> (TLS) is a cryptographic protocol designed to provide communication security over the network. When using TLS, rsyslog messages are encrypted before sending, and mutual authentication exists between the sender and receiver.
+ </div><div class="para">
+ <span class="emphasis"><em>Generic Security Service API</em></span> (GSSAPI) is an application programming interface for programs to access security services. To use it in connection with <span class="application"><strong>rsyslog</strong></span> you must have a functioning <span class="application"><strong>Kerberos</strong></span> environment.
+ </div></div><div class="section" id="s2-using_RELP"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.4.4. Using RELP</h3></div></div></div><div class="para">
+ <span class="emphasis"><em>Reliable Event Logging Protocol</em></span> (RELP) is a networking protocol for data logging in computer networks. It is designed to provide reliable delivery of event messages, which makes it useful in environments where message loss is not acceptable.
+ </div></div></div><div class="section" id="s1-interaction_of_rsyslog_and_journal"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.5. Interaction of Rsyslog and Journal</h2></div></div></div><div class="para">
+ As mentioned above, <span class="application"><strong>Rsyslog</strong></span> and <span class="application"><strong>Journal</strong></span>, the two logging applications present on your system, have several distinctive features that make them suitable for specific use cases. In many situations it is useful to combine their capabilities, for example to create structured messages and store them in a file database (see <a class="xref" href="#s1-structured_logging_with_rsyslog">Section 17.6, “Structured Logging with Rsyslog”</a>). A communication interface needed for this cooperation is provided by input and output modules on the side of <span class="application"><strong>Rsyslog</strong></span> and by the <span class="application"><strong>Journal</strong></span>'s communication socket.
+ </div><div class="para">
+ By default, <code class="systemitem">rsyslogd</code> uses the <code class="systemitem">imjournal</code> module as a default input mode for journal files. With this module, you import not only the messages but also the structured data provided by <code class="systemitem">journald</code>. Also, older data can be imported from <code class="systemitem">journald</code> (unless forbidden with the <code class="option">$ImjournalIgnorePreviousMessages</code> directive). See <a class="xref" href="#s2-importing_data_from_journal">Section 17.6.1, “Importing Data from Journal”</a> for basic configuration of <code class="systemitem">imjournal</code>.
+ </div><div class="para">
+ As an alternative, configure <code class="systemitem">rsyslogd</code> to read from the socket provided by <code class="systemitem">journal</code> as an output for syslog-based applications. The path to the socket is <code class="filename">/run/systemd/journal/syslog</code>. Use this option when you want to maintain plain rsyslog messages. Compared to <code class="systemitem">imjournal</code> the socket input currently offers more features, such as ruleset binding or filtering. To import <span class="application"><strong>Journal</strong></span> data trough the socket, use the following configuration in <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imuxsock
+$OmitLocalLogging off
+</pre><div class="para">
+ The above syntax loads the <code class="systemitem">imuxsock</code> module and turns off the <code class="option">$OmitLocalLogging</code> directive, which enables the import trough the system socket. The path to this socket is specified separately in <code class="filename">/etc/rsyslog.d/listen.conf</code> as follows:
+ </div><pre class="screen">
+$SystemLogSocketName /run/systemd/journal/syslog
+</pre><div class="para">
+ You can also output messages from <span class="application"><strong>Rsyslog</strong></span> to <span class="application"><strong>Journal</strong></span> with the <code class="systemitem">omjournal</code> module. Configure the output in <code class="filename">/etc/rsyslog.conf</code> as follows:
+ </div><pre class="screen">
+$ModLoad omjournal
+
+*.* :omjournal:
+</pre><div class="para">
+ For instance, the following configuration forwards all received messages on tcp port 10514 to the Journal:
+ </div><pre class="screen">
+$ModLoad imtcp
+$ModLoad omjournal
+
+$RuleSet remote
+*.* :omjournal:
+
+$InputTCPServerBindRuleset remote
+$InputTCPServerRun 10514
+</pre></div><div class="section" id="s1-structured_logging_with_rsyslog"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.6. Structured Logging with Rsyslog</h2></div></div></div><div class="para">
+ On systems that produce large amounts of log data, it can be convenient to maintain log messages in a <span class="emphasis"><em>structured format</em></span>. With structured messages, it is easier to search for particular information, to produce statistics and to cope with changes and inconsistencies in message structure. <span class="application"><strong>Rsyslog</strong></span> uses the <span class="emphasis"><em>JSON</em></span> (JavaScript Object Notation) format to provide structure for log messages.
+ </div><div class="para">
+ Compare the following unstructured log message:
+ </div><pre class="synopsis">Oct 25 10:20:37 localhost anacron[1395]: Jobs will be executed sequentially</pre><div class="para">
+ with a structured one:
+ </div><pre class="synopsis">{"timestamp":"2013-10-25T10:20:37", "host":"localhost", "program":"anacron", "pid":"1395", "msg":"Jobs will be executed sequentially"}</pre><div class="para">
+ Searching structured data with use of key-value pairs is faster and more precise than searching text files with regular expressions. The structure also lets you to search for the same entry in messages produced by various applications. Also, JSON files can be stored in a document database such as <span class="database">MongoDB</span>, which provides additional performance and analysis capabilities. On the other hand, a structured message requires more disk space than the unstructured one.
+ </div><div class="para">
+ In <span class="application"><strong>rsyslog</strong></span>, log messages with meta data are pulled from <span class="application"><strong>Journal</strong></span> with use of the <code class="systemitem">imjournal</code> module. With the <code class="systemitem">mmjsonparse</code> module, you can parse data imported from <span class="application"><strong>Journal</strong></span> and from other sources and process them further, for example as a database output. For parsing to be successful, <code class="systemitem">mmjsonparse</code> requires input messages to be structured in a way that is defined by the <span class="bold bold"><strong>Lumberjack</strong></span> project.
+ </div><div class="para">
+ The <span class="bold bold"><strong>Lumberjack</strong></span> project aims to add structured logging to <span class="application"><strong>rsyslog</strong></span> in a backward-compatible way. To identify a structured message, <span class="bold bold"><strong>Lumberjack</strong></span> specifies the <span class="bold bold"><strong>@cee:</strong></span> string that prepends the actual JSON structure. Also, <span class="bold bold"><strong>Lumberjack</strong></span> defines the list of standard field names that should be used for entities in the JSON string. For more information on <span class="bold bold"><strong>Lumberjack</strong></span>, see <a class="xref" href="#brid-Log_Files-Resources-Online">the section called “Online Documentation”</a>.
+ </div><div class="para">
+ The following is an example of a lumberjack-formatted message:
+ </div><pre class="synopsis"> @cee: {"pid":17055, "uid":1000, "gid":1000, "appname":"logger", "msg":"Message text."} </pre><div class="para">
+ To build this structure inside <span class="application"><strong>Rsyslog</strong></span>, a template is used, see <a class="xref" href="#s2-filtering_structured_messages">Section 17.6.2, “Filtering Structured Messages”</a>. Applications and servers can employ the <code class="systemitem">libumberlog</code> library to generate messages in the lumberjack-compliant form. For more information on <code class="systemitem">libumberlog</code>, see <a class="xref" href="#brid-Log_Files-Resources-Online">the section called “Online Documentation”</a>.
+ </div><div class="section" id="s2-importing_data_from_journal"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.6.1. Importing Data from Journal</h3></div></div></div><div class="para">
+ The <code class="command">imjournal</code> module is <span class="application"><strong>Rsyslog</strong></span>'s input module to natively read the journal files (see <a class="xref" href="#s1-interaction_of_rsyslog_and_journal">Section 17.5, “Interaction of Rsyslog and Journal”</a>). Journal messages are then logged in text format as other rsyslog messages. However, with further processing, it is possible to translate meta data provided by <span class="application"><strong>Journal</strong></span> into a structured message.
+ </div><div class="para">
+ To import data from <span class="application"><strong>Journal</strong></span> to <span class="application"><strong>Rsyslog</strong></span>, use the following configuration in <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imjournal
+
+$imjournalPersistStateInterval <em class="replaceable"><code>number_of_messages</code></em>
+$imjournalStateFile <em class="replaceable"><code>path</code></em>
+$imjournalRatelimitInterval <em class="replaceable"><code>seconds</code></em>
+$imjournalRatelimitBurst <em class="replaceable"><code>burst_number</code></em>
+$ImjournalIgnorePreviousMessages <em class="replaceable"><code>off/on</code></em>
+</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ With <em class="replaceable"><code>number_of_messages</code></em>, you can specify how often the journal data must be saved. This will happen each time the specified number of messages is reached.
+ </div></li><li class="listitem"><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a path to the state file. This file tracks the journal entry that was the last one processed.
+ </div></li><li class="listitem"><div class="para">
+ With <em class="replaceable"><code>seconds</code></em>, you set the length of the rate limit interval. The number of messages processed during this interval can not exceed the value specified in <em class="replaceable"><code>burst_number</code></em>. The default setting is 20,000 messages per 600 seconds. Rsyslog discards messages that come after the maximum burst within the time frame specified.
+ </div></li><li class="listitem"><div class="para">
+ With <code class="option">$ImjournalIgnorePreviousMessages</code> you can ignore messages that are currently in Journal and import only new messages, which is used when there is no state file specified. The default setting is <code class="literal">off</code>. Please note that if this setting is off and there is no state file, all messages in the Journal are processed, even if they were already processed in a previous rsyslog session.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ You can use <code class="systemitem">imjournal</code> simultaneously with <code class="systemitem">imuxsock</code> module that is the traditional system log input. However, to avoid message duplication, you must prevent <code class="systemitem">imuxsock</code> from reading the Journal's system socket. To do so, use the <code class="option">$OmitLocalLogging</code> directive:
+ </div><pre class="screen">
+$ModLoad imuxsock
+$ModLoad imjournal
+
+$OmitLocalLogging on
+$AddUnixListenSocket /run/systemd/journal/syslog
+</pre></div></div><div class="para">
+ You can translate all data and meta data stored by <span class="application"><strong>Journal</strong></span> into structured messages. Some of these meta data entries are listed in <a class="xref" href="#ex-verbose_journalctl_output">Example 17.16, “Verbose journalctl Output”</a>, for a complete list of journal fields see the <code class="filename">systemd.journal-fields(7)</code> manual page. For example, it is possible to focus on <span class="emphasis"><em>kernel journal fields</em></span>, that are used by messages originating in the kernel.
+ </div></div><div class="section" id="s2-filtering_structured_messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.6.2. Filtering Structured Messages</h3></div></div></div><div class="para">
+ To create a lumberjack-formatted message that is required by <span class="application"><strong>rsyslog</strong></span>'s parsing module, use the following template:
+ </div><pre class="screen">
+template(name="CEETemplate" type="string" string="%TIMESTAMP% %HOSTNAME% %syslogtag% @cee: %$!all-json%\n")
+</pre><div class="para">
+ This template prepends the <code class="literal">@cee:</code> string to the JSON string and can be applied, for example, when creating an output file with <code class="systemitem">omfile</code> module. To access JSON field names, use the <span class="bold bold"><strong>$!</strong></span> prefix. For example, the following filter condition searches for messages with specific <span class="emphasis"><em>hostname</em></span> and <span class="emphasis"><em>UID</em></span> :
+ </div><pre class="screen">
+($!hostname == "<em class="replaceable"><code>hostname</code></em>" && $!UID== "<em class="replaceable"><code>UID</code></em>")
+</pre></div><div class="section" id="s2-parsing_JSON"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.6.3. Parsing JSON</h3></div></div></div><div class="para">
+ The <code class="systemitem">mmjsonparse</code> module is used for parsing structured messages. These messages can come from <span class="application"><strong>Journal</strong></span> or from other input sources, and must be formatted in a way defined by the <span class="bold bold"><strong>Lumberjack</strong></span> project. These messages are identified by the presence of the <span class="bold bold"><strong>@cee:</strong></span> string. Then, <code class="systemitem">mmjsonparse</code> checks if the JSON structure is valid and then the message is parsed.
+ </div><div class="para">
+ To parse lumberjack-formatted JSON messages with <code class="systemitem">mmjsonparse</code>, use the following configuration in the <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad mmjsonparse
+
+*.* :mmjsonparse:
+</pre><div class="para">
+ In this example, the <code class="systemitem">mmjsonparse</code> module is loaded on the first line, then all messages are forwarded to it. Currently, there are no configuration parameters available for <code class="systemitem">mmjsonparse</code>.
+ </div></div><div class="section" id="s2-storing_messages_in_the_mongodb"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.6.4. Storing Messages in the MongoDB</h3></div></div></div><div class="para">
+ <span class="application"><strong>Rsyslog</strong></span> supports storing JSON logs in the <span class="database">MongoDB</span> document database through the <span class="emphasis"><em>ommongodb</em></span> output module.
+ </div><div class="para">
+ To forward log messages into <span class="database">MongoDB</span>, use the following syntax in the <code class="filename">/etc/rsyslog.conf</code> (configuration parameters for <span class="emphasis"><em>ommongodb</em></span> are available only in the new configuration format; see <a class="xref" href="#s2-using_the_new_configuration_format">Section 17.2.6, “Using the New Configuration Format”</a>):
+ </div><pre class="screen">
+$ModLoad ommongodb
+
+*.* action(type="ommongodb" server="<em class="replaceable"><code>DB_server</code></em>" serverport="<em class="replaceable"><code>port</code></em>" db="<em class="replaceable"><code>DB_name</code></em>" collection="<em class="replaceable"><code>collection_name</code></em>" uid="<em class="replaceable"><code>UID</code></em>" pwd="<em class="replaceable"><code>password</code></em>")
+</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Replace <em class="replaceable"><code>DB_server</code></em> with the name or address of the MongoDB server. Specify <em class="replaceable"><code>port</code></em> to select a non-standard port from the MongoDB server. The default <em class="replaceable"><code>port</code></em> value is <code class="literal">0</code> and usually there is no need to change this parameter.
+ </div></li><li class="listitem"><div class="para">
+ With <em class="replaceable"><code>DB_name</code></em>, you identify to which database on the MongoDB server you want to direct the output. Replace <em class="replaceable"><code>collection_name</code></em> with the name of a collection in this database. In <span class="database">MongoDB</span>, collection is a group of documents, the equivalent of an RDBMS table.
+ </div></li><li class="listitem"><div class="para">
+ You can set your login details by replacing <em class="replaceable"><code>UID</code></em> and <em class="replaceable"><code>password</code></em>.
+ </div></li></ul></div><div class="para">
+ You can shape the form of the final database output with use of templates. By default, <span class="application"><strong>ryslog</strong></span> uses a template based on standard <span class="application"><strong>lumberjack</strong></span> field names.
+ </div></div></div><div class="section" id="s1-debugging_rsyslog"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.7. Debugging Rsyslog</h2></div></div></div><div class="para">
+ To run <code class="systemitem">rsyslogd</code> in debugging mode, use the following command:
+ </div><pre class="synopsis"><code class="systemitem">rsyslogd</code> <code class="option">-dn</code></pre><div class="para">
+ With this command, <code class="systemitem">rsyslogd</code> produces debugging information and prints it to the standard output. The <code class="option">-n</code> stands for "no fork". You can modify debugging with environmental variables, for example, you can store the debug output in a log file. Before starting <code class="systemitem">rsyslogd</code>, type the following on the command line:
+ </div><pre class="screen">
+export RSYSLOG_DEBUGLOG="<em class="replaceable"><code>path</code></em>"
+export RSYSLOG_DEBUG="Debug"
+</pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a desired location for the file where the debugging information will be logged. For a complete list of options available for the RSYSLOG_DEBUG variable, see the related section in the <code class="filename">rsyslogd(8)</code> manual page.
+ </div><div class="para">
+ To check if syntax used in the <code class="filename">etc/rsyslog.conf</code> file is valid use:
+ </div><pre class="synopsis"><code class="systemitem">rsyslogd</code> <code class="option">-N</code> <code class="literal">1</code></pre><div class="para">
+ Where <code class="literal">1</code> represents level of verbosity of the output message. This is a forward compatibility option because currently, only one level is provided. However, you must add this argument to run the validation.
+ </div></div><div class="section" id="s1-Using_the_Journal"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.8. Using the Journal</h2></div></div></div><div class="para">
+ The Journal is a component of <span class="application"><strong>systemd</strong></span> that is responsible for viewing and management of log files. It can be used in parallel, or in place of a traditional syslog daemon, such as <code class="systemitem">rsyslogd</code>. The Journal was developed to address problems connected with traditional logging. It is closely integrated with the rest of the system, supports various logging technologies and access management for the log files.
+ </div><div class="para">
+ Logging data is collected, stored, and processed by the Journal's <code class="systemitem">journald</code> service. It creates and maintains binary files called <span class="emphasis"><em>journals</em></span> based on logging information that is received from the kernel, from user processes, from standard output, and standard error output of system services or via its native API. These journals are structured and indexed, which provides relatively fast seek times. Journal entries can carry a unique identifier. The <code class="systemitem">journald</code> service collects numerous meta data fields for each log message. The actual journal files are secured, and therefore cannot be manually edited.
+ </div><div class="section" id="s2-Viewing_Log_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.8.1. Viewing Log Files</h3></div></div></div><div class="para">
+ To access the journal logs, use the <span class="application"><strong>journalctl</strong></span> tool. For a basic view of the logs type as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code class="command">journalctl</code></pre><div class="para">
+ An output of this command is a list of all log files generated on the system including messages generated by system components and by users. The structure of this output is similar to one used in <code class="filename">/var/log/messages/</code> but with certain improvements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ the priority of entries is marked visually. Lines of error priority and higher are highlighted with red color and a bold font is used for lines with notice and warning priority
+ </div></li><li class="listitem"><div class="para">
+ the time stamps are converted for the local time zone of your system
+ </div></li><li class="listitem"><div class="para">
+ all logged data is shown, including rotated logs
+ </div></li><li class="listitem"><div class="para">
+ the beginning of a boot is tagged with a special line
+ </div></li></ul></div><div class="example" id="ex-Example_Output_of_journalctl"><h6>Example 17.15. Example Output of journalctl</h6><div class="example-contents"><div class="para">
+ The following is an example output provided by the <span class="application"><strong>journalctl</strong></span> tool. When called without parameters, the listed entries begin with a time stamp, then the host name and application that performed the operation is mentioned followed by the actual message. This example shows the first three entries in the journal log:
+ </div><pre class="screen">
+# <code class="command">journalctl</code>
+-- Logs begin at Thu 2013-08-01 15:42:12 CEST, end at Thu 2013-08-01 15:48:48 CEST. --
+Aug 01 15:42:12 localhost systemd-journal[54]: Allowing runtime journal files to grow to 49.7M.
+Aug 01 15:42:12 localhost kernel: Initializing cgroup subsys cpuset
+Aug 01 15:42:12 localhost kernel: Initializing cgroup subsys cpu
+
+[...]
+</pre></div></div><br class="example-break" /><div class="para">
+ In many cases, only the latest entries in the journal log are relevant. The simplest way to reduce <code class="command">journalctl</code> output is to use the <code class="option">-n</code> option that lists only the specified number of most recent log entries:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-n</code> <em class="replaceable"><code>Number</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>Number</code></em> with the number of lines to be shown. When no number is specified, <code class="command">journalctl</code> displays the ten most recent entries.
+ </div><div class="para">
+ The <code class="command">journalctl</code> command allows controlling the form of the output with the following syntax:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-o</code> <em class="replaceable"><code>form</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>form</code></em> with a keyword specifying a desired form of output. There are several options, such as <code class="option">verbose</code>, which returns full-structured entry items with all fields, <code class="option">export</code>, which creates a binary stream suitable for backups and network transfer, and <code class="option">json</code>, which formats entries as JSON data structures. For the full list of keywords, see the <code class="filename">journalctl(1)</code> manual page.
+ </div><div class="example" id="ex-verbose_journalctl_output"><h6>Example 17.16. Verbose journalctl Output</h6><div class="example-contents"><div class="para">
+ To view full meta data about all entries, type:
+ </div><pre class="screen">
+# <code class="command">journalctl</code> <code class="option">-o verbose</code>
+[...]
+
+Fri 2013-08-02 14:41:22 CEST [s=e1021ca1b81e4fc688fad6a3ea21d35b;i=55c;b=78c81449c920439da57da7bd5c56a770;m=27cc
+ _BOOT_ID=78c81449c920439da57da7bd5c56a770
+ PRIORITY=5
+ SYSLOG_FACILITY=3
+ _TRANSPORT=syslog
+ _MACHINE_ID=69d27b356a94476da859461d3a3bc6fd
+ _HOSTNAME=localhost.localdomain
+ _PID=562
+ _COMM=dbus-daemon
+ _EXE=/usr/bin/dbus-daemon
+ _CMDLINE=/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
+ _SYSTEMD_CGROUP=/system/dbus.service
+ _SYSTEMD_UNIT=dbus.service
+ SYSLOG_IDENTIFIER=dbus
+ SYSLOG_PID=562
+ _UID=81
+ _GID=81
+ _SELINUX_CONTEXT=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023
+ MESSAGE=[system] Successfully activated service 'net.reactivated.Fprint'
+ _SOURCE_REALTIME_TIMESTAMP=1375447282839181
+
+[...]
+</pre><div class="para">
+ This example lists fields that identify a single log entry. These meta data can be used for message filtering as shown in <a class="xref" href="#advanced_filtering">the section called “Advanced Filtering”</a>. For a complete description of all possible fields see the <code class="filename">systemd.journal-fields(7)</code> manual page.
+ </div></div></div><br class="example-break" /></div><div class="section" id="s2-Access_Control"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.8.2. Access Control</h3></div></div></div><div class="para">
+ By default, <span class="application"><strong>Journal</strong></span> users without <code class="systemitem">root</code> privileges can only see log files generated by them. The system administrator can add selected users to the <span class="emphasis"><em>adm</em></span> group, which grants them access to complete log files. To do so, type as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code class="command">usermod</code> <code class="option">-a</code> <code class="option">-G</code> <span class="emphasis"><em>adm</em></span> <em class="replaceable"><code>username</code></em></pre><div class="para">
+ Here, replace <em class="replaceable"><code>username</code></em> with a name of the user to be added to the <span class="emphasis"><em>adm</em></span> group. This user then receives the same output of the <code class="command">journalctl</code> command as the root user. Note that access control only works when persistent storage is enabled for <span class="application"><strong>Journal</strong></span>.
+ </div></div><div class="section" id="s2-Using_The_Live_View"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.8.3. Using The Live View</h3></div></div></div><div class="para">
+ When called without parameters, <code class="command">journalctl</code> shows the full list of entries, starting with the oldest entry collected. With the live view, you can supervise the log messages in real time as new entries are continuously printed as they appear. To start <span class="application"><strong>journalctl</strong></span> in live view mode, type:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-f</code></pre><div class="para">
+ This command returns a list of the ten most current log lines. The <span class="application"><strong>journalctl</strong></span> utility then stays running and waits for new changes to show them immediately.
+ </div></div><div class="section" id="s2-Filtering_Messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.8.4. Filtering Messages</h3></div></div></div><div class="para">
+ The output of the <code class="command">journalctl</code> command executed without parameters is often extensive, therefore you can use various filtering methods to extract information to meet your needs.
+ </div><h4 id="filtering_by_priority">Filtering by Priority</h4><div class="para">
+ Log messages are often used to track erroneous behavior on the system. To view only entries with a selected or higher priority, use the following syntax:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-p</code> <em class="replaceable"><code>priority</code></em></pre><div class="para">
+ Here, replace <em class="replaceable"><code>priority</code></em> with one of the following keywords (or with a number): <code class="command">debug</code> (7), <code class="command">info</code> (6), <code class="command">notice</code> (5), <code class="command">warning</code> (4), <code class="command">err</code> (3), <code class="command">crit</code> (2), <code class="command">alert</code> (1), and <code class="command">emerg</code> (0).
+ </div><div class="example" id="ex-filtering_by_priority"><h6>Example 17.17. Filtering by Priority</h6><div class="example-contents"><div class="para">
+ To view only entries with <span class="emphasis"><em>error</em></span> or higher priority, use:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-p err</code></pre></div></div><br class="example-break" /><h4 id="filtering_by_time">Filtering by Time</h4><div class="para">
+ To view log entries only from the current boot, type:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-b</code></pre><div class="para">
+ If you reboot your system just occasionally, the <code class="option">-b</code> will not significantly reduce the output of <code class="command">journalctl</code>. In such cases, time-based filtering is more helpful:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">--since</code>=<em class="replaceable"><code>value</code></em> <code class="option">--until</code>=<em class="replaceable"><code>value</code></em></pre><div class="para">
+ With <code class="option">--since</code> and <code class="option">--until</code>, you can view only log messages created within a specified time range. You can pass <em class="replaceable"><code>values</code></em> to these options in form of date or time or both as shown in the following example.
+ </div><div class="example" id="ex-filtering_by_time_and_priority"><h6>Example 17.18. Filtering by Time and Priority</h6><div class="example-contents"><div class="para">
+ Filtering options can be combined to reduce the set of results according to specific requests. For example, to view the <span class="emphasis"><em>warning</em></span> or higher priority messages from a certain point in time, type:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-p warning</code> <code class="option">--since="2013-3-16 23:59:59"</code></pre></div></div><br class="example-break" /><h4 id="advanced_filtering">Advanced Filtering</h4><div class="para">
+ <a class="xref" href="#ex-verbose_journalctl_output">Example 17.16, “Verbose journalctl Output”</a> lists a set of fields that specify a log entry and can all be used for filtering. For a complete description of meta data that <code class="systemitem">systemd</code> can store, see the <code class="filename">systemd.journal-fields(7)</code> manual page. This meta data is collected for each log message, without user intervention. Values are usually text-based, but can take binary and large values; fields can have multiple values assigned though it is not very common.
+ </div><div class="para">
+ To view a list of unique values that occur in a specified field, use the following syntax:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-F</code> <em class="replaceable"><code>fieldname</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>fieldname</code></em> with a name of a field you are interested in.
+ </div><div class="para">
+ To show only log entries that fit a specific condition, use the following syntax:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <em class="replaceable"><code>fieldname</code></em>=<em class="replaceable"><code>value</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>fieldname</code></em> with a name of a field and <em class="replaceable"><code>value</code></em> with a specific value contained in that field. As a result, only lines that match this condition are returned.
+ </div><div class="note"><div class="admonition_header"><h2><span class="keycap"><strong>Tab</strong></span> Completion on Field Names</h2></div><div class="admonition"><div class="para">
+ As the number of meta data fields stored by <code class="systemitem">systemd</code> is quite large, it is easy to forget the exact name of the field of interest. When unsure, type:
+ </div><pre class="synopsis"><code class="command">journalctl</code></pre><div class="para">
+ and press the <span class="keycap"><strong>Tab</strong></span> key two times. This shows a list of available field names. <span class="keycap"><strong>Tab</strong></span> completion based on context works on field names, so you can type a distinctive set of letters from a field name and then press <span class="keycap"><strong>Tab</strong></span> to complete the name automatically. Similarly, you can list unique values from a field. Type:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <em class="replaceable"><code>fieldname</code></em>=</pre><div class="para">
+ and press <span class="keycap"><strong>Tab</strong></span> two times. This serves as an alternative to <code class="command">journalctl</code> <code class="option">-F</code> <em class="replaceable"><code>fieldname</code></em>.
+ </div></div></div><div class="para">
+ You can specify multiple values for one field:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <em class="replaceable"><code>fieldname</code></em>=<em class="replaceable"><code>value1</code></em> <em class="replaceable"><code>fieldname</code></em>=<em class="replaceable"><code>value2</code></em> ...</pre><div class="para">
+ Specifying two matches for the same field results in a logical <code class="function">OR</code> combination of the matches. Entries matching <em class="replaceable"><code>value1</code></em> or <em class="replaceable"><code>value2</code></em> are displayed.
+ </div><div class="para">
+ Also, you can specify multiple field-value pairs to further reduce the output set:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <em class="replaceable"><code>fieldname1</code></em>=<em class="replaceable"><code>value</code></em> <em class="replaceable"><code>fieldname2</code></em>=<em class="replaceable"><code>value</code></em> ...</pre><div class="para">
+ If two matches for different field names are specified, they will be combined with a logical <code class="function">AND</code>. Entries have to match both conditions to be shown.
+ </div><div class="para">
+ With use of the <span class="emphasis"><em>+</em></span> symbol, you can set a logical <code class="function">OR</code> combination of matches for multiple fields:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <em class="replaceable"><code>fieldname1</code></em>=<em class="replaceable"><code>value</code></em> + <em class="replaceable"><code>fieldname2</code></em>=<em class="replaceable"><code>value</code></em> ...</pre><div class="para">
+ This command returns entries that match at least one of the conditions, not only those that match both of them.
+ </div><div class="example" id="ex-advanced_filtering"><h6>Example 17.19. Advanced filtering</h6><div class="example-contents"><div class="para">
+ To display entries created by <code class="systemitem">avahi-daemon.service</code> or <code class="systemitem">crond.service</code> under user with UID 70, use the following command:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="literal">_UID=70</code> <code class="literal">_SYSTEMD_UNIT=avahi-daemon.service</code> <code class="literal">_SYSTEMD_UNIT=crond.service</code></pre><div class="para">
+ Since there are two values set for the <code class="literal">_SYSTEMD_UNIT</code> field, both results will be displayed, but only when matching the <code class="literal">_UID=70</code> condition. This can be expressed simply as: (UID=70 and (avahi or cron)).
+ </div></div></div><br class="example-break" /><div class="para">
+ You can apply the aforementioned filtering also in the live-view mode to keep track of the latest changes in the selected group of log entries:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-f</code> <em class="replaceable"><code>fieldname</code></em>=<em class="replaceable"><code>value</code></em> ...</pre></div><div class="section" id="s2-Enabling_Persistent_Storage"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.8.5. Enabling Persistent Storage</h3></div></div></div><div class="para">
+ By default, <span class="application"><strong>Journal</strong></span> stores log files only in memory or a small ring-buffer in the <code class="filename">/run/log/journal/</code> directory. This is sufficient to show recent log history with <code class="command">journalctl</code>. This directory is volatile, log data is not saved permanently. With the default configuration, syslog reads the journal logs and stores them in the <code class="filename">/var/log/</code> directory. With persistent logging enabled, journal files are stored in <code class="filename">/var/log/journal</code> which means they persist after reboot. Journal can then replace <span class="application"><strong>rsyslog</strong></span> for some users (but see the chapter introduction).
+ </div><div class="para">
+ Enabled persistent storage has the following advantages
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Richer data is recorded for troubleshooting in a longer period of time
+ </div></li><li class="listitem"><div class="para">
+ For immediate troubleshooting, richer data is available after a reboot
+ </div></li><li class="listitem"><div class="para">
+ Server console currently reads data from journal, not log files
+ </div></li></ul></div><div class="para">
+ Persistent storage has also certain disadvantages:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Even with persistent storage the amount of data stored depends on free memory, there is no guarantee to cover a specific time span
+ </div></li><li class="listitem"><div class="para">
+ More disk space is needed for logs
+ </div></li></ul></div><div class="para">
+ To enable persistent storage for Journal, create the journal directory manually as shown in the following example. As <code class="systemitem">root</code> type:
+ </div><pre class="synopsis"><code class="command">mkdir</code> <code class="option">-p</code> <code class="filename">/var/log/journal</code></pre><div class="para">
+ Then, restart <code class="systemitem">journald</code> to apply the change:
+ </div><pre class="synopsis"><code class="command">systemctl</code> <code class="option">restart</code> <code class="systemitem">systemd-journald</code></pre></div></div><div class="section" id="s1-managing_log_files_in_a_graphical_environment"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.9. Managing Log Files in a Graphical Environment</h2></div></div></div><div class="para">
+ As an alternative to the aforementioned command-line utilities, Red Hat Enterprise Linux 7 provides an accessible GUI for managing log messages.
+ </div><div class="section" id="s2-logfiles-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.9.1. Viewing Log Files</h3></div></div></div><a id="idm261780317936" class="indexterm"></a><div class="para">
+ Most log files are stored in plain text format. You can view them with any text editor such as <code class="command">Vi</code> or <span class="application"><strong>Emacs</strong></span>. Some log files are readable by all users on the system; however, root privileges are required to read most log files.
+ </div><a id="idm261780314864" class="indexterm"></a><div class="para">
+ To view system log files in an interactive, real-time application, use the <span class="application"><strong>System Log</strong></span>.
+ </div><div class="note"><div class="admonition_header"><h2>Installing the gnome-system-log package</h2></div><div class="admonition"><div class="para">
+ In order to use the <span class="application"><strong>System Log</strong></span>, first ensure the <span class="package">gnome-system-log</span> package is installed on your system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">yum install gnome-system-log</code>
+</pre><div class="para">
+ For more information on installing packages with Yum, see <a class="xref" href="#sec-Installing">Section 5.2.4, “Installing Packages”</a>.
+ </div></div></div><div class="para">
+ After you have installed the <span class="package">gnome-system-log</span> package, open the <span class="application"><strong>System Log</strong></span> by clicking <span class="guimenu"><strong>Applications</strong></span> → <span class="guimenuitem"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Log</strong></span>, or type the following command at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">gnome-system-log</code>
+</pre><div class="para">
+ The application only displays log files that exist; thus, the list might differ from the one shown in <a class="xref" href="#fig-redhat-logviewer">Figure 17.2, “System Log”</a>.
+ </div><a id="idm261744226736" class="indexterm"></a><a id="idm261715153296" class="indexterm"></a><div class="figure" id="fig-redhat-logviewer"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer.png" width="444" alt="System Log" /><div class="longdesc"><div class="para">
+ System Log
+ </div></div></div></div><h6>Figure 17.2. System Log</h6></div><br class="figure-break" /><a id="idm261722689184" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>System Log</strong></span> application lets you filter any existing log file. Click on the button marked with the gear symbol to view the menu, select <span class="guimenuitem"><strong>Filters</strong></span> → <span class="guimenuitem"><strong>Manage Filters</strong></span> to define or edit the desired filter.
+ </div><div class="figure" id="fig-redhat-filters"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-filters.png" alt="System Log - Filters" /><div class="longdesc"><div class="para">
+ System Log - Filters
+ </div></div></div></div><h6>Figure 17.3. System Log - 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.4, “System Log - defining a filter”</a>.
+ </div><div class="figure" id="fig-redhat-filter-sample"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-filter-sample.png" alt="System Log - defining a filter" /><div class="longdesc"><div class="para">
+ System Log - Defining a Filter
+ </div></div></div></div><h6>Figure 17.4. System Log - defining a filter</h6></div><br class="figure-break" /><div class="para">
+ When defining a filter, the following parameters can be edited:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>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, it can be selected from the <span class="guilabel"><strong>Filters</strong></span> menu and it will automatically search for the strings you have defined in the filter and highlight or hide every successful match in the log file you are currently viewing.
+ </div><div class="figure" id="fig-redhat-filter-enable"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-filter-enable.png" width="444" alt="System Log - enabled filter" /><div class="longdesc"><div class="para">
+ System Log - Enabling a Filter
+ </div></div></div></div><h6>Figure 17.5. System Log - enabled filter</h6></div><br class="figure-break" /><div class="para">
+ When you select the <span class="guilabel"><strong>Show matches only</strong></span> option, only the matched strings will be shown in the log file you are currently viewing.
+ </div></div><div class="section" id="s2-logfiles-adding"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.9.2. Adding a Log File</h3></div></div></div><div class="para">
+ To add a log file you want to view in the list, select <span class="guimenu"><strong>File</strong></span> → <span class="guimenuitem"><strong>Open</strong></span>. This will display the <span class="guilabel"><strong>Open Log</strong></span> window where you can select the directory and file name of the log file you want to view. <a class="xref" href="#fig-redhat-logviewer-add">Figure 17.6, “System Log - adding a log file”</a> illustrates the <span class="guimenu"><strong>Open Log</strong></span> window.
+ </div><div class="figure" id="fig-redhat-logviewer-add"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-add.png" width="444" alt="System Log - adding a log file" /><div class="longdesc"><div class="para">
+ System Log - Adding a Log File
+ </div></div></div></div><h6>Figure 17.6. System Log - adding a log file</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Open</strong></span> button to open the file. The file is immediately added to the viewing list where you can select it and view its contents.
+ </div><div class="note"><div class="admonition_header"><h2>Reading zipped log files</h2></div><div class="admonition"><div class="para">
+ The <span class="application"><strong>System Log</strong></span> also allows you to open log files zipped in the <code class="literal">.gz</code> format.
+ </div></div></div></div><div class="section" id="s2-logfiles-examining"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.9.3. Monitoring Log Files</h3></div></div></div><a id="idm261757560096" class="indexterm"></a><a id="idm261757558656" class="indexterm"></a><div class="para">
+ <span class="application"><strong>System Log</strong></span> monitors all opened logs by default. If a new line is added to a monitored log file, the log name appears in bold in the log list. If the log file is selected or displayed, the new lines appear in bold at the bottom of the log file. <a class="xref" href="#fig-redhat-logviewer-monitoring">Figure 17.7, “System Log - new log alert”</a> illustrates a new alert in the <span class="guilabel"><strong>cron</strong></span> log file and in the <span class="guilabel"><strong>messages</strong></span> log file. Clicking on the <span class="guimenuitem"><strong>messages</strong></span> log file displays the logs in the file with the new lines in bold.
+ </div><div class="figure" id="fig-redhat-logviewer-monitoring"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-monitoring.png" width="444" alt="System Log - new log alert" /><div class="longdesc"><div class="para">
+ System Log - New Log Alert
+ </div></div></div></div><h6>Figure 17.7. System Log - new log alert</h6></div><br class="figure-break" /></div></div><div class="section" id="s1-log-files-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.10. Additional Resources</h2></div></div></div><div class="para">
+ For more information on how to configure the <code class="systemitem">rsyslog</code> daemon and how to locate, view, and monitor log files, see the resources listed below.
+ </div><h3 id="brid-Log_Files-Resources-Installed">Installed Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">rsyslogd</code>(8) — The manual page for the <code class="systemitem">rsyslogd</code> daemon documents its usage.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">rsyslog.conf</code>(5) — The manual page named <code class="systemitem">rsyslog.conf</code> documents available configuration options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">logrotate</code>(8) — The manual page for the <span class="application"><strong>logrotate</strong></span> utility explains in greater detail how to configure and use it.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">journalctl</code>(1) — The manual page for the <code class="command">journalctl</code> daemon documents its usage.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">journald.conf</code>(5) — This manual page documents available configuration options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">systemd.journal-fields</code>(7) — This manual page lists special <span class="application"><strong>Journal</strong></span> fields.
+ </div></li></ul></div><h3 id="brid-Log_Files-Resources-Online">Online Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.rsyslog.com/">rsyslog Home Page</a> — The <span class="application"><strong>rsyslog</strong></span> home page offers a thorough technical breakdown of its features, documentation, configuration examples, and video tutorials.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.rsyslog.com/doc/rainerscript.html"><span class="emphasis"><em>RainerScript</em></span> documentation on the rsyslog Home Page</a> — Commented summary of data types, expressions, and functions available in <span class="emphasis"><em>RainerScript</em></span>.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.rsyslog.com/doc/queues.html">Description of <span class="emphasis"><em>queues</em></span> on the rsyslog Home Page</a> — General information on various types of message queues and their usage.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://wiki.rsyslog.com/index.php/Main_Page">rsyslog Wiki</a> — <em class="citetitle">The rsyslog Wiki</em> contains useful configuration examples.
+ </div></li></ul></div></div></div><div xml:lang="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 class="toc"><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="#sect-Cron-Installing">18.1.1. Installing Cron and Anacron</a></span></dt><dt><span class="section"><a href="#sect-Cron-Running">18.1.2. Running the Crond Service</a></span></dt><dt><span class="section"><a href="#s2-configuring-anacron-jobs">18.1.3. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="#s2-configuring-cron-jobs">18.1.4. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-cron-access">18.1.5. Controlling Access to Cron</a></span></dt><dt><span class="section"><a href="#s2-black-white-listing-of-cron-job
s">18.1.6. Black and 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="#sect-At_and_Batch_Installation">18.2.1. Installing At and Batch</a></span></dt><dt><span class="section"><a href="#sect-Atd-Running">18.2.2. Running the At Service</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-configuring">18.2.3. Configuring an At Job</a></span></dt><dt><span class="section"><a href="#s2-autotasks-batch-configuring">18.2.4. Configuring a Batch Job</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-viewing">18.2.5. Viewing Pending Jobs</a></span></dt><dt><span class="section"><a href="#s2-autotasks-commandline-options">18.2.6. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="#s2-autotasks-at-batch-controlling-access">18.2.7. Controlling Access to At and Batch</a></span></dt></d
l></dd><dt><span class="section"><a href="#s1-autotasks-additional-resources">18.3. Additional Resources</a></span></dt></dl></div><a id="idm261743745904" class="indexterm"></a><div class="para">
+ Tasks, also known as <em class="firstterm">jobs</em>, can be configured to run automatically within a specified period of time, on a specified date, or when the system load average decreases below 0.8.
+ </div><div class="para">
+ Fedora is pre-configured to run important system tasks to keep the system updated. For example, the <span class="database">slocate</span> database used by the <code class="command">locate</code> command is updated daily. A system administrator can use automated tasks to perform periodic backups, monitor the system, run custom scripts, and so on.
+ </div><div class="para">
+ Fedora comes with the following automated task utilities: <code class="command">cron</code>, <code class="command">anacron</code>, <code class="command">at</code>, and <code class="command">batch</code>.
+ </div><div class="para">
+ Every utility is intended for scheduling a different job type: while Cron and Anacron schedule recurring jobs, At and Batch schedule one-time jobs (refer to <a class="xref" href="#s1-autotasks-cron-anacron">Section 18.1, “Cron and Anacron”</a> and <a class="xref" href="#s1-autotasks-at-batch">Section 18.2, “At and Batch”</a> respectively).
+ </div><div class="para">
+ Fedora supports the use of <code class="systemitem">systemd.timer</code> for executing a job at a specific time. See man <code class="filename">systemd.timer(5)</code> for more information.
+ </div><div class="section" id="s1-autotasks-cron-anacron"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.1. Cron and Anacron</h2></div></div></div><a id="idm261782821696" class="indexterm"></a><a id="idm261745989184" class="indexterm"></a><div class="para">
+ Both Cron and Anacron are daemons that can schedule execution of recurring tasks to a certain point in time defined by the exact time, day of the month, month, day of the week, and week.
+ </div><div class="para">
+ Cron jobs can run as often as every minute. However, the utility assumes that the system is running continuously and if the system is not on at the time when a job is scheduled, the job is not executed.
+ </div><div class="para">
+ On the other hand, Anacron remembers the scheduled jobs if the system is not running at the time when the job is scheduled. The job is then executed as soon as the system is up. However, Anacron can only run a job once a day.
+ </div><div class="section" id="sect-Cron-Installing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.1. Installing Cron and Anacron</h3></div></div></div><div class="para">
+ To install Cron and Anacron, you need to install the <span class="package">cronie</span> package with Cron and the <span class="package">cronie-anacron</span> package with Anacron (<span class="package">cronie-anacron</span> is a sub-package of <span class="package">cronie</span>).
+ </div><div class="para">
+ To determine if the packages are already installed on your system, issue the following command:
+ </div><pre class="synopsis"><code class="command">rpm -q cronie cronie-anacron</code></pre><div class="para">
+ The command returns full names of the <span class="package">cronie</span> and <span class="package">cronie-anacron</span> packages if already installed, or notifies you that the packages are not available.
+ </div><div class="para">
+ To install these packages, use the <code class="command">yum</code> command in the following form as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code class="command">yum install <em class="replaceable"><code>package</code></em></code></pre><div class="para">
+ For example, to install both Cron and Anacron, type the following at a shell prompt:
+ </div><pre class="screen">~]# <code class="command">yum install cronie cronie-anacron</code></pre><div class="para">
+ For more information on how to install new packages in Fedora, see <a class="xref" href="#sec-Installing">Section 5.2.4, “Installing Packages”</a>.
+ </div></div><div class="section" id="sect-Cron-Running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.2. Running the Crond Service</h3></div></div></div><div class="para">
The cron and anacron jobs are both picked by the <code class="systemitem">crond</code> service. This section provides information on how to start, stop, and restart the <code class="systemitem">crond</code> service, and shows how to configure it to start automatically at boot time.
</div><div class="section" id="sect-Cron-service"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">18.1.2.1. Starting and Stopping the Cron Service</h4></div></div></div><div class="para">
To determine if the service is running, use the following command:
@@ -9021,7 +9856,7 @@ compress
To restart the <code class="systemitem">crond</code> service, type the following at a shell prompt as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">systemctl restart crond.service</code></pre><div class="para">
This command stops the service and starts it again in quick succession.
- </div></div></div><div class="section" id="s2-configuring-anacron-jobs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.3. Configuring Anacron Jobs</h3></div></div></div><a id="idm225471886320" class="indexterm"></a><a id="idm225357244128" class="indexterm"></a><a id="idm225357242688" class="indexterm"></a><a id="idm225449730320" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s2-configuring-anacron-jobs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.3. Configuring Anacron Jobs</h3></div></div></div><a id="idm261751651664" class="indexterm"></a><a id="idm261751650256" class="indexterm"></a><a id="idm261750728096" class="indexterm"></a><a id="idm261750726656" class="indexterm"></a><div class="para">
The main configuration file to schedule jobs is the <code class="filename">/etc/anacrontab</code> file, which can be only accessed by the <code class="systemitem">root</code> user. The file contains the following:
</div><pre class="programlisting">SHELL=/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin
@@ -9098,7 +9933,7 @@ START_HOURS_RANGE=16-20
The second job executes the <code class="filename">weeklyjob.bash</code> script in the <code class="filename">/etc/</code> directory once a week.
</div><div class="para">
The third job runs a command, which writes the contents of <code class="filename">/proc</code> to the <code class="filename">/tmp/proc</code> file (<code class="command">ls /proc >> /tmp/proc</code>) once a month.
- </div></div></div><div class="section" id="s2-configuring-cron-jobs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.4. Configuring Cron Jobs</h3></div></div></div><a id="idm225412070720" class="indexterm"></a><a id="idm225412069280" class="indexterm"></a><a id="idm225445662400" class="indexterm"></a><a id="idm225445660960" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s2-configuring-cron-jobs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.4. Configuring Cron Jobs</h3></div></div></div><a id="idm261744693440" class="indexterm"></a><a id="idm261741317360" class="indexterm"></a><a id="idm261741315920" class="indexterm"></a><a id="idm261724566976" class="indexterm"></a><div class="para">
The configuration file for cron jobs is <code class="filename">/etc/crontab</code>, which can be only modified by the <code class="systemitem">root</code> user. The file contains the following:
</div><pre class="programlisting">SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
@@ -9178,7 +10013,7 @@ HOME=/
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.5, “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">18.2. At and Batch</h2></div></div></div><a id="idm225464453216" class="indexterm"></a><a id="idm225464451776" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s1-autotasks-at-batch"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.2. At and Batch</h2></div></div></div><a id="idm261732220400" class="indexterm"></a><a id="idm261732218960" class="indexterm"></a><div class="para">
While Cron is used to schedule recurring tasks, the <span class="application"><strong>At</strong></span> utility is used to schedule a one-time task at a specific time and the <span class="application"><strong>Batch</strong></span> utility is used to schedule a one-time task to be executed when the system load average drops below 0.8.
</div><div class="section" id="sect-At_and_Batch_Installation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.2.1. Installing At and Batch</h3></div></div></div><div class="para">
To determine if the <span class="package">at</span> package is already installed on your system, issue the following command:
@@ -9308,7 +10143,7 @@ HOME=/
The <code class="command">at</code> daemon (<code class="command">atd</code>) does not have to be restarted if the access control files are modified. The access control files are read each time a user tries to execute the <code class="command">at</code> or <code class="command">batch</code> commands.
</div><div class="para">
The <code class="systemitem">root</code> user can always execute <code class="command">at</code> and <code class="command">batch</code> commands, regardless of the content of the access control files.
- </div></div></div><div class="section" id="s1-autotasks-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.3. Additional Resources</h2></div></div></div><a id="idm225438559040" class="indexterm"></a><a id="idm225438557600" class="indexterm"></a><a id="idm225424401888" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s1-autotasks-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.3. Additional Resources</h2></div></div></div><a id="idm261757198528" class="indexterm"></a><a id="idm261757197088" class="indexterm"></a><a id="idm261755917360" class="indexterm"></a><div class="para">
To learn more about configuring automated tasks, see the following installed documentation:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="filename">cron(8)</code> man page contains an overview of cron.
@@ -9328,14 +10163,14 @@ HOME=/
<code class="filename">/usr/share/doc/at/timespec</code> contains detailed information about the time values that can be used in cron job definitions.
</div></li><li class="listitem"><div class="para">
<code class="filename">at</code> manual page contains descriptions of <code class="command">at</code> and <code class="command">batch</code> and their command line options.
- </div></li></ul></div></div></div><div xml:lang="en-US" class="chapter" id="ch-OProfile" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 19. OProfile</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-oprofile-overview-tools">19.1. Overview of Tools</a></span></dt><dt><span class="section"><a href="#s1-oprofile-configuring">19.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-kernel">19.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="#s2-oprofile-events">19.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="#s2-oprofile-starting-separate">19.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-starting">19.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="#s1-oprofile-saving-data">19.4. Saving Data</a>
</span></dt><dt><span class="section"><a href="#s1-oprofile-analyzing-data">19.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-reading-opreport">19.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opreport-single">19.5.2. Using opreport on a Single Executable</a></span></dt><dt><span class="section"><a href="#s2-oprofile-module-output">19.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opannotate">19.5.4. Using <code class="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-dev-oprofile">19.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="#s1-oprofile-example-usage">19.7. Example Usage</a></span></dt><dt><span class="section"><a href="#s1-oprofile-java-support">19.8. OProfile S
upport for Java</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-java-profiling">19.8.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-gui">19.9. Graphical Interface</a></span></dt><dt><span class="section"><a href="#s1-oprofile-and-systemtap">19.10. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="#s1-oprofile-additional-resources">19.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-installed-docs">19.11.1. Installed Docs</a></span></dt><dt><span class="section"><a href="#s2-oprofile-useful-websites">19.11.2. Useful Websites</a></span></dt></dl></dd></dl></div><a id="idm225476046640" class="indexterm"></a><a id="idm225467953184" class="indexterm"></a><div class="para">
+ </div></li></ul></div></div></div><div xml:lang="en-US" class="chapter" id="ch-OProfile" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 19. OProfile</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-oprofile-overview-tools">19.1. Overview of Tools</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-operf_vs_opcontrol">19.1.1. operf vs. opcontrol</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-using-operf">19.2. Using operf</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-operf-kernel">19.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="#s2-operf-events">19.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="#s2-operf-categorization">19.2.3. Categorization of Samples</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-configuring">19.3. Configuring OProfile Using Legacy Mode</a></span></
dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-kernel">19.3.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="#s2-oprofile-events">19.3.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="#s2-oprofile-starting-separate">19.3.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-starting">19.4. Starting and Stopping OProfile Using Legacy Mode</a></span></dt><dt><span class="section"><a href="#s1-oprofile-saving-data">19.5. Saving Data in Legacy Mode</a></span></dt><dt><span class="section"><a href="#s1-oprofile-analyzing-data">19.6. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="#s2-oprofile-reading-opreport">19.6.1. Using <code class="command">opreport</code></a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opreport-single">19.6.2. Using opreport on a Single Executable</a></span></dt><dt><span clas
s="section"><a href="#s2-oprofile-module-output">19.6.3. Getting More Detailed Output on the Modules</a></span></dt><dt><span class="section"><a href="#s2-oprofile-reading-opannotate">19.6.4. Using <code class="command">opannotate</code></a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-dev-oprofile">19.7. Understanding the /dev/oprofile/ directory </a></span></dt><dt><span class="section"><a href="#s1-oprofile-example-usage">19.8. Example Usage</a></span></dt><dt><span class="section"><a href="#s1-oprofile-java-support">19.9. OProfile Support for Java</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-oprofile-java-profiling">19.9.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-oprofile-gui">19.10. Graphical Interface</a></span></dt><dt><span class="section"><a href="#s1-oprofile-and-systemtap">19.11. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="#s1-oprofile_additional_resou
rces">19.12. Additional Resources</a></span></dt></dl></div><a id="idm261735313392" class="indexterm"></a><a id="idm261740589840" class="indexterm"></a><div class="para">
OProfile is a low overhead, system-wide performance monitoring tool. It uses the performance monitoring hardware on the processor to retrieve information about the kernel and executables on the system, such as when memory is referenced, the number of L2 cache requests, and the number of hardware interrupts received. On a Fedora system, the <code class="filename">oprofile</code> package must be installed to use this tool.
</div><div class="para">
- Many processors include dedicated performance monitoring hardware. This hardware makes it possible to detect when certain events happen (such as the requested data not being in cache). The hardware normally takes the form of one or more <em class="firstterm">counters</em> that are incremented each time an event takes place. When the counter value, essentially rolls over, an interrupt is generated, making it possible to control the amount of detail (and therefore, overhead) produced by performance monitoring.
+ Many processors include dedicated performance monitoring hardware. This hardware makes it possible to detect when certain events happen (such as the requested data not being in cache). The hardware normally takes the form of one or more <em class="firstterm">counters</em> that are incremented each time an event takes place. When the counter value increments, an interrupt is generated, making it possible to control the amount of detail (and therefore, overhead) produced by performance monitoring.
</div><div class="para">
OProfile uses this hardware (or a timer-based substitute in cases where performance monitoring hardware is not present) to collect <em class="firstterm">samples</em> of performance-related data each time a counter generates an interrupt. These samples are periodically written out to disk; later, the data contained in these samples can then be used to generate reports on system-level and application-level performance.
</div><div class="para">
- OProfile is a useful tool, but be aware of some limitations when using it:
+ Be aware of the following limitations when using OProfile:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<span class="emphasis"><em>Use of shared libraries</em></span> — Samples for code in shared libraries are not attributed to the particular application unless the <code class="option">--separate=library</code> option is used.
</div></li><li class="listitem"><div class="para">
@@ -9345,11 +10180,11 @@ HOME=/
</div></li><li class="listitem"><div class="para">
<span class="emphasis"><em>OProfile accumulates data from multiple runs</em></span> — OProfile is a system-wide profiler and expects processes to start up and shut down multiple times. Thus, samples from multiple runs accumulate. Use the command <code class="command">opcontrol --reset</code> to clear out the samples from previous runs.
</div></li><li class="listitem"><div class="para">
- <span class="emphasis"><em>Hardware performance counters do not work on guest virtual machines</em></span> — Because the hardware performance counters are not available on virtual systems, you need to use the <code class="computeroutput">timer</code> mode. Run the command <code class="command">opcontrol --deinit</code>, and then execute <code class="command">modprobe oprofile timer=1</code> to enable the <code class="computeroutput">timer</code> mode.
+ <span class="emphasis"><em>Hardware performance counters do not work on guest virtual machines</em></span> — Because the hardware performance counters are not available on virtual systems, you need to use the <code class="computeroutput">timer</code> mode. Enter the command <code class="command">opcontrol --deinit</code>, and then execute <code class="command">modprobe oprofile timer=1</code> to enable the <code class="computeroutput">timer</code> mode.
</div></li><li class="listitem"><div class="para">
<span class="emphasis"><em>Non-CPU-limited performance problems</em></span> — OProfile is oriented to finding problems with CPU-limited processes. OProfile does not identify processes that are asleep because they are waiting on locks or for some other event to occur (for example an I/O device to finish an operation).
- </div></li></ul></div><div class="section" id="s1-oprofile-overview-tools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.1. Overview of Tools</h2></div></div></div><a id="idm225440105600" class="indexterm"></a><div class="para">
- <a class="xref" href="#tb-oprofile-tools">Table 19.1, “OProfile Commands”</a> provides a brief overview of the tools provided with the <code class="filename">oprofile</code> package.
+ </div></li></ul></div><div class="section" id="s1-oprofile-overview-tools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.1. Overview of Tools</h2></div></div></div><a id="idm261738480832" class="indexterm"></a><div class="para">
+ <a class="xref" href="#tb-oprofile-tools">Table 19.1, “OProfile Commands”</a> provides a brief overview of the most commonly used tools provided with the <code class="filename">oprofile</code> package.
</div><div class="table" id="tb-oprofile-tools"><h6>Table 19.1. OProfile Commands</h6><div class="table-contents"><table summary="OProfile Commands" border="1"><colgroup><col width="29%" class="command" /><col width="71%" class="description" /></colgroup><thead><tr><th class="">
Command
</th><th class="">
@@ -9371,19 +10206,26 @@ HOME=/
</td></tr><tr><td class="">
<code class="command">opannotate</code>
</td><td class="">
- Creates annotated source for an executable if the application was compiled with debugging symbols. See <a class="xref" href="#s2-oprofile-reading-opannotate">Section 19.5.4, “Using <code class="command">opannotate</code> ”</a> for details.
+ Creates annotated source for an executable if the application was compiled with debugging symbols. See <a class="xref" href="#s2-oprofile-reading-opannotate">Section 19.6.4, “Using <code class="command">opannotate</code>”</a> for details.
</td></tr><tr><td class="">
<code class="command">opcontrol</code>
</td><td class="">
<div class="para">
- Configures what data is collected. See <a class="xref" href="#s1-oprofile-configuring">Section 19.2, “Configuring OProfile”</a> for details.
+ Configures what data is collected. See <a class="xref" href="#s1-oprofile-configuring">Section 19.3, “Configuring OProfile Using Legacy Mode”</a> for details.
</div>
</td></tr><tr><td class="">
+ <code class="command">operf</code>
+ </td><td class="">
+ <div class="para">
+ Recommended tool to be used in place of <code class="command">opcontrol</code> for profiling. See <a class="xref" href="#s1-using-operf">Section 19.2, “Using operf”</a> for details.
+ </div>
+ For differences between <code class="command">operf</code> and <code class="command">opcontrol</code> see <a class="xref" href="#s2-operf_vs_opcontrol">Section 19.1.1, “operf vs. opcontrol”</a>.
+ </td></tr><tr><td class="">
<code class="command">opreport</code>
</td><td class="">
<div class="para">
- Retrieves profile data. See <a class="xref" href="#s2-oprofile-reading-opreport">Section 19.5.1, “Using <code class="command">opreport</code> ”</a> for details.
+ Retrieves profile data. See <a class="xref" href="#s2-oprofile-reading-opreport">Section 19.6.1, “Using <code class="command">opreport</code>”</a> for details.
</div>
</td></tr><tr><td class="">
@@ -9393,23 +10235,103 @@ HOME=/
Runs as a daemon to periodically write sample data to disk.
</div>
- </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="s1-oprofile-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.2. Configuring OProfile</h2></div></div></div><a id="idm225474294976" class="indexterm"></a><a id="idm225435523440" class="indexterm"></a><a id="idm225435521328" class="indexterm"></a><div class="para">
- Before OProfile can be run, it must be configured. At a minimum, selecting to monitor the kernel (or selecting not to monitor the kernel) is required. The following sections describe how to use the <code class="command">opcontrol</code> utility to configure OProfile. As the <code class="command">opcontrol</code> commands are executed, the setup options are saved to the <code class="filename">/root/.oprofile/daemonrc</code> file.
- </div><div class="section" id="s2-oprofile-kernel"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.1. Specifying the Kernel</h3></div></div></div><a id="idm225448680480" class="indexterm"></a><div class="para">
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="s2-operf_vs_opcontrol"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.1.1. operf vs. opcontrol</h3></div></div></div><div class="para">
+ There are two mutually exclusive methods for collecting profiling data with OProfile. You can either use the newer and preferred <code class="command">operf</code> or the <code class="command">opcontrol</code> tool.
+ </div><h4 id="idm261743703392">operf</h4><div class="para">
+ This is the recommended mode for profiling. The <code class="command">operf</code> tool uses the Linux Performance Events Subsystem, and therefore does not require the <span class="emphasis"><em>oprofile</em></span> kernel driver. The <code class="command">operf</code> tool allows you to target your profiling more precisely, as a single process or system-wide, and also allows OProfile to co-exist better with other tools using the performance monitoring hardware on your system. Unlike <code class="command">opcontrol</code>, it can be used without the <code class="systemitem">root</code> privileges. However, <code class="command">operf</code> is also capable of system-wide operations with use of the <code class="option">--system-wide</code> option, where root authority is required.
+ </div><div class="para">
+ With <code class="command">operf</code>, there is no initial setup needed. You can invoke <code class="command">operf</code> with command-line options to specify your profiling settings. After that, you can run the OProfile post-processing tools described in <a class="xref" href="#s1-oprofile-analyzing-data">Section 19.6, “Analyzing the Data”</a>. See <a class="xref" href="#s1-using-operf">Section 19.2, “Using operf”</a> for further information.
+ </div><h4 id="idm261716755184">opcontrol</h4><div class="para">
+ This mode consists of the <code class="command">opcontrol</code> shell script, the <code class="systemitem">oprofiled</code> daemon, and several post-processing tools. The <code class="command">opcontrol</code> command is used for configuring, starting, and stopping a profiling session. An OProfile kernel driver, usually built as a kernel module, is used for collecting samples, which are then recorded into sample files by <code class="systemitem">oprofiled</code>. You can use legacy mode only if you have <code class="systemitem">root</code> privileges. In certain cases, such as when you need to sample areas with disabled interrupt request (IRQ), this is a better alternative.
+ </div><div class="para">
+ Before OProfile can be run in legacy mode, it must be configured as shown in <a class="xref" href="#s1-oprofile-configuring">Section 19.3, “Configuring OProfile Using Legacy Mode”</a>. These settings are then applied when starting OProfile (<a class="xref" href="#s1-oprofile-starting">Section 19.4, “Starting and Stopping OProfile Using Legacy Mode”</a>).
+ </div></div></div><div class="section" id="s1-using-operf"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.2. Using operf</h2></div></div></div><div class="para">
+ <code class="command">operf</code> is the recommended profiling mode that does not require initial setup before starting. All settings are specified as command-line options and there is no separate command to start the profiling process. To stop <code class="command">operf</code>, press Ctrl+C. The typical <code class="command">operf</code> command syntax looks as follows:
+ </div><pre class="synopsis"><code class="command">operf</code> <em class="replaceable"><code>options</code></em> <em class="replaceable"><code>range</code></em> <em class="replaceable"><code>command</code></em> <em class="replaceable"><code>args</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>options</code></em> with the desired command-line options to specify your profiling settings. Full set of options is described in <code class="systemitem">operf(1)</code> manual page. Replace <em class="replaceable"><code>range</code></em> with one of the following:
+ </div><div class="para">
+ <code class="option">--system-wide</code> - this setting allows for global profiling, see <a class="xref" href="#using_operf_system-wide">Using <code class="command">operf</code> in System-wide Mode</a>
+ </div><div class="para">
+ <code class="option">--pid=<em class="replaceable"><code>PID</code></em></code> - this is to profile a running application, where <em class="replaceable"><code>PID</code></em> is the process ID of the process you want to profile.
+ </div><div class="para">
+ With <em class="replaceable"><code>command</code></em> and <em class="replaceable"><code>args</code></em>, you can define a specific command or application to be profiled, and also the input arguments that this command or application requires. Either <em class="replaceable"><code>command</code></em>, <code class="option">--pid</code> or <code class="option">--system-wide</code> is required, but these cannot be used simultaneously.
+ </div><div class="para">
+ When you invoke <code class="command">operf</code> on a command line without setting the <em class="replaceable"><code>range</code></em> option, data will be collected for the children processes.
+ </div><div class="note" id="using_operf_system-wide"><div class="admonition_header"><h2>Using <code class="command">operf</code> in System-wide Mode</h2></div><div class="admonition"><div class="para">
+ To run <code class="command">operf</code> <code class="option">--system-wide</code>, you need <code class="systemitem">root</code> authority. When finished profiling, you can stop <code class="command">operf</code> with <code class="literal">Ctrl+C</code>.
+ </div><div class="para">
+ If you run <code class="command">operf</code> <code class="option">--system-wide</code> as a background process (with <code class="literal">&</code>), stop it in a controlled manner in order to process the collected profile data. For this purpose, use:
+ </div><pre class="synopsis"><code class="command">kill -SIGINT operf-PID </code></pre><div class="para">
+ When running <code class="command">operf</code> <code class="option">--system-wide</code>, it is recommended that your current working directory is <code class="filename">/root</code> or a subdirectory of <code class="filename">/root</code> so that sample data files are not stored in locations accessible by regular users.
+ </div></div></div><div class="section" id="s2-operf-kernel"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.1. Specifying the Kernel</h3></div></div></div><div class="para">
+ To monitor the kernel, execute the following command:
+ </div><pre class="synopsis"><code class="command">operf</code> <code class="option">--vmlinux</code>=<em class="replaceable"><code>vmlinux_path</code></em></pre><div class="para">
+ With this option, you can specify a path to a vmlinux file that matches the running kernel. Kernel samples will be attributed to this binary, allowing post-processing tools to attribute samples to the appropriate kernel symbols. If this option is not specified, all kernel samples will be attributed to a pseudo binary named "no-vmlinux".
+ </div></div><div class="section" id="s2-operf-events"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.2. Setting Events to Monitor</h3></div></div></div><div class="para">
+ Most processors contain counters, which are used by OProfile to monitor specific events. As shown in <a class="xref" href="#tb-oprofile-processors">Table 19.3, “OProfile Processors and Counters”</a>, the number of counters available depends on the processor.
+ </div><div class="para">
+ The events for each counter can be configured via the command line or with a graphical interface. For more information on the graphical interface, see <a class="xref" href="#s1-oprofile-gui">Section 19.10, “Graphical Interface”</a>. If the counter cannot be set to a specific event, an error message is displayed.
+ </div><div class="note"><div class="admonition_header"><h2>Older Processors and operf</h2></div><div class="admonition"><div class="para">
+ Some older processor models are not supported by the underlying Linux Performance Events Subsystem kernel and therefore are not supported by <code class="command">operf</code>. If you receive this message:
+<pre class="screen">
+Your kernel's Performance Events Subsystem does not support your processor type
+</pre>
+ when attempting to use <code class="command">operf</code>, try profiling with <code class="command">opcontrol</code> to see if your processor type may be supported by OProfile's legacy mode.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Using operf on Virtual Systems</h2></div><div class="admonition"><div class="para">
+ Since hardware performance counters are not available on guest virtual machines, you have to enable <span class="emphasis"><em>timer</em></span> mode to use <span class="application"><strong>operf</strong></span> on virtual systems. To do so, type as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code class="command">opcontrol</code> <code class="option">--deinit</code></pre><pre class="synopsis"><code class="command">modprobe</code> <code class="command">oprofile</code> <code class="option">timer=1</code></pre></div></div><div class="para">
+ To set the event for each configurable counter via the command line, use:
+ </div><pre class="synopsis"><code class="command">operf</code> <code class="option">--events</code>=<em class="replaceable"><code>event1</code></em>,<em class="replaceable"><code>event2</code></em>…</pre><div class="para">
+ Here, pass a comma-separated list of event specifications for profiling. Each event specification is a colon-separated list of attributes in the following form:
+ </div><pre class="synopsis"><em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em>:<em class="replaceable"><code>kernel</code></em>:<em class="replaceable"><code>user</code></em></pre><div class="para">
+ <a class="xref" href="#tab_event_specifications">Table 19.2, “Event Specifications”</a> summarizes these options. The last three values are optional, if you omit them, they will be set to their default values. Note that certain events do require a unit mask.
+ </div><div class="table" id="tab_event_specifications"><h6>Table 19.2. Event Specifications</h6><div class="table-contents"><table summary="Event Specifications" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="" align="left">
+ Specification
+ </th><th class="" align="left">
+ Description
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ <em class="replaceable"><code>event-name</code></em>
+ </td><td class="" align="left">
+ The exact symbolic event name taken from <code class="command">ophelp</code>
+ </td></tr><tr><td class="" align="left">
+ <em class="replaceable"><code>sample-rate</code></em>
+ </td><td class="" align="left">
+ The number of events to wait before sampling again. The smaller the count, the more frequent the samples. For events that do not happen frequently, a lower count may be needed to capture a statistically significant number of event instances. On the other hand, sampling too frequently can overload the system. By default, OProfile uses a time-based event set, which creates a sample every 100,000 clock cycles per processor.
+ </td></tr><tr><td class="" align="left">
+ <em class="replaceable"><code>unit-mask</code></em>
+ </td><td class="" align="left">
+ Unit masks, which further define the event, are listed in <code class="command">ophelp</code>. You can insert either a hexadecimal value, beginning with "0x", or a string that matches the first word of the unit mask description in <code class="command">ophelp</code>. Definition by name is valid only for unit masks having "extra:" parameters, as shown by the output of <code class="command">ophelp</code>. This type of unit mask cannot be defined with a hexadecimal value. Note that on certain architectures, there can be multiple unit masks with the same hexadecimal value. In that case they have to be specified by their names only.
+ </td></tr><tr><td class="" align="left">
+ <em class="replaceable"><code>kernel</code></em>
+ </td><td class="" align="left">
+ Specifies whether to profile kernel code (insert <code class="literal">0</code> or <code class="literal">1</code>(default))
+ </td></tr><tr><td class="" align="left">
+ <em class="replaceable"><code>user</code></em>
+ </td><td class="" align="left">
+ Specifies whether to profile user-space code (insert <code class="literal">0</code> or <code class="literal">1</code> (default))
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The events available vary depending on the processor type. When no event specification is given, the default event for the running processor type will be used for profiling. See <a class="xref" href="#tb-oprofile-default-events">Table 19.4, “Default Events”</a> for a list of these default events. To determine the events available for profiling, use the <code class="command">ophelp</code> command.
+ </div><pre class="synopsis"><code class="command">ophelp</code></pre></div><div class="section" id="s2-operf-categorization"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.3. Categorization of Samples</h3></div></div></div><div class="para">
+ The <code class="option">--separate-thread</code> option categorizes samples by thread group ID (tgid) and thread ID (tid). This is useful for seeing per-thread samples in multi-threaded applications. When used in conjunction with the <code class="option">--system-wide</code> option, <code class="option">--separate-thread</code> is also useful for seeing per-process (i.e., per-thread group) samples for the case where multiple processes are executing the same program during a profiling run.
+ </div><div class="para">
+ The <code class="option">--separate-cpu</code> option categorizes samples by CPU.
+ </div></div></div><div class="section" id="s1-oprofile-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.3. Configuring OProfile Using Legacy Mode</h2></div></div></div><a id="idm261754691568" class="indexterm"></a><a id="idm261739138688" class="indexterm"></a><a id="idm261739137088" class="indexterm"></a><div class="para">
+ Before OProfile can be run in legacy mode, it must be configured. At a minimum, selecting to monitor the kernel (or selecting not to monitor the kernel) is required. The following sections describe how to use the <code class="command">opcontrol</code> utility to configure OProfile. As the <code class="command">opcontrol</code> commands are executed, the setup options are saved to the <code class="filename">/root/.oprofile/daemonrc</code> file.
+ </div><div class="section" id="s2-oprofile-kernel"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.3.1. Specifying the Kernel</h3></div></div></div><a id="idm261734456064" class="indexterm"></a><div class="para">
First, configure whether OProfile should monitor the kernel. This is the only configuration option that is required before starting OProfile. All others are optional.
</div><div class="para">
- To monitor the kernel, execute the following command as root:
- </div><a id="idm225448677760" class="indexterm"></a><pre class="screen">~]# <code class="command">opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux</code></pre><div class="note"><div class="admonition_header"><h2>Install the debuginfo package</h2></div><div class="admonition"><div class="para">
- The <span class="package">debuginfo</span> package for the kernel must be installed (which contains the uncompressed kernel) in order to monitor the kernel.
+ To monitor the kernel, execute the following command as <code class="systemitem">root</code>:
+ </div><a id="idm261715107744" class="indexterm"></a><pre class="screen">~]# <code class="command">opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux</code></pre><div class="important"><div class="admonition_header"><h2>Install the debuginfo package</h2></div><div class="admonition"><div class="para">
+ In order to monitor the kernel, the <span class="package">debuginfo</span> package which contains the uncompressed kernel must be installed.
</div></div></div><div class="para">
- To configure OProfile not to monitor the kernel, execute the following command as root:
- </div><a id="idm225408471120" class="indexterm"></a><pre class="screen">~]# <code class="command">opcontrol --setup --no-vmlinux</code></pre><div class="para">
- This command also loads the <code class="computeroutput">oprofile</code> kernel module, if it is not already loaded, and creates the <code class="filename">/dev/oprofile/</code> directory, if it does not already exist. See <a class="xref" href="#s1-oprofile-dev-oprofile">Section 19.6, “Understanding <code class="filename">/dev/oprofile/</code> ”</a> for details about this directory.
- </div><div class="para">
- Setting whether samples should be collected within the kernel only changes what data is collected, not how or where the collected data is stored. To generate different sample files for the kernel and application libraries, refer to <a class="xref" href="#s2-oprofile-starting-separate">Section 19.2.3, “Separating Kernel and User-space Profiles”</a>.
- </div></div><div class="section" id="s2-oprofile-events"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.2. Setting Events to Monitor</h3></div></div></div><a id="idm225422787888" class="indexterm"></a><div class="para">
- Most processors contain <em class="firstterm">counters</em>, which are used by OProfile to monitor specific events. As shown in <a class="xref" href="#tb-oprofile-processors">Table 19.2, “OProfile Processors and Counters”</a>, the number of counters available depends on the processor.
- </div><div class="table" id="tb-oprofile-processors"><h6>Table 19.2. OProfile Processors and Counters</h6><div class="table-contents"><table summary="OProfile Processors and Counters" border="1"><colgroup><col width="43%" class="option" /><col width="29%" class="description" /><col width="29%" class="description" /></colgroup><thead><tr><th class="">
+ To configure OProfile not to monitor the kernel, execute the following command as <code class="systemitem">root</code>:
+ </div><a id="idm261784827856" class="indexterm"></a><pre class="screen">~]# <code class="command">opcontrol --setup --no-vmlinux</code></pre><div class="para">
+ This command also loads the <code class="computeroutput">oprofile</code> kernel module, if it is not already loaded, and creates the <code class="filename">/dev/oprofile/</code> directory, if it does not already exist. See <a class="xref" href="#s1-oprofile-dev-oprofile">Section 19.7, “Understanding the /dev/oprofile/ directory ”</a> for details about this directory.
+ </div><div class="para">
+ Setting whether samples should be collected within the kernel only changes what data is collected, not how or where the collected data is stored. To generate different sample files for the kernel and application libraries, see <a class="xref" href="#s2-oprofile-starting-separate">Section 19.3.3, “Separating Kernel and User-space Profiles”</a>.
+ </div></div><div class="section" id="s2-oprofile-events"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.3.2. Setting Events to Monitor</h3></div></div></div><a id="idm261759264688" class="indexterm"></a><div class="para">
+ Most processors contain <em class="firstterm">counters</em>, which are used by OProfile to monitor specific events. As shown in <a class="xref" href="#tb-oprofile-processors">Table 19.3, “OProfile Processors and Counters”</a>, the number of counters available depends on the processor.
+ </div><div class="table" id="tb-oprofile-processors"><h6>Table 19.3. OProfile Processors and Counters</h6><div class="table-contents"><table summary="OProfile Processors and Counters" border="1"><colgroup><col width="43%" class="option" /><col width="29%" class="description" /><col width="29%" class="description" /></colgroup><thead><tr><th class="">
Processor
</th><th class="">
<code class="command">cpu_type</code>
@@ -9422,12 +10344,6 @@ HOME=/
</td><td class="">
4
</td></tr><tr><td class="">
- AMD Athlon
- </td><td class="">
- i386/athlon
- </td><td class="">
- 4
- </td></tr><tr><td class="">
AMD Family 10h
</td><td class="">
x86-64/family10
@@ -9458,6 +10374,24 @@ HOME=/
</td><td class="">
6
</td></tr><tr><td class="">
+ Applied Micro X-Gene
+ </td><td class="">
+ arm/armv8-xgene
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ ARM Cortex A53
+ </td><td class="">
+ arm/armv8-ca53
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ ARM Cortex A57
+ </td><td class="">
+ arm/armv8-ca57
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
IBM eServer System i and IBM eServer System p
</td><td class="">
timer
@@ -9482,6 +10416,42 @@ HOME=/
</td><td class="">
8
</td></tr><tr><td class="">
+ IBM PowerPC 970MP
+ </td><td class="">
+ ppc64/970MP
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ IBM POWER5+
+ </td><td class="">
+ ppc64/power5+
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER5++
+ </td><td class="">
+ ppc64/power5++
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER56
+ </td><td class="">
+ ppc64/power6
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER7
+ </td><td class="">
+ ppc64/power7
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER8
+ </td><td class="">
+ ppc64/power7
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
IBM S/390 and IBM System z
</td><td class="">
timer
@@ -9500,36 +10470,78 @@ HOME=/
</td><td class="">
4
</td></tr><tr><td class="">
- Intel Pentium 4 (non-hyper-threaded)
+ Intel Westmere microarchitecture
+ </td><td class="">
+ i386/westmere
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Haswell microarchitecture (non-hyper-threaded)
</td><td class="">
- i386/p4
+ i386/haswell
</td><td class="">
8
</td></tr><tr><td class="">
- Intel Pentium 4 (hyper-threaded)
+ Intel Haswell microarchitecture (hyper-threaded)
</td><td class="">
- i386/p4-ht
+ i386/haswell-ht
</td><td class="">
4
</td></tr><tr><td class="">
- Intel Westmere microarchitecture
+ Intel Ivy Bridge microarchitecture (non-hyper-threaded)
</td><td class="">
- i386/westmere
+ i386/ivybridge
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Ivy Bridge microarchitecture (hyper-threaded)
+ </td><td class="">
+ i386/ivybridge-ht
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Sandy Bridge microarchitecture (non-hyper-threaded)
+ </td><td class="">
+ i386/sandybridge
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Sandy Bridge microarchitecture
+ </td><td class="">
+ i386/sandybridge-ht
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Broadwell microarchitecture (non-hyper-threaded)
+ </td><td class="">
+ i386/broadwell
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Broadwell microarchitecture (hyper-threaded)
+ </td><td class="">
+ i386/broadwell-ht
</td><td class="">
4
</td></tr><tr><td class="">
+ Intel Silvermont microarchitecture
+ </td><td class="">
+ i386/silvermont
+ </td><td class="">
+ 2
+ </td></tr><tr><td class="">
TIMER_INT
</td><td class="">
timer
</td><td class="">
1
</td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
- Use <a class="xref" href="#tb-oprofile-processors">Table 19.2, “OProfile Processors and Counters”</a> to verify that the correct processor type was detected and to determine the number of events that can be monitored simultaneously. <code class="computeroutput">timer</code> is used as the processor type if the processor does not have supported performance monitoring hardware.
+ Use <a class="xref" href="#tb-oprofile-processors">Table 19.3, “OProfile Processors and Counters”</a> to determine the number of events that can be monitored simultaneously for your CPU type. If the processor does not have supported performance monitoring hardware, the <code class="computeroutput">timer</code> is used as the processor type.
</div><div class="para">
If <code class="computeroutput">timer</code> is used, events cannot be set for any processor because the hardware does not have support for hardware performance counters. Instead, the timer interrupt is used for profiling.
</div><div class="para">
- If <code class="computeroutput">timer</code> is not used as the processor type, the events monitored can be changed, and counter 0 for the processor is set to a time-based event by default. If more than one counter exists on the processor, the counters other than counter 0 are not set to an event by default. The default events monitored are shown in <a class="xref" href="#tb-oprofile-default-events">Table 19.3, “Default Events”</a>.
- </div><div class="table" id="tb-oprofile-default-events"><h6>Table 19.3. Default Events</h6><div class="table-contents"><table summary="Default Events" border="1"><colgroup><col width="25%" class="option" /><col width="33%" class="description" /><col width="42%" class="description" /></colgroup><thead><tr><th class="">
+ If <code class="computeroutput">timer</code> is not used as the processor type, the events monitored can be changed, and counter 0 for the processor is set to a time-based event by default. If more than one counter exists on the processor, the counters other than 0 are not set to an event by default. The default events monitored are shown in <a class="xref" href="#tb-oprofile-default-events">Table 19.4, “Default Events”</a>.
+ </div><div class="table" id="tb-oprofile-default-events"><h6>Table 19.4. Default Events</h6><div class="table-contents"><table summary="Default Events" border="1"><colgroup><col width="25%" class="option" /><col width="33%" class="description" /><col width="42%" class="description" /></colgroup><thead><tr><th class="">
Processor
</th><th class="">
Default Event for Counter
@@ -9554,15 +10566,39 @@ HOME=/
</td><td class="">
The processor's clock is not halted
</td></tr><tr><td class="">
- IBM POWER4
+ Applied Micro X-Gene
</td><td class="">
- CYCLES
+ CPU_CYCLES
</td><td class="">
Processor Cycles
</td></tr><tr><td class="">
- IBM POWER5
+ ARM Cortex A53
</td><td class="">
- CYCLES
+ CPU_CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ ARM Cortex A57
+ </td><td class="">
+ CPU_CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ IBM POWER4
+ </td><td class="">
+ CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ IBM POWER5
+ </td><td class="">
+ CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ IBM POWER8
+ </td><td class="">
+ CYCLES
</td><td class="">
Processor Cycles
</td></tr><tr><td class="">
@@ -9596,6 +10632,18 @@ HOME=/
</td><td class="">
The processor's clock is not halted
</td></tr><tr><td class="">
+ Intel Broadwell microarchitecture
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ Intel Silvermont microarchitecture
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
TIMER_INT
</td><td class="">
(none)
@@ -9605,72 +10653,87 @@ HOME=/
The number of events that can be monitored at one time is determined by the number of counters for the processor. However, it is not a one-to-one correlation; on some processors, certain events must be mapped to specific counters. To determine the number of counters available, execute the following command:
</div><pre class="screen">~]# <code class="command">ls -d /dev/oprofile/[0-9]*</code></pre><div class="para">
The events available vary depending on the processor type. To determine the events available for profiling, execute the following command as root (the list is specific to the system's processor type):
- </div><a id="idm225463837040" class="indexterm"></a><a id="idm225468838592" class="indexterm"></a><pre class="screen">~]# <code class="command">ophelp</code></pre><div class="para">
- The events for each counter can be configured via the command line or with a graphical interface. For more information on the graphical interface, refer to <a class="xref" href="#s1-oprofile-gui">Section 19.9, “Graphical Interface”</a>. If the counter cannot be set to a specific event, an error message is displayed.
+ </div><a id="idm261737873808" class="indexterm"></a><a id="idm261737871888" class="indexterm"></a><pre class="screen">~]# <code class="command">ophelp</code></pre><div class="note"><div class="admonition_header"><h2>Make sure that OProfile is configured</h2></div><div class="admonition"><div class="para">
+ Unless OProfile is properly configured, <code class="command">ophelp</code> fails with the following error message:
+ </div><pre class="screen">Unable to open cpu_type file for reading
+Make sure you have done opcontrol --init
+cpu_type 'unset' is not valid
+you should upgrade oprofile or force the use of timer mode</pre><div class="para">
+ To configure OProfile, follow the instructions in <a class="xref" href="#s1-oprofile-configuring">Section 19.3, “Configuring OProfile Using Legacy Mode”</a>.
+ </div></div></div><div class="para">
+ The events for each counter can be configured via the command line or with a graphical interface. For more information on the graphical interface, see <a class="xref" href="#s1-oprofile-gui">Section 19.10, “Graphical Interface”</a>. If the counter cannot be set to a specific event, an error message is displayed.
</div><div class="para">
To set the event for each configurable counter via the command line, use <code class="command">opcontrol</code>:
</div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em></code></pre><div class="para">
Replace <em class="replaceable"><code>event-name</code></em> with the exact name of the event from <code class="command">ophelp</code>, and replace <em class="replaceable"><code>sample-rate</code></em> with the number of events between samples.
- </div><div class="section" id="s3-oprofile-events-sampling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">19.2.2.1. Sampling Rate</h4></div></div></div><a id="idm225497752080" class="indexterm"></a><div class="para">
- By default, a time-based event set is selected. It creates a sample every 100,000 clock cycles per processor. If the timer interrupt is used, the timer is set to whatever the jiffy rate is and is not user-settable. If the <code class="computeroutput">cpu_type</code> is not <code class="computeroutput">timer</code>, each event can have a <em class="firstterm">sampling rate</em> set for it. The sampling rate is the number of events between each sample snapshot.
+ </div><div class="section" id="s3-oprofile-events-sampling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">19.3.2.1. Sampling Rate</h4></div></div></div><a id="idm261753271120" class="indexterm"></a><div class="para">
+ By default, a time-based event set is selected. It creates a sample every 100,000 clock cycles per processor. If the timer interrupt is used, the timer is set to the respective rate and is not user-settable. If the <code class="computeroutput">cpu_type</code> is not <code class="computeroutput">timer</code>, each event can have a <em class="firstterm">sampling rate</em> set for it. The sampling rate is the number of events between each sample snapshot.
</div><div class="para">
When setting the event for the counter, a sample rate can also be specified:
</div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em></code></pre><div class="para">
Replace <em class="replaceable"><code>sample-rate</code></em> with the number of events to wait before sampling again. The smaller the count, the more frequent the samples. For events that do not happen frequently, a lower count may be needed to capture the event instances.
</div><div class="warning"><div class="admonition_header"><h2>Sampling too frequently can overload the system</h2></div><div class="admonition"><div class="para">
- Be extremely careful when setting sampling rates. Sampling too frequently can overload the system, causing the system to appear as if it is frozen or causing the system to actually freeze.
- </div></div></div></div><div class="section" id="s3-oprofile-events-unit-masks"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">19.2.2.2. Unit Masks</h4></div></div></div><a id="idm225431528400" class="indexterm"></a><div class="para">
+ Be extremely careful when setting sampling rates. Sampling too frequently can overload the system, causing the system to appear frozen or causing the system to actually freeze.
+ </div></div></div></div><div class="section" id="s3-oprofile-events-unit-masks"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">19.3.2.2. Unit Masks</h4></div></div></div><a id="idm261732562112" class="indexterm"></a><div class="para">
Some user performance monitoring events may also require unit masks to further define the event.
</div><div class="para">
Unit masks for each event are listed with the <code class="command">ophelp</code> command. The values for each unit mask are listed in hexadecimal format. To specify more than one unit mask, the hexadecimal values must be combined using a bitwise <em class="firstterm">or</em> operation.
- </div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em></code></pre></div></div><div class="section" id="s2-oprofile-starting-separate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.3. Separating Kernel and User-space Profiles</h3></div></div></div><a id="idm225462508032" class="indexterm"></a><div class="para">
+ </div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em></code></pre><div class="para">
+ Note that on certain architectures, there can be multiple unit masks with the same hexadecimal value. In that case they have to be specified by their names only.
+ </div></div></div><div class="section" id="s2-oprofile-starting-separate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.3.3. Separating Kernel and User-space Profiles</h3></div></div></div><a id="idm261752606256" class="indexterm"></a><div class="para">
By default, kernel mode and user mode information is gathered for each event. To configure OProfile to ignore events in kernel mode for a specific counter, execute the following command:
</div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em>:0</code></pre><div class="para">
Execute the following command to start profiling kernel mode for the counter again:
</div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em>:1</code></pre><div class="para">
To configure OProfile to ignore events in user mode for a specific counter, execute the following command:
- </div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em>:<em class="replaceable"><code>kernel</code></em>:0</code></pre><div class="para">
+ </div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em>:1:0</code></pre><div class="para">
Execute the following command to start profiling user mode for the counter again:
- </div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em>:<em class="replaceable"><code>kernel</code></em>:1</code></pre><div class="para">
+ </div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em>:1:1</code></pre><div class="para">
When the OProfile daemon writes the profile data to sample files, it can separate the kernel and library profile data into separate sample files. To configure how the daemon writes to sample files, execute the following command as root:
</div><pre class="screen">~]# <code class="command">opcontrol --separate=<em class="replaceable"><code>choice</code></em></code></pre><div class="para">
- <em class="replaceable"><code>choice</code></em> can be one of the following:
+ The <em class="replaceable"><code>choice</code></em> argument can be one of the following:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <code class="computeroutput">none</code> — do not separate the profiles (default)
+ <code class="computeroutput">none</code> — Do not separate the profiles (default).
</div></li><li class="listitem"><div class="para">
- <code class="command">library</code> — generate per-application profiles for libraries
+ <code class="command">library</code> — Generate per-application profiles for libraries.
</div></li><li class="listitem"><div class="para">
- <code class="command">kernel</code> — generate per-application profiles for the kernel and kernel modules
+ <code class="command">kernel</code> — Generate per-application profiles for the kernel and kernel modules.
</div></li><li class="listitem"><div class="para">
- <code class="command">all</code> — generate per-application profiles for libraries and per-application profiles for the kernel and kernel modules
+ <code class="command">all</code> — Generate per-application profiles for libraries and per-application profiles for the kernel and kernel modules.
</div></li></ul></div><div class="para">
If <code class="option">--separate=library</code> is used, the sample file name includes the name of the executable as well as the name of the library.
</div><div class="note"><div class="admonition_header"><h2>Restart the OProfile profiler</h2></div><div class="admonition"><div class="para">
These configuration changes will take effect when the OProfile profiler is restarted.
- </div></div></div></div></div><div class="section" id="s1-oprofile-starting"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.3. Starting and Stopping OProfile</h2></div></div></div><a id="idm225467429936" class="indexterm"></a><div class="para">
+ </div></div></div></div></div><div class="section" id="s1-oprofile-starting"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.4. Starting and Stopping OProfile Using Legacy Mode</h2></div></div></div><a id="idm261701975472" class="indexterm"></a><div class="para">
To start monitoring the system with OProfile, execute the following command as root:
- </div><a id="idm225467427744" class="indexterm"></a><pre class="screen">~]# <code class="command">opcontrol --start</code></pre><div class="para">
+ </div><a id="idm261739384656" class="indexterm"></a><pre class="screen">~]# <code class="command">opcontrol --start</code></pre><div class="para">
Output similar to the following is displayed:
</div><pre class="screen">Using log file /var/lib/oprofile/oprofiled.log Daemon started. Profiler running.</pre><div class="para">
The settings in <code class="filename">/root/.oprofile/daemonrc</code> are used.
- </div><a id="idm225451562720" class="indexterm"></a><a id="idm225451560496" class="indexterm"></a><a id="idm225460938544" class="indexterm"></a><div class="para">
+ </div><a id="idm261685689472" class="indexterm"></a><a id="idm261685687552" class="indexterm"></a><a id="idm261730230448" class="indexterm"></a><div class="para">
The OProfile daemon, <code class="command">oprofiled</code>, is started; it periodically writes the sample data to the <code class="filename">/var/lib/oprofile/samples/</code> directory. The log file for the daemon is located at <code class="filename">/var/lib/oprofile/oprofiled.log</code>.
</div><div class="important"><div class="admonition_header"><h2>Disable the nmi_watchdog registers</h2></div><div class="admonition"><div class="para">
On a Fedora 21 system, the <code class="computeroutput">nmi_watchdog</code> registers with the <code class="computeroutput">perf</code> subsystem. Due to this, the <code class="computeroutput">perf</code> subsystem grabs control of the performance counter registers at boot time, blocking OProfile from working.
</div><div class="para">
- To resolve this, either boot with the <code class="command">nmi_watchdog=0</code> kernel parameter set, or run the following command to disable <code class="computeroutput">nmi_watchdog</code> at run time:
+ To resolve this, either boot with the <code class="command">nmi_watchdog=0</code> kernel parameter set, or run the following command as <code class="systemitem">root</code> to disable <code class="computeroutput">nmi_watchdog</code> at run time:
</div><pre class="screen">~]# <code class="command">echo 0 > /proc/sys/kernel/nmi_watchdog</code></pre><div class="para">
- To re-enable <code class="computeroutput">nmi_watchdog</code>, use the following command:
+ To re-enable <code class="computeroutput">nmi_watchdog</code>, use the following command as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">echo 1 > /proc/sys/kernel/nmi_watchdog</code></pre></div></div><div class="para">
To stop the profiler, execute the following command as root:
- </div><pre class="screen">~]# <code class="command">opcontrol --shutdown</code></pre></div><div class="section" id="s1-oprofile-saving-data"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.4. Saving Data</h2></div></div></div><a id="idm225458164256" class="indexterm"></a><div class="para">
+ </div><pre class="screen">~]# <code class="command">opcontrol --shutdown</code></pre></div><div class="section" id="s1-oprofile-saving-data"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.5. Saving Data in Legacy Mode</h2></div></div></div><a id="idm261716294096" class="indexterm"></a><div class="para">
Sometimes it is useful to save samples at a specific time. For example, when profiling an executable, it may be useful to gather different samples based on different input data sets. If the number of events to be monitored exceeds the number of counters available for the processor, multiple runs of OProfile can be used to collect data, saving the sample data to different files each time.
</div><div class="para">
- To save the current set of sample files, execute the following command, replacing <em class="replaceable"><code>name</code></em> with a unique descriptive name for the current session.
+ To save the current set of sample files, execute the following command, replacing <em class="replaceable"><code>name</code></em> with a unique descriptive name for the current session:
</div><pre class="screen">~]# <code class="command">opcontrol --save=<em class="replaceable"><code>name</code></em></code></pre><div class="para">
- The directory <code class="filename">/var/lib/oprofile/samples/<em class="replaceable"><code>name</code></em>/</code> is created and the current sample files are copied to it.
- </div></div><div class="section" id="s1-oprofile-analyzing-data"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.5. Analyzing the Data</h2></div></div></div><a id="idm225457897024" class="indexterm"></a><div class="para">
- Periodically, the OProfile daemon, <code class="command">oprofiled</code>, collects the samples and writes them to the <code class="filename">/var/lib/oprofile/samples/</code> directory. Before reading the data, make sure all data has been written to this directory by executing the following command as root:
+ The command creates the directory <code class="filename">/var/lib/oprofile/samples/<em class="replaceable"><code>name</code></em>/</code> and the current sample files are copied to it.
+ </div><div class="para">
+ To specify the session directory to hold the sample data, use the <code class="option">--session-dir</code> option. If not specified, the data is saved in the <code class="filename">oprofile_data/</code> directory on the current path.
+ </div></div><div class="section" id="s1-oprofile-analyzing-data"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.6. Analyzing the Data</h2></div></div></div><a id="idm261755246032" class="indexterm"></a><div class="para">
+ The same OProfile post-processing tools are used whether you collect your profile with <code class="command">operf</code> or <code class="command">opcontrol</code> in legacy mode.
+ </div><div class="para">
+ By default, <code class="command">operf</code> stores the profiling data in the <code class="filename"><em class="replaceable"><code>current_dir</code></em>/oprofile_data/</code> directory. You can change to a different location with the <code class="option">--session-dir</code> option. The usual post-profiling analysis tools such as <code class="command">opreport</code> and <code class="command">opannotate</code> can be used to generate profile reports. These tools search for samples in <code class="filename"><em class="replaceable"><code>current_dir</code></em>/oprofile_data/</code> first. If this directory does not exist, the analysis tools use the standard session directory of <code class="filename">/var/lib/oprofile/</code>. Statistics, such as total samples received and lost samples, are written to the <code class="filename"><em class="replaceable"><code>session_dir</code></em>/samples/operf.log</code> file.
+ </div><div class="para">
+ When using legacy mode, the OProfile daemon, <code class="command">oprofiled</code>, periodically collects the samples and writes them to the <code class="filename">/var/lib/oprofile/samples/</code> directory. Before reading the data, make sure all data has been written to this directory by executing the following command as root:
</div><pre class="screen">~]# <code class="command">opcontrol --dump</code></pre><div class="para">
Each sample file name is based on the name of the executable. For example, the samples for the default event on a Pentium III processor for <code class="command">/bin/bash</code> becomes:
</div><pre class="screen">\{root\}/bin/bash/\{dep\}/\{root\}/bin/bash/CPU_CLK_UNHALTED.100000</pre><div class="para">
@@ -9682,14 +10745,13 @@ HOME=/
</div></li></ul></div><div class="para">
Use these tools, along with the binaries profiled, to generate reports that can be further analyzed.
</div><div class="warning"><div class="admonition_header"><h2>Back up the executable and the sample files</h2></div><div class="admonition"><div class="para">
- The executable being profiled must be used with these tools to analyze the data. If it must change after the data is collected, back up the executable used to create the samples as well as the sample files. Please note that the sample file and the binary have to agree. Making a backup is not going to work if they do not match. <code class="command">oparchive</code> can be used to address this problem.
+ The executable being profiled must be used with these tools to analyze the data. If it must change after the data is collected, back up the executable used to create the samples as well as the sample files. Note that the names of the sample file and the binary have to agree. You cannot make a backup if these names do not match. As an alternative, <code class="command">oparchive</code> can be used to address this problem.
</div></div></div><div class="para">
- Samples for each executable are written to a single sample file. Samples from each dynamically linked library are also written to a single sample file. While OProfile is running, if the executable being monitored changes and a sample file for the executable exists, the existing sample file is automatically deleted. Thus, if the existing sample file is needed, it must be backed up, along with the executable used to create it before replacing the executable with a new version. The OProfile analysis tools use the executable file that created the samples during analysis. If the executable changes the analysis tools will be unable to analyze the associated samples. See <a class="xref" href="#s1-oprofile-saving-data">Section 19.4, “Saving Data”</a> for details on how to back up the sample file.
- </div><div class="section" id="s2-oprofile-reading-opreport"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.5.1. Using <code class="command">opreport</code> </h3></div></div></div><a id="idm225482130336" class="indexterm"></a><a id="idm225444210304" class="indexterm"></a><div class="para">
- The <code class="command">opreport</code> tool provides an overview of all the executables being profiled.
- </div><div class="para">
- The following is part of a sample output:
- </div><pre class="screen">Profiling through timer interrupt
+ Samples for each executable are written to a single sample file. Samples from each dynamically linked library are also written to a single sample file. While OProfile is running, if the executable being monitored changes and a sample file for the executable exists, the existing sample file is automatically deleted. Thus, if the existing sample file is needed, it must be backed up, along with the executable used to create it before replacing the executable with a new version. The OProfile analysis tools use the executable file that created the samples during analysis. If the executable changes, the analysis tools will be unable to analyze the associated samples. See <a class="xref" href="#s1-oprofile-saving-data">Section 19.5, “Saving Data in Legacy Mode”</a> for details on how to back up the sample file.
+ </div><div class="section" id="s2-oprofile-reading-opreport"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.6.1. Using <code class="command">opreport</code></h3></div></div></div><a id="idm261750450960" class="indexterm"></a><a id="idm261750449040" class="indexterm"></a><div class="para">
+ The <code class="command">opreport</code> tool provides an overview of all the executables being profiled. The following is part of a sample output from the <code class="command">opreport</code> command:
+ </div><pre class="screen">~]$ <code class="command">opreport</code>
+Profiling through timer interrupt
TIMER:0|
samples| %|
------------------
@@ -9717,13 +10779,15 @@ samples| %|
1 0.0038 libwnck-1.so.4.9.0</pre><div class="para">
Each executable is listed on its own line. The first column is the number of samples recorded for the executable. The second column is the percentage of samples relative to the total number of samples. The third column is the name of the executable.
</div><div class="para">
- See the <code class="command">opreport</code> man page for a list of available command line options, such as the <code class="option">-r</code> option used to sort the output from the executable with the smallest number of samples to the one with the largest number of samples.
- </div></div><div class="section" id="s2-oprofile-reading-opreport-single"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.5.2. Using opreport on a Single Executable</h3></div></div></div><a id="idm225437695968" class="indexterm"></a><a id="idm225437693264" class="indexterm"></a><div class="para">
- To retrieve more detailed profiled information about a specific executable, use <code class="command">opreport</code>:
+ See the <code class="systemitem">opreport(1)</code> manual page for a list of available command-line options, such as the <code class="option">-r</code> option used to sort the output from the executable with the smallest number of samples to the one with the largest number of samples. You can also use the <code class="option">-t</code> or <code class="option">--threshold</code> option to trim the output of <code class="command">opcontrol</code>.
+ </div></div><div class="section" id="s2-oprofile-reading-opreport-single"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.6.2. Using opreport on a Single Executable</h3></div></div></div><a id="idm261781464816" class="indexterm"></a><a id="idm261730534512" class="indexterm"></a><div class="para">
+ To retrieve more detailed profiled information about a specific executable, use the <code class="command">opreport</code> command:
</div><pre class="screen">~]# <code class="command">opreport <em class="replaceable"><code>mode</code></em> <em class="replaceable"><code>executable</code></em></code></pre><div class="para">
- <em class="replaceable"><code>executable</code></em> must be the full path to the executable to be analyzed. <em class="replaceable"><code>mode</code></em> must be one of the following:
+ Replace <em class="replaceable"><code>executable</code></em> with the full path to the executable to be analyzed. <em class="replaceable"><code>mode</code></em> stands for one of the following options:
</div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">-l</code> </span></dt><dd><div class="para">
- List sample data by symbols. For example, the following is part of the output from running the command <code class="command">opreport -l /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code>:
+ This option is used to list sample data by symbols. For example, running this command: <pre class="synopsis">~]# <code class="command">opreport -l /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code></pre>
+ </div><div class="para">
+ produces the following output:
</div><pre class="screen">samples % symbol name
12 21.4286 __gconv_transform_utf8_internal
5 8.9286 _int_malloc 4 7.1429 malloc
@@ -9754,14 +10818,18 @@ samples| %|
</div><div class="para">
To sort the output from the largest number of samples to the smallest (reverse order), use <code class="option">-r</code> in conjunction with the <code class="option">-l</code> option.
</div></dd><dt class="varlistentry"><span class="term"> <code class="option">-i <em class="replaceable"><code>symbol-name</code></em> </code> </span></dt><dd><div class="para">
- List sample data specific to a symbol name. For example, the following output is from the command <code class="command">opreport -l -i __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code>:
+ List sample data specific to a symbol name. For example, running: <pre class="synopsis">~]# <code class="command">opreport -l -i __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code></pre>
+ </div><div class="para">
+ returns the following output:
</div><pre class="screen">samples % symbol name
12 100.000 __gconv_transform_utf8_internal</pre><div class="para">
The first line is a summary for the symbol/executable combination.
</div><div class="para">
The first column is the number of samples for the memory symbol. The second column is the percentage of samples for the memory address relative to the total number of samples for the symbol. The third column is the symbol name.
</div></dd><dt class="varlistentry"><span class="term"> <code class="option">-d</code> </span></dt><dd><div class="para">
- List sample data by symbols with more detail than <code class="option">-l</code>. For example, the following output is from the command <code class="command">opreport -l -d __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code>:
+ This option lists sample data by symbols with more detail than the <code class="option">-l</code> option. For example, with the following command: <pre class="synopsis">~]# <code class="command">opreport -d -i __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code></pre>
+ </div><div class="para">
+ this output is returned:
</div><pre class="screen">vma samples % symbol name
00a98640 12 100.000 __gconv_transform_utf8_internal
00a98640 1 8.3333
@@ -9776,12 +10844,12 @@ samples| %|
00a98869 1 8.3333
00a98b08 1 8.3333</pre><div class="para">
The data is the same as the <code class="option">-l</code> option except that for each symbol, each virtual memory address used is shown. For each virtual memory address, the number of samples and percentage of samples relative to the number of samples for the symbol is displayed.
- </div></dd><dt class="varlistentry"><span class="term"> <code class="option">-x</code> <em class="replaceable"><code>symbol-name</code></em> </span></dt><dd><div class="para">
- Exclude the comma-separated list of symbols from the output.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">-e</code> <em class="replaceable"><code>symbol-name</code></em>… </span></dt><dd><div class="para">
+ With this option, you can exclude some symbols from the output. Replace <em class="replaceable"><code>symbol-name</code></em> with the comma-separated list of symbols you want to exclude.
</div></dd><dt class="varlistentry"><span class="term"> <code class="option">session</code>:<em class="replaceable"><code>name</code></em> </span></dt><dd><div class="para">
- Specify the full path to the session or a directory relative to the <code class="filename">/var/lib/oprofile/samples/</code> directory.
- </div></dd></dl></div></div><div class="section" id="s2-oprofile-module-output"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.5.3. Getting more detailed output on the modules</h3></div></div></div><a id="idm225450868912" class="indexterm"></a><a id="idm225475873568" class="indexterm"></a><div class="para">
- OProfile collects data on a system-wide basis for kernel- and user-space code running on the machine. However, once a module is loaded into the kernel, the information about the origin of the kernel module is lost. The module could have come from the <code class="filename">initrd</code> file on boot up, the directory with the various kernel modules, or a locally created kernel module. As a result, when OProfile records sample for a module, it just lists the samples for the modules for an executable in the root directory, but this is unlikely to be the place with the actual code for the module. You will need to take some steps to make sure that analysis tools get the executable.
+ Here, you can specify the full path to the session, a directory relative to the <code class="filename">/var/lib/oprofile/samples/</code> directory, or if you are using <code class="command">operf</code>, a directory relative to <code class="filename">./oprofile_data/samples/</code>.
+ </div></dd></dl></div></div><div class="section" id="s2-oprofile-module-output"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.6.3. Getting More Detailed Output on the Modules</h3></div></div></div><a id="idm261633490960" class="indexterm"></a><a id="idm261633489040" class="indexterm"></a><div class="para">
+ OProfile collects data on a system-wide basis for kernel- and user-space code running on the machine. However, once a module is loaded into the kernel, the information about the origin of the kernel module is lost. The module could come from the <code class="filename">initrd</code> file on boot up, the directory with the various kernel modules, or a locally created kernel module. As a result, when OProfile records samples for a module, it just lists the samples for the modules for an executable in the root directory, but this is unlikely to be the place with the actual code for the module. You will need to take some steps to make sure that analysis tools get the proper executable.
</div><div class="para">
To get a more detailed view of the actions of the module, you will need to either have the module "unstripped" (that is installed from a custom build) or have the <span class="package">debuginfo</span> package installed for the kernel.
</div><div class="para">
@@ -9808,18 +10876,18 @@ samples % symbol name
583 3.5361 ext4_xattr_get
479 2.9053 ext4_htree_store_dirent
469 2.8447 ext4_get_group_desc
-414 2.5111 ext4_dx_find_entry</pre></div><div class="section" id="s2-oprofile-reading-opannotate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.5.4. Using <code class="command">opannotate</code> </h3></div></div></div><a id="idm225459181568" class="indexterm"></a><a id="idm225459179344" class="indexterm"></a><div class="para">
- The <code class="command">opannotate</code> tool tries to match the samples for particular instructions to the corresponding lines in the source code. The resulting files generated should have the samples for the lines at the left. It also puts in a comment at the beginning of each function listing the total samples for the function.
+414 2.5111 ext4_dx_find_entry</pre></div><div class="section" id="s2-oprofile-reading-opannotate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.6.4. Using <code class="command">opannotate</code></h3></div></div></div><a id="idm261720556128" class="indexterm"></a><a id="idm261720554208" class="indexterm"></a><div class="para">
+ The <code class="command">opannotate</code> tool tries to match the samples for particular instructions to the corresponding lines in the source code. The resulting generated files should have the samples for the lines at the left. It also puts in a comment at the beginning of each function listing the total samples for the function.
</div><div class="para">
- For this utility to work, the appropriate <span class="package">debuginfo</span> package for the executable must be installed on the system. By default, Fedora <span class="package">debuginfo</span> packages are not installed together with their corresponding packages, which contain the executable, so that you have to obtain and install the <span class="package">debuginfo</span> packages separately.
+ For this utility to work, the appropriate <span class="package">debuginfo</span> package for the executable must be installed on the system. On Fedora, the <span class="package">debuginfo</span> packages are not automatically installed with the corresponding packages that contain the executable. You have to obtain and install them separately.
</div><div class="para">
The general syntax for <code class="command">opannotate</code> is as follows:
</div><pre class="screen">~]# <code class="command">opannotate --search-dirs <em class="replaceable"><code>src-dir</code></em> --source <em class="replaceable"><code>executable</code></em></code></pre><div class="para">
- The directory containing the source code and the executable to be analyzed must be specified. See the <code class="command">opannotate</code> man page for a list of additional command line options.
- </div></div></div><div class="section" id="s1-oprofile-dev-oprofile"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.6. Understanding <code class="filename">/dev/oprofile/</code> </h2></div></div></div><a id="idm225472950544" class="indexterm"></a><a id="idm225506256560" class="indexterm"></a><div class="para">
- The <code class="filename">/dev/oprofile/</code> directory contains the file system for OProfile. Use the <code class="command">cat</code> command to display the values of the virtual files in this file system. For example, the following command displays the type of processor OProfile detected:
+ These command-line options are mandatory. Replace <em class="replaceable"><code>src-dir</code></em> with a path to the directory containing the source code and specify the executable to be analyzed. See the <code class="systemitem">opannotate(1)</code> manual page for a list of additional command line options.
+ </div></div></div><div class="section" id="s1-oprofile-dev-oprofile"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.7. Understanding the /dev/oprofile/ directory </h2></div></div></div><a id="idm261746157520" class="indexterm"></a><a id="idm261729274336" class="indexterm"></a><div class="para">
+ When using OProfile in legacy mode, the <code class="filename">/dev/oprofile/</code> directory is used to store the file system for OProfile. On the other hand, <code class="command">operf</code> does not require <code class="filename">/dev/oprofile/</code>. Use the <code class="command">cat</code> command to display the values of the virtual files in this file system. For example, the following command displays the type of processor OProfile detected:
</div><pre class="screen">~]# <code class="command">cat /dev/oprofile/cpu_type</code></pre><div class="para">
- A directory exists in <code class="filename">/dev/oprofile/</code> for each counter. For example, if there are 2 counters, the directories <code class="filename">/dev/oprofile/0/</code> and <code class="filename">dev/oprofile/1/</code> exist.
+ A directory exists in <code class="filename">/dev/oprofile/</code> for each counter. For example, if there are 2 counters, the directories <code class="filename">/dev/oprofile/0/</code> and <code class="filename">/dev/oprofile/1/</code> exist.
</div><div class="para">
Each directory for a counter contains the following files:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
@@ -9838,79 +10906,569 @@ samples % symbol name
<code class="filename">user</code> — If 0, samples are not collected for the counter event when the processor is in user-space; if 1, samples are collected even if the processor is in user-space.
</div></li></ul></div><div class="para">
The values of these files can be retrieved with the <code class="command">cat</code> command. For example:
- </div><pre class="screen">~]# <code class="command">cat /dev/oprofile/0/count</code></pre></div><div class="section" id="s1-oprofile-example-usage"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.7. Example Usage</h2></div></div></div><div class="para">
+ </div><pre class="screen">~]# <code class="command">cat /dev/oprofile/0/count</code></pre></div><div class="section" id="s1-oprofile-example-usage"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.8. Example Usage</h2></div></div></div><div class="para">
While OProfile can be used by developers to analyze application performance, it can also be used by system administrators to perform system analysis. For example:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <span class="emphasis"><em>Determine which applications and services are used the most on a system</em></span> — <code class="command">opreport</code> can be used to determine how much processor time an application or service uses. If the system is used for multiple services but is under performing, the services consuming the most processor time can be moved to dedicated systems.
+ <span class="emphasis"><em>Determine which applications and services are used the most on a system</em></span> — <code class="command">opreport</code> can be used to determine how much processor time an application or service uses. If the system is used for multiple services but is underperforming, the services consuming the most processor time can be moved to dedicated systems.
</div></li><li class="listitem"><div class="para">
<span class="emphasis"><em>Determine processor usage</em></span> — The <code class="computeroutput">CPU_CLK_UNHALTED</code> event can be monitored to determine the processor load over a given period of time. This data can then be used to determine if additional processors or a faster processor might improve system performance.
- </div></li></ul></div></div><div class="section" id="s1-oprofile-java-support"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.8. OProfile Support for Java</h2></div></div></div><a id="idm225479558848" class="indexterm"></a><div class="para">
- OProfile allows you to profile dynamically compiled code (also known as "just-in-time" or JIT code) of the Java Virtual Machine (JVM). OProfile in Fedora 21 includes build-in support for the JVM Tools Interface (JVMTI) agent library, which supports Java 1.5 and higher.
- </div><div class="section" id="s1-oprofile-java-profiling"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.8.1. Profiling Java Code</h3></div></div></div><div class="para">
+ </div></li></ul></div></div><div class="section" id="s1-oprofile-java-support"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.9. OProfile Support for Java</h2></div></div></div><a id="idm261733098320" class="indexterm"></a><div class="para">
+ OProfile allows you to profile dynamically compiled code (also known as "just-in-time" or JIT code) of the Java Virtual Machine (JVM). OProfile in Fedora 21 includes built-in support for the JVM Tools Interface (JVMTI) agent library, which supports Java 1.5 and higher.
+ </div><div class="section" id="s1-oprofile-java-profiling"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.9.1. Profiling Java Code</h3></div></div></div><div class="para">
To profile JIT code from the Java Virtual Machine with the JVMTI agent, add the following to the JVM startup parameters:
- </div><pre class="screen"><code class="option">-agentlib:jvmti_oprofile</code></pre><div class="note"><div class="admonition_header"><h2>Install the oprofile-jit package</h2></div><div class="admonition"><div class="para">
- The <span class="package">oprofile-jit</span> package must be installed on the system in order to profile JIT code with OProfile.
+ </div><pre class="screen"><code class="option">-agentlib:</code><em class="replaceable"><code>jvmti_oprofile</code></em></pre><div class="para">
+ Where <em class="replaceable"><code>jvmti_oprofile</code></em> is a path to the OProfile agent. For 64-bit JVM, the path looks as follows:
+ </div><pre class="screen"><code class="option">-agentlib:/usr/lib64/oprofile/libjvmti_oprofile.so</code></pre><div class="para">
+ Currently, you can add one command-line option: <code class="option">--debug</code>, which enables debugging mode.
+ </div><div class="note"><div class="admonition_header"><h2>Install the oprofile-jit package</h2></div><div class="admonition"><div class="para">
+ The <span class="package">oprofile-jit</span> package must be installed on the system in order to profile JIT code with OProfile. With this package, you gain the capability to show method-level information.
</div></div></div><div class="para">
- To learn more about Java support in OProfile, refer to the OProfile Manual, which is linked from <a class="xref" href="#s1-oprofile-additional-resources">Section 19.11, “Additional Resources”</a>.
- </div></div></div><div class="section" id="s1-oprofile-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.9. Graphical Interface</h2></div></div></div><a id="idm225453654576" class="indexterm"></a><div class="para">
- Some OProfile preferences can be set with a graphical interface. To start it, execute the <code class="command">oprof_start</code> command as root at a shell prompt. To use the graphical interface, you will need to have the <code class="filename">oprofile-gui</code> package installed.
+ Depending on the JVM that you are using, you may have to install the <span class="emphasis"><em>debuginfo</em></span> package for the JVM. For OpenJDK, this package is required, there is no debuginfo package for Oracle JDK. To keep the debug information packages synchronized with their respective non-debug packages, you also need to install the <span class="emphasis"><em>yum-plugin-auto-update-debug-info</em></span> plug-in. This plug-in searches the debug information repository for corresponding updates.
+ </div><div class="para">
+ After successful setup, you can apply the standard profiling and analyzing tools described in previous sections
+ </div><div class="para">
+ To learn more about Java support in OProfile, see the OProfile Manual, which is linked from <a class="xref" href="#s1-oprofile_additional_resources">Section 19.12, “Additional Resources”</a>.
+ </div></div></div><div class="section" id="s1-oprofile-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.10. Graphical Interface</h2></div></div></div><a id="idm261787983968" class="indexterm"></a><div class="para">
+ Some OProfile preferences can be set with a graphical interface. Make sure you have the <code class="filename">oprofile-gui</code> package that provides the OProfile GUI installed on your system. To start the interface, execute the <code class="command">oprof_start</code> command as root at a shell prompt.
</div><div class="para">
After changing any of the options, save them by clicking the <span class="guibutton"><strong>Save and quit</strong></span> button. The preferences are written to <code class="filename">/root/.oprofile/daemonrc</code>, and the application exits. Exiting the application does not stop OProfile from sampling.
</div><div class="para">
- On the <span class="guilabel"><strong>Setup</strong></span> tab, to set events for the processor counters as discussed in <a class="xref" href="#s2-oprofile-events">Section 19.2.2, “Setting Events to Monitor”</a>, select the counter from the pulldown menu and select the event from the list. A brief description of the event appears in the text box below the list. Only events available for the specific counter and the specific architecture are displayed. The interface also displays whether the profiler is running and some brief statistics about it.
+ On the <span class="guilabel"><strong>Setup</strong></span> tab, to set events for the processor counters as discussed in <a class="xref" href="#s2-oprofile-events">Section 19.3.2, “Setting Events to Monitor”</a>, select the counter from the pulldown menu and select the event from the list. A brief description of the event appears in the text box below the list. Only events available for the specific counter and the specific architecture are displayed. The interface also displays whether the profiler is running and some brief statistics about it.
</div><div class="figure" id="fig-oprofile-setup"><div class="figure-contents"><div class="mediaobject"><img src="images/oprof-start-setup.png" alt="OProfile Setup" /><div class="longdesc"><div class="para">
<code class="command">oprof_start</code> interface
</div></div></div></div><h6>Figure 19.1. OProfile Setup</h6></div><br class="figure-break" /><div class="para">
- On the right side of the tab, select the <span class="guilabel"><strong>Profile kernel</strong></span> option to count events in kernel mode for the currently selected event, as discussed in <a class="xref" href="#s2-oprofile-starting-separate">Section 19.2.3, “Separating Kernel and User-space Profiles”</a>. If this option is unselected, no samples are collected for the kernel.
+ On the right side of the tab, select the <span class="guilabel"><strong>Profile kernel</strong></span> option to count events in kernel mode for the currently selected event, as discussed in <a class="xref" href="#s2-oprofile-starting-separate">Section 19.3.3, “Separating Kernel and User-space Profiles”</a>. If this option is not selected, no samples are collected for the kernel.
</div><div class="para">
- Select the <span class="guilabel"><strong>Profile user binaries</strong></span> option to count events in user mode for the currently selected event, as discussed in <a class="xref" href="#s2-oprofile-starting-separate">Section 19.2.3, “Separating Kernel and User-space Profiles”</a>. If this option is unselected, no samples are collected for user applications.
+ Select the <span class="guilabel"><strong>Profile user binaries</strong></span> option to count events in user mode for the currently selected event, as discussed in <a class="xref" href="#s2-oprofile-starting-separate">Section 19.3.3, “Separating Kernel and User-space Profiles”</a>. If this option is not selected, no samples are collected for user applications.
</div><div class="para">
- Use the <span class="guilabel"><strong>Count</strong></span> text field to set the sampling rate for the currently selected event as discussed in <a class="xref" href="#s3-oprofile-events-sampling">Section 19.2.2.1, “Sampling Rate”</a>.
+ Use the <span class="guilabel"><strong>Count</strong></span> text field to set the sampling rate for the currently selected event as discussed in <a class="xref" href="#s3-oprofile-events-sampling">Section 19.3.2.1, “Sampling Rate”</a>.
</div><div class="para">
- If any unit masks are available for the currently selected event, as discussed in <a class="xref" href="#s3-oprofile-events-unit-masks">Section 19.2.2.2, “Unit Masks”</a>, they are displayed in the <span class="guilabel"><strong>Unit Masks</strong></span> area on the right side of the <span class="guilabel"><strong>Setup</strong></span> tab. Select the checkbox beside the unit mask to enable it for the event.
+ If any unit masks are available for the currently selected event, as discussed in <a class="xref" href="#s3-oprofile-events-unit-masks">Section 19.3.2.2, “Unit Masks”</a>, they are displayed in the <span class="guilabel"><strong>Unit Masks</strong></span> area on the right side of the <span class="guilabel"><strong>Setup</strong></span> tab. Select the check box beside the unit mask to enable it for the event.
</div><div class="para">
On the <span class="guilabel"><strong>Configuration</strong></span> tab, to profile the kernel, enter the name and location of the <code class="filename">vmlinux</code> file for the kernel to monitor in the <span class="guilabel"><strong>Kernel image file</strong></span> text field. To configure OProfile not to monitor the kernel, select <span class="guilabel"><strong>No kernel image</strong></span>.
</div><div class="figure" id="fig-oprofile-configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/oprof-start-config.png" alt="OProfile Configuration" /><div class="longdesc"><div class="para">
OProfile Configuration
</div></div></div></div><h6>Figure 19.2. OProfile Configuration</h6></div><br class="figure-break" /><div class="para">
- If the <span class="guilabel"><strong>Verbose</strong></span> option is selected, the <code class="command">oprofiled</code> daemon log includes more information.
+ If the <span class="guilabel"><strong>Verbose</strong></span> option is selected, the <code class="command">oprofiled</code> daemon log includes more detailed information.
</div><div class="para">
- If <span class="guilabel"><strong>Per-application profiles</strong></span> is selected, OProfile generates per-application profiles for libraries. This is equivalent to the <code class="command">opcontrol --separate=library</code> command. If <span class="guilabel"><strong>Per-application profiles, including kernel</strong></span> is selected, OProfile generates per-application profiles for the kernel and kernel modules as discussed in <a class="xref" href="#s2-oprofile-starting-separate">Section 19.2.3, “Separating Kernel and User-space Profiles”</a>. This is equivalent to the <code class="command">opcontrol --separate=kernel</code> command.
+ If <span class="guilabel"><strong>Per-application profiles</strong></span> is selected, OProfile generates per-application profiles for libraries. This is equivalent to the <code class="command">opcontrol --separate=library</code> command. If <span class="guilabel"><strong>Per-application profiles, including kernel</strong></span> is selected, OProfile generates per-application profiles for the kernel and kernel modules as discussed in <a class="xref" href="#s2-oprofile-starting-separate">Section 19.3.3, “Separating Kernel and User-space Profiles”</a>. This is equivalent to the <code class="command">opcontrol --separate=kernel</code> command.
</div><div class="para">
- To force data to be written to samples files as discussed in <a class="xref" href="#s1-oprofile-analyzing-data">Section 19.5, “Analyzing the Data”</a>, click the <span class="guibutton"><strong>Flush</strong></span> button. This is equivalent to the <code class="command">opcontrol --dump</code> command.
+ To force data to be written to samples files as discussed in <a class="xref" href="#s1-oprofile-analyzing-data">Section 19.6, “Analyzing the Data”</a>, click the <span class="guibutton"><strong>Flush</strong></span> button. This is equivalent to the <code class="command">opcontrol --dump</code> command.
</div><div class="para">
To start OProfile from the graphical interface, click <span class="guibutton"><strong>Start</strong></span>. To stop the profiler, click <span class="guibutton"><strong>Stop</strong></span>. Exiting the application does not stop OProfile from sampling.
- </div></div><div class="section" id="s1-oprofile-and-systemtap"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.10. OProfile and SystemTap</h2></div></div></div><a id="idm225460174784" class="indexterm"></a><div class="para">
- SystemTap is a tracing and probing tool that allows users to study and monitor the activities of the operating system in fine detail. It provides information similar to the output of tools like <code class="command">netstat</code>, <code class="command">ps</code>, <code class="command">top</code>, and <code class="command">iostat</code>; however, SystemTap is designed to provide more filtering and analysis options for collected information.
+ </div></div><div class="section" id="s1-oprofile-and-systemtap"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.11. OProfile and SystemTap</h2></div></div></div><a id="idm261752767504" class="indexterm"></a><div class="para">
+ SystemTap is a tracing and probing tool that allows users to study and monitor the activities of the operating system in fine detail. It provides information similar to the output of tools like <code class="command">netstat</code>, <code class="command">ps</code>, <code class="command">top</code>, and <code class="command">iostat</code>; however, SystemTap is designed to provide more filtering and analysis options for the collected information.
</div><div class="para">
While using OProfile is suggested in cases of collecting data on where and why the processor spends time in a particular area of code, it is less usable when finding out why the processor stays idle.
</div><div class="para">
- You might want to use SystemTap when instrumenting specific places in code. Because SystemTap allows you to run the code instrumentation without having to stop and restart the instrumentation, it is particularly useful for instrumenting the kernel and daemons.
+ You might want to use SystemTap when instrumenting specific places in code. Because SystemTap allows you to run the code instrumentation without having to stop and restart the instrumented code, it is particularly useful for instrumenting the kernel and daemons.
+ </div><div class="para">
+ For more information on SystemTap, see <a class="xref" href="#br-oprofile_online_documentation">the section called “Online Documentation”</a> for the relevant SystemTap documentation.
+ </div></div><div class="section" id="s1-oprofile_additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.12. Additional Resources</h2></div></div></div><a id="idm261748311616" class="indexterm"></a><div class="para">
+ To learn more about OProfile and how to configure it, see the following resources.
+ </div><h3 id="br-oprofile_installed_documentation">Installed Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/oprofile/oprofile.html</code> — <em class="citetitle">OProfile Manual</em>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">oprofile(1)</code> manual page — Discusses <code class="command">opcontrol</code>, <code class="command">opreport</code>, <code class="command">opannotate</code>, and <code class="command">ophelp</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">operf(1)</code> manual page
+ </div></li></ul></div><h3 id="br-oprofile_online_documentation">Online Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://oprofile.sourceforge.net/">http://oprofile.sourceforge.net/</a> — Contains the latest upstream documentation, mailing lists, IRC channels, and more.
+ </div></li></ul></div><h3 id="br-oprofile_see_also">See Also</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SystemTap_Beginners_Guide/index.html">SystemTap Beginners Guide</a> — Provides basic instructions on how to use SystemTap to monitor different subsystems of Fedora in finer detail.
+ </div></li></ul></div></div></div></div><div class="part" id="part-Kernel_Module_and_Driver_Configuration"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part VI. Kernel, Module and Driver Configuration</h1></div></div></div><div class="partintro" id="idm261733176720"><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 class="toc"><dt><span class="chapter"><a href="#ch-Working_with_the_GRUB_2_Boot_Loader">20. Working with the GRUB 2 Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configuring_the_GRUB_2_Boot_Loader">20.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="#sec-Customizing_GRUB_2_Menu">20.2. Customizing GRUB 2 Menu</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Changing_the_Default_Boot_Entry">20.2.1. Changing the Default Boot Entry</a></span></dt><dt><span class="section"><a href="#sec-Editing_an_Entry">20.2.2. Editing an Entry</a></span></dt><dt><span class="section"><a href="#sec-Adding_a_new_Entry">20.2.3. Adding a new Entry</a></span></dt><dt><span class="section"><a href="#sec-Using_only_a_Custom_Menu">20.2.4. Creating a Custom Menu</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-GRUB_2_Password_Protection"
>20.3. GRUB 2 Password Protection</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries">20.3.1. Setting Up Users and Password Protection, Specifying Menu Entries</a></span></dt><dt><span class="section"><a href="#sec-Password_Encryption">20.3.2. Password Encryption</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Reinstalling_GRUB_2">20.4. Reinstalling GRUB 2</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Using_the_grub2-install_Command">20.4.1. Using the grub2-install Command</a></span></dt><dt><span class="section"><a href="#sec-Resetting_and_Reinstalling_GRUB_2">20.4.2. Resetting and Reinstalling GRUB 2</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-GRUB_2_over_Serial_Console">20.5. GRUB 2 over Serial Console</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configuring_GRUB_2">20.5.1. Configuring GRUB 2</a></span></dt><dt><span class="
section"><a href="#sec-Using_screen_to_Connect_to_the_Serial_Console">20.5.2. Using screen to Connect to the Serial Console</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Terminal_Menu_Editing_During_Boot">20.6. Terminal Menu Editing During Boot</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Booting_to_Rescue_Mode">20.6.1. Booting to Rescue Mode</a></span></dt><dt><span class="section"><a href="#sec-Booting_to_Emergency_Mode">20.6.2. Booting to Emergency Mode</a></span></dt><dt><span class="section"><a href="#sec-Changing_and_Resetting_the_Root_Password">20.6.3. Changing and Resetting the Root Password</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-UEFI_Secure_Boot">20.7. UEFI Secure Boot</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-UEFI_Secure_Boot_Support_in_Fedora">20.7.1. UEFI Secure Boot Support in Fedora</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Working_with_the_GRUB_2_Boot_Loa
der-Additional_Resources">20.8. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="#ch-Manually_Upgrading_the_Kernel">21. Manually Upgrading the Kernel</a></span></dt><dd><dl><dt><span class="section"><a href="#s1-kernel-packages">21.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="#s1-kernel-preparing">21.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="#s1-kernel-download">21.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="#s1-kernel-perform-upgrade">21.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="#sec-Verifying_the_Initial_RAM_Disk_Image">21.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="#s1-kernel-boot-loader">21.6. Verifying the Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-kernel-boot-loader-grub">21.6.1. Configuring the GRUB 2 Boot Loader</a></sp
an></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-iseries">21.6.2. Configuring the OS/400 Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-pseries">21.6.3. Configuring the YABOOT Boot Loader</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="#ch-Working_with_Kernel_Modules">22. Working with Kernel Modules</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="#sec-Displaying_Information_About_a_Module">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="#sec-Loading_a_Module">22.3. Loading a Module</a></span></dt><dt><span class="section"><a href="#sec-Unloading_a_Module">22.4. Unloading a Module</a></span></dt><dt><span class="section"><a href="#sec-Setting_Module_Parameters">22.5. Setting Module Parameters</a></span></dt><dt><span cl
ass="section"><a href="#sec-Persistent_Module_Loading">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="#sect-signing-kernel-modules-for-secure-boot">22.7. Signing Kernel Modules for Secure Boot</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-prerequisites">22.7.1. Prerequisites</a></span></dt><dt><span class="section"><a href="#sect-kernel-module-authentication">22.7.2. Kernel Module Authentication</a></span></dt><dt><span class="section"><a href="#sect-generating-a-public-private-x509-key-pair">22.7.3. Generating a Public and Private X.509 Key Pair</a></span></dt><dt><span class="section"><a href="#sect-enrolling-public-key-on-target-system">22.7.4. Enrolling Public Key on Target System</a></span></dt><dt><span class="section"><a href="#sect-signing-kernel-module-with-the-private-key">22.7.5. Signing Kernel Module with the Private Key</a></span></dt><dt><span class="section"><a href="#sect-loading-signed-kernel-module">22.7.
6. Loading Signed Kernel Module</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kernel-modules-additional-resources">22.8. Additional Resources</a></span></dt></dl></dd></dl></div></div><div xml:lang="en-US" class="chapter" id="ch-Working_with_the_GRUB_2_Boot_Loader" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 20. Working with the GRUB 2 Boot Loader</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sec-Configuring_the_GRUB_2_Boot_Loader">20.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="#sec-Customizing_GRUB_2_Menu">20.2. Customizing GRUB 2 Menu</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Changing_the_Default_Boot_Entry">20.2.1. Changing the Default Boot Entry</a></span></dt><dt><span class="section"><a href="#sec-Editing_an_Entry">20.2.2. Editing an Entry</a></span></dt><dt><span class="section"><a href="#sec-Adding_a_new_Entry">
20.2.3. Adding a new Entry</a></span></dt><dt><span class="section"><a href="#sec-Using_only_a_Custom_Menu">20.2.4. Creating a Custom Menu</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-GRUB_2_Password_Protection">20.3. GRUB 2 Password Protection</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries">20.3.1. Setting Up Users and Password Protection, Specifying Menu Entries</a></span></dt><dt><span class="section"><a href="#sec-Password_Encryption">20.3.2. Password Encryption</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Reinstalling_GRUB_2">20.4. Reinstalling GRUB 2</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Using_the_grub2-install_Command">20.4.1. Using the grub2-install Command</a></span></dt><dt><span class="section"><a href="#sec-Resetting_and_Reinstalling_GRUB_2">20.4.2. Resetting and Reinstalling GRUB 2</a></span></dt></dl></dd><dt><span cl
ass="section"><a href="#sec-GRUB_2_over_Serial_Console">20.5. GRUB 2 over Serial Console</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Configuring_GRUB_2">20.5.1. Configuring GRUB 2</a></span></dt><dt><span class="section"><a href="#sec-Using_screen_to_Connect_to_the_Serial_Console">20.5.2. Using screen to Connect to the Serial Console</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Terminal_Menu_Editing_During_Boot">20.6. Terminal Menu Editing During Boot</a></span></dt><dd><dl><dt><span class="section"><a href="#sec-Booting_to_Rescue_Mode">20.6.1. Booting to Rescue Mode</a></span></dt><dt><span class="section"><a href="#sec-Booting_to_Emergency_Mode">20.6.2. Booting to Emergency Mode</a></span></dt><dt><span class="section"><a href="#sec-Changing_and_Resetting_the_Root_Password">20.6.3. Changing and Resetting the Root Password</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-UEFI_Secure_Boot">20.7. UEFI Secure Boot</a></spa
n></dt><dd><dl><dt><span class="section"><a href="#sec-UEFI_Secure_Boot_Support_in_Fedora">20.7.1. UEFI Secure Boot Support in Fedora</a></span></dt></dl></dd><dt><span class="section"><a href="#sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources">20.8. Additional Resources</a></span></dt></dl></div><a id="idm261754124016" class="indexterm"></a><a id="idm261739290256" class="indexterm"></a><a id="idm261752313296" class="indexterm"></a><a id="idm261715047856" class="indexterm"></a><div class="para">
+ Fedora 21 is distributed with the GNU GRand Unified Boot loader (GRUB) version 2 boot loader, which allows the user to select an operating system or kernel to be loaded at system boot time. GRUB 2 also allows the user to pass arguments to the kernel.
+ </div><div class="section" id="sec-Configuring_the_GRUB_2_Boot_Loader"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.1. Configuring the GRUB 2 Boot Loader</h2></div></div></div><div class="para">
+ GRUB 2 reads its configuration from the <code class="filename">/boot/grub2/grub.cfg</code> file on traditional BIOS-based machines and from the <code class="filename">/boot/efi/EFI/redhat/grub.cfg</code> file on UEFI machines. This file contains menu information, however, it is not supposed to be edited as it is generated by the <span class="application"><strong>/usr/sbin/grub2-mkconfig</strong></span> utility based on Linux kernels located in the <code class="filename">/boot/</code> directory, template files located in <code class="filename">/etc/grub.d/</code>, and custom settings in the <code class="filename">/etc/default/grub</code> file. Any manual edits could therefore cause the changes to be lost during updates. The GRUB 2 configuration file, <code class="filename">grub.cfg</code>, is automatically updated each time a new kernel is installed. Note that any changes to <code class="filename">/etc/default/grub</code> require rebuilding the <code class="filename">grub.
cfg</code> file. To update the GRUB 2 configuration file manually, use the <code class="command">grub2-mkconfig <code class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div class="para">
+ On UEFI-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div><div class="para">
+ Among various code snippets and directives, the <code class="filename">grub.cfg</code> configuration file contains one or more <code class="literal">menuentry</code> blocks, each representing a single GRUB 2 boot menu entry. These blocks always start with the <code class="literal">menuentry</code> keyword followed by a title, list of options, and an opening curly bracket, and end with a closing curly bracket. Anything between the opening and closing bracket should be indented. For example, the following is a sample <code class="literal">menuentry</code> block for Fedora 21 with Linux kernel 3.17.4-301.fc21.x86_64:
+ </div><pre class="programlisting">
+menuentry 'Fedora, with Linux 3.17.4-301.fc21.x86_64' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.17.4-301.fc21.x86_64-advanced-effee860-8d55-4e4a-995e-b4c88f9ac9f0' {
+ load_video
+ set gfxpayload=keep
+ insmod gzio
+ insmod part_msdos
+ insmod ext2
+ set root='hd0,msdos1'
+ if [ x$feature_platform_search_hint = xy ]; then
+ search --no-floppy --fs-uuid --set=root --hint='hd0,msdos1' f19c92f4-9ead-4207-b46a-723b7a2c51c8
+ else
+ search --no-floppy --fs-uuid --set=root f19c92f4-9ead-4207-b46a-723b7a2c51c8
+ fi
+ linux16 /vmlinuz-3.17.4-301.fc21.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
+ initrd16 /initramfs-3.17.4-301.fc21.x86_64.img
+}
+</pre><div class="para">
+ Each <code class="literal">menuentry</code> block that represents an installed Linux kernel contains <code class="literal">linux</code> on 64-bit IBM POWER Series, <code class="literal">linux16</code> on x86_64 BIOS-based systems, and <code class="literal">linuxefi</code> on UEFI-based systems. Then the <code class="literal">initrd</code> directives followed by the path to the kernel and the <code class="systemitem">initramfs</code> image respectively. If a separate <code class="filename">/boot</code> partition was created, the paths to the kernel and the <code class="systemitem">initramfs</code> image are relative to <code class="filename">/boot</code>. In the example above, the <code class="literal">initrd /initramfs-3.8.0-0.40.el7.x86_64.img</code> line means that the <code class="systemitem">initramfs</code> image is actually located at <code class="filename">/boot/initramfs-3.8.0-0.40.el7.x86_64.img</code> when the <code class="systemitem">root</code> file system is
mounted, and likewise for the kernel path.
+ </div><div class="para">
+ The kernel version number as given on the <code class="literal">linux16 /vmlinuz-kernel_version</code> line must match the version number of the <code class="systemitem">initramfs</code> image given on the <code class="literal">initrd /initramfs-kernel_version.img</code> line of each <code class="literal">menuentry</code> block. For more information on how to verify the initial RAM disk image, see <a class="xref" href="#sec-Verifying_the_Initial_RAM_Disk_Image">Section 21.5, “Verifying the Initial RAM Disk Image”</a>.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ In <code class="literal">menuentry</code> blocks, the <code class="computeroutput">initrd</code> directive must point to the location (relative to the <code class="filename">/boot/</code> directory if it is on a separate partition) of the <code class="filename">initramfs</code> file corresponding to the same kernel version. This directive is called <code class="literal">initrd</code> because the previous tool which created initial RAM disk images, <code class="command">mkinitrd</code>, created what were known as <code class="systemitem">initrd</code> files. The <code class="filename">grub.cfg</code> directive remains <code class="systemitem">initrd</code> to maintain compatibility with other tools. The file-naming convention of systems using the <code class="command">dracut</code> utility to create the initial RAM disk image is <code class="filename">initramfs-<em class="replaceable"><code>kernel_version</code></em>.img</code>.
+ </div><div class="para">
+ For information on using <span class="application"><strong>Dracut</strong></span>, see <a class="xref" href="#sec-Verifying_the_Initial_RAM_Disk_Image">Section 21.5, “Verifying the Initial RAM Disk Image”</a>.
+ </div></div></div></div><div class="section" id="sec-Customizing_GRUB_2_Menu"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.2. Customizing GRUB 2 Menu</h2></div></div></div><div class="para">
+ GRUB 2 scripts search the user's computer and build a boot menu based on what operating systems the scripts find. To reflect the latest system boot options, the boot menu is rebuilt automatically when the kernel is updated or a new kernel is added.
+ </div><div class="para">
+ However, users may want to build a menu containing specific entries or to have the entries in a specific order. GRUB 2 allows basic customization of the boot menu to give users control of what actually appears on the screen.
</div><div class="para">
- For more information on SystemTap, refer to <a class="xref" href="#s2-oprofile-useful-websites">Section 19.11.2, “Useful Websites”</a> for the relevant SystemTap documentation.
- </div></div><div class="section" id="s1-oprofile-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.11. Additional Resources</h2></div></div></div><a id="idm225460140224" class="indexterm"></a><div class="para">
- This chapter only highlights OProfile and how to configure and use it. To learn more, refer to the following resources.
- </div><div class="section" id="s1-oprofile-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.11.1. Installed Docs</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <code class="filename">/usr/share/doc/oprofile/oprofile.html</code> — <em class="citetitle">OProfile Manual</em>
+ GRUB 2 uses a series of scripts to build the menu; these are located in the <code class="filename">/etc/grub.d/</code> directory. The following files are included:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">00_header</code>, which loads GRUB 2 settings from the <code class="filename">/etc/default/grub</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">01_users</code>, which is created only when a boot loader password is assigned in a <span class="application"><strong>kickstart</strong></span> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">10_linux</code>, which locates kernels in the default partition of Fedora.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">30_os-prober</code>, which builds entries for operating systems found on other partitions.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">40_custom</code>, a template, which can be used to create additional menu entries.
+ </div></li></ul></div><div class="para">
+ Scripts from the <code class="filename">/etc/grub.d/</code> directory are read in alphabetical order and can be therefore renamed to change the boot order of specific menu entries.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ With the <code class="option">GRUB_TIMEOUT</code> key set to <code class="literal">0</code> in the <code class="filename">/etc/default/grub</code> file, GRUB 2 does not display the list of bootable kernels when the system starts up. In order to display this list when booting, press and hold any alphanumeric key when the BIOS information is displayed; GRUB 2 will present you with the GRUB menu.
+ </div></div></div><div class="section" id="sec-Changing_the_Default_Boot_Entry"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.2.1. Changing the Default Boot Entry</h3></div></div></div><div class="para">
+ By default, the key for the <code class="literal">GRUB_DEFAULT</code> directive in the <code class="filename">/etc/default/grub</code> file is the word <code class="literal">saved</code>. This instructs GRUB 2 to load the kernel specified by the <code class="option">saved_entry</code> directive in the GRUB 2 environment file, located at <code class="filename">/boot/grub2/grubenv</code>. You can set another GRUB record to be the default, using the <code class="command">grub2-set-default</code> command, which will update the GRUB 2 environment file.
+ </div><div class="para">
+ By default, the <code class="option">saved_entry</code> value is set to the name of latest installed kernel of package type <span class="package">kernel</span>. This is defined in <code class="filename">/etc/sysconfig/kernel</code> by the <code class="literal">UPDATEDEFAULT</code> and <code class="literal">DEFAULTKERNEL</code> directives. The file can be viewed by the <code class="systemitem">root</code> user as follows:
+<pre class="screen">~]# <code class="command">cat /etc/sysconfig/kernel</code>
+# UPDATEDEFAULT specifies if new-kernel-pkg should make
+# new kernels the default
+UPDATEDEFAULT=yes
+
+# DEFAULTKERNEL specifies the default kernel package type
+DEFAULTKERNEL=kernel-core</pre>
+ The <code class="literal">DEFAULTKERNEL</code> directive specifies what package type will be used as the default. Installing a package of type <span class="package">kernel-debug</span> will not change the default kernel while the <code class="literal">DEFAULTKERNEL</code> is set to package type <span class="package">kernel</span>.
+ </div><div class="para">
+ GRUB 2 supports using a numeric value as the key for the <code class="option">saved_entry</code> directive to change the default order in which the operating systems are loaded. To specify which operating system should be loaded first, pass its number to the <code class="command">grub2-set-default</code> command. For example:
+ </div><pre class="screen">~]# <code class="command">grub2-set-default</code> <code class="literal">2</code></pre><div class="para">
+ Note that the position of a menu entry in the list is denoted by a number starting with zero; therefore, in the example above, the third entry will be loaded. This value will be overwritten by the name of the next kernel to be installed.
+ </div><div class="para">
+ To force a system to always use a particular menu entry, use the menu entry name as the key to the <code class="literal">GRUB_DEFAULT</code> directive in the <code class="filename">/etc/default/grub</code> file. To list the available menu entries, run the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">awk -F\' '$1=="menuentry " {print $2}' /etc/grub2.cfg</code></pre>
+ Changes to <code class="filename">/etc/default/grub</code> require rebuilding the <code class="filename">grub.cfg</code> file as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/grub2/grub.cfg</code></pre>
+
</div></li><li class="listitem"><div class="para">
- <code class="command">oprofile</code> man page — Discusses <code class="command">opcontrol</code>, <code class="command">opreport</code>, <code class="command">opannotate</code>, and <code class="command">ophelp</code>
- </div></li></ul></div></div><div class="section" id="s2-oprofile-useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.11.2. Useful Websites</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <a href="http://oprofile.sourceforge.net/">http://oprofile.sourceforge.net/</a> — Contains the latest documentation, mailing lists, IRC channels, and more.
+ On UEFI-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></div><div class="section" id="sec-Editing_an_Entry"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.2.2. Editing an Entry</h3></div></div></div><h4 id="idm261755941952">Kernel Parameters</h4><div class="para">
+ To use a kernel parameter only during a single boot process, when the GRUB 2 boot menu appears, move the cursor to the kernel you want to start, and press the <span class="keycap"><strong>e</strong></span> key to edit the kernel parameters. For example, to run the system in emergency mode, add the <span class="emphasis"><em>emergency</em></span> parameter at the end of the <code class="literal">linux16</code> line:
+ </div><pre class="screen">linux16 /vmlinuz-3.17.4-301.fc21.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8 emergency</pre><div class="para">
+ These settings are not persistent and apply only for a single boot. To make the settings persistent, edit values of the <code class="systemitem">GRUB_CMDLINE_LINUX</code> key in the <code class="filename">/etc/default/grub</code> file. For example, if you want to enable emergency mode for each boot, use:
+ </div><pre class="screen">GRUB_CMDLINE_LINUX="emergency"</pre><div class="para">
+ Note that you can specify multiple parameters for the <code class="systemitem">GRUB_CMDLINE_LINUX</code> key, similarly to adding the parameters in the GRUB 2 boot menu. For example: <pre class="synopsis">GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,9600n8"</pre> Where <code class="option">console=tty0</code> is the first virtual terminal and <code class="option">console=ttyS0</code> is the serial terminal to be used.
+ </div><div class="para">
+ Changes to <code class="filename">/etc/default/grub</code> require rebuilding the <code class="filename">grub.cfg</code> file as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/grub2/grub.cfg</code></pre>
+
</div></li><li class="listitem"><div class="para">
- <a href="http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/SystemTap_Beginners_Guide/index.html">SystemTap Beginners Guide</a> — Provides basic instructions on how to use SystemTap to monitor different subsystems of Fedora in finer detail.
- </div></li></ul></div></div></div></div></div><div class="part" id="part-Kernel_Module_and_Driver_Configuration"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part VI. Kernel, Module and Driver Configuration</h1></div></div></div><div class="partintro" id="idm225424994576"><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 class="toc"><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 2 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><sp
an class="section"><a href="#sec-Persistent_Module_Loading">21.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="#s1-kernel-modules-additional-resources">21.7. Additional Resources</a></span></dt></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 class="toc"><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 2 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="idm225460510400" class="indexterm"></a><a id="idm225439191392" class="indexterm"></a><a id="idm225356568000" class="indexterm"></a><a id="idm225427422416" class="indexterm"></a><div class="para">
+ On UEFI-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></div><div class="section" id="sec-Adding_a_new_Entry"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.2.3. Adding a new Entry</h3></div></div></div><div class="para">
+ When executing the <code class="command">grub2-mkconfig</code> command, GRUB 2 searches for Linux kernels and other operating systems based on the files located in the <code class="filename">/etc/grub.d/</code> directory. The <code class="filename">/etc/grub.d/10_linux</code> script searches for installed Linux kernels on the same partition. The <code class="filename">/etc/grub.d/30_os-prober</code> script searches for other operating systems. Menu entries are also automatically added to the boot menu when updating the kernel.
+ </div><div class="para">
+ The <code class="filename">40_custom</code> file located in the <code class="filename">/etc/grub.d/</code> directory is a template for custom entries and looks as follows:
+ </div><pre class="programlisting"><span class="perl_Comment">#!/bin/sh</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span><span class="perl_Reserved">exec</span> <span class="perl_BString">tail</span> -n +3 <span class="perl_Others">$0</span>
+<span class="perl_Comment"># This file provides an easy way to add custom menu entries. Simply type the</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span><span class="perl_Comment"># menu entries you want to add after this comment. Be careful not to change</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span><span class="perl_Comment"># the 'exec tail' line above.</span></pre><div class="para">
+ This file can be edited or copied. Note that as a minimum, a valid menu entry must include at least the following:
+ </div><pre class="screen"><span class="strong strong"><strong>menuentry</strong></span> "<Title>"<span class="strong strong"><strong>{</strong></span>
+<Data>
+<span class="strong strong"><strong>}</strong></span></pre></div><div class="section" id="sec-Using_only_a_Custom_Menu"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.2.4. Creating a Custom Menu</h3></div></div></div><div class="para">
+ If you do not want menu entries to be updated automatically, you can create a custom menu.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Before proceeding, back up the contents of the <code class="filename">/etc/grub.d/</code> directory in case you need to revert the changes later.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that modifying the <code class="filename">/etc/default/grub</code> file does not have any effect on creating custom menus.
+ </div></div></div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ On BIOS-based machines, copy the contents of <code class="filename">/boot/grub2/grub.cfg</code>, or, on UEFI machines, copy the contents of <code class="filename">/boot/efi/EFI/redhat/grub.cfg</code>. Put the content of the <code class="filename">grub.cfg</code> into the <code class="filename">/etc/grub.d/40_custom</code> file below the existing header lines. The executable part of the <code class="filename">40_custom</code> script has to be preserved.
+ </div></li><li class="step"><div class="para">
+ From the content put into the <code class="filename">/etc/grub.d/40_custom</code> file, only the <code class="literal">menuentry</code> blocks are needed to create the custom menu. The <code class="filename">/boot/grub2/grub.cfg</code> and <code class="filename">/boot/efi/EFI/redhat/grub.cfg</code> files might contain function specifications and other content above and below the <code class="literal">menuentry</code> blocks. If you put these unnecessary lines into the <code class="filename">40_custom</code> file in the previous step, erase them.
+ </div><div class="para">
+ This is an example of a custom <code class="filename">40_custom</code> script:
+ </div><pre class="programlisting"><span class="perl_Comment">#!/bin/sh</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span><span class="perl_Reserved">exec</span> <span class="perl_BString">tail</span> -n +3 <span class="perl_Others">$0</span>
+<span class="perl_Comment"># This file provides an easy way to add custom menu entries. Simply type the</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span><span class="perl_Comment"># menu entries you want to add after this comment. Be careful not to change</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span><span class="perl_Comment"># the 'exec tail' line above.</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span>
+menuentry <span class="perl_String">'First custom entry'</span> --class <span class="perl_BString">red</span> --class gnu-linux --class gnu --class os <span class="perl_Others">$menuentry_id_option</span> <span class="perl_String">'gnulinux-3.10.0-67.el7.x86_64-advanced-32782dd0-4b47-4d56-a740-2076ab5e5976'</span> <span class="perl_Keyword">{</span>
+ load_video
+ <span class="perl_Keyword">set</span> <span class="perl_Others">gfxpayload=</span>keep
+ insmod gzio
+ insmod part_msdos
+ insmod xfs
+ <span class="perl_Keyword">set</span> <span class="perl_Others">root=</span><span class="perl_String">'hd0,msdos1'</span>
+ <span class="perl_Keyword">if</span><span class="perl_Reserved"> [</span> x<span class="perl_Others">$feature_platform_search_hint</span> = xy<span class="perl_Reserved"> ]</span>; <span class="perl_Keyword">then</span>
+ search --no-floppy --fs-uuid --set=root --hint=<span class="perl_String">'hd0,msdos1'</span> 7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">else</span>
+ search --no-floppy --fs-uuid --set=root 7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">fi</span>
+ linux16 /vmlinuz-3.10.0-67.el7.x86_64 <span class="perl_Others">root=</span>/dev/mapper/rhel-root ro rd.lvm.<span class="perl_Others">lv=</span>rhel/root vconsole.<span class="perl_Others">font=</span>latarcyrheb-sun16 rd.lvm.<span class="perl_Others">lv=</span>rhel/swap vconsole.<span class="perl_Others">keymap=</span>us <span class="perl_Others">crashkernel=</span>auto rhgb quiet <span class="perl_Others">LANG=</span>en_US.UTF-8
+ initrd16 /initramfs-3.10.0-67.el7.x86_64.img
+<span class="perl_Keyword">}</span>
+menuentry <span class="perl_String">'Second custom entry'</span> --class <span class="perl_BString">red</span> --class gnu-linux --class gnu --class os <span class="perl_Others">$menuentry_id_option</span> <span class="perl_String">'gnulinux-0-rescue-07f43f20a54c4ce8ada8b70d33fd001c-advanced-32782dd0-4b47-4d56-a740-2076ab5e5976'</span> <span class="perl_Keyword">{</span>
+ load_video
+ insmod gzio
+ insmod part_msdos
+ insmod xfs
+ <span class="perl_Keyword">set</span> <span class="perl_Others">root=</span><span class="perl_String">'hd0,msdos1'</span>
+ <span class="perl_Keyword">if</span><span class="perl_Reserved"> [</span> x<span class="perl_Others">$feature_platform_search_hint</span> = xy<span class="perl_Reserved"> ]</span>; <span class="perl_Keyword">then</span>
+ search --no-floppy --fs-uuid --set=root --hint=<span class="perl_String">'hd0,msdos1'</span> 7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">else</span>
+ search --no-floppy --fs-uuid --set=root 7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">fi</span>
+ linux16 /vmlinuz-0-rescue-07f43f20a54c4ce8ada8b70d33fd001c <span class="perl_Others">root=</span>/dev/mapper/rhel-root ro rd.lvm.<span class="perl_Others">lv=</span>rhel/root vconsole.<span class="perl_Others">font=</span>latarcyrheb-sun16 rd.lvm.<span class="perl_Others">lv=</span>rhel/swap vconsole.<span class="perl_Others">keymap=</span>us <span class="perl_Others">crashkernel=</span>auto rhgb quiet
+ initrd16 /initramfs-0-rescue-07f43f20a54c4ce8ada8b70d33fd001c.img
+<span class="perl_Keyword">}</span></pre></li><li class="step"><div class="para">
+ Remove all files from the <code class="filename">/etc/grub.d</code> directory except the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">00_header</code>,
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">40_custom</code>,
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">01_users</code> (if it exists),
+ </div></li><li class="listitem"><div class="para">
+ and <code class="filename">README</code>.
+ </div></li></ul></div><div class="para">
+ Alternatively, if you want to keep the files in the <code class="filename">/etc/grub2.d/</code> directory, make them unexecutable by running the <code class="command">chmod <code class="option">a-x</code> <file_name></code> command.
+ </div></li><li class="step"><div class="para">
+ Edit, add, or remove menu entries in the <code class="filename">40_custom</code> file as desired.
+ </div></li><li class="step"><div class="para">
+ Update the <code class="filename">grub.cfg</code> file by running the <code class="command">grub2-mkconfig <code class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div class="para">
+ On UEFI-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></li></ol></div></div></div><div class="section" id="sec-GRUB_2_Password_Protection"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.3. GRUB 2 Password Protection</h2></div></div></div><div class="para">
+ GRUB 2 supports both plain-text and encrypted passwords in the GRUB 2 template files. To enable the use of passwords, specify a superuser who can reach the protected entries. Other users can be specified to access these entries as well. Menu entries can be password-protected for booting by adding one or more users to the menu entry as described in <a class="xref" href="#sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries">Section 20.3.1, “Setting Up Users and Password Protection, Specifying Menu Entries”</a>. To use encrypted passwords, see <a class="xref" href="#sec-Password_Encryption">Section 20.3.2, “Password Encryption”</a>.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ If you do not use the correct format for the menu, or modify the configuration in an incorrect way, you might be unable to boot your system.
+ </div></div></div><div class="para">
+ All menu entries can be password-protected against changes by setting superusers, which can be done in the <code class="filename">/etc/grub.d/00_header</code> or the <code class="filename">/etc/grub.d/01_users</code> file. The <code class="filename">00_header</code> file is very complicated and, if possible, avoid making modifications in this file. Menu entries should be placed in the <code class="filename">/etc/grub.d/40_custom</code> and users in the <code class="filename">/etc/grub.d/01_users</code> file. The <code class="filename">01_users</code> file is generated by the installation application <span class="application"><strong>anaconda</strong></span> when a grub boot loader password is used in a <span class="application"><strong>kickstart</strong></span> template (but it should be created and used it if it does not exist). Examples in this section adopt this policy.
+ </div><div class="section" id="sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.3.1. Setting Up Users and Password Protection, Specifying Menu Entries</h3></div></div></div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To specify a superuser, add the following lines in the <code class="filename">/etc/grub.d/01_users</code> file, where <code class="systemitem">john</code> is the name of the user designated as the superuser, and <code class="literal">johnspassword</code> is the superuser's password:
+ </div><pre class="screen">cat <<EOF
+set superusers="john"
+password john johnspassword
+EOF</pre></li><li class="step"><div class="para">
+ To allow other users to access the menu entries, add additional lines per user at the end of the <code class="filename">/etc/grub.d/01_users</code> file.
+ </div><pre class="screen">cat <<EOF
+set superusers="john"
+password john johnspassword
+password jane janespassword
+EOF</pre></li><li class="step"><div class="para">
+ When the users and passwords are set up, specify the menu entries that should be password-protected in the <code class="filename">/etc/grub.d/40_custom</code> file in a similar fashion to the following:
+ </div><pre class="screen">
+menuentry 'Red Hat Enterprise Linux Server' --unrestricted {
+set root=(hd0,msdos1)
+linux /vmlinuz
+}
+
+menuentry 'Fedora' --users jane {
+set root=(hd0,msdos2)
+linux /vmlinuz
+}
+
+menuentry 'Red Hat Enterprise Linux Workstation' {
+set root=(hd0,msdos3)
+linux /vmlinuz
+}</pre></li></ol></div><div class="para">
+ In the above example:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">john</code> is the <code class="literal">superuser</code> and can therefore boot any menu entry, use the GRUB 2 command line, and edit items of the GRUB 2 menu during boot. In this case, <code class="systemitem">john</code> can access both Red Hat Enterprise Linux Server, Fedora, and Red Hat Enterprise Linux Workstation. Note that only <code class="systemitem">john</code> can access Red Hat Enterprise Linux Workstation because neither the <code class="option">--users</code> nor <code class="option">--unrestricted</code> options have been used.
+ </div></li><li class="listitem"><div class="para">
+ User <code class="systemitem">jane</code> can boot Fedora since she was granted the permission in the configuration.
+ </div></li><li class="listitem"><div class="para">
+ Anyone can boot Red Hat Enterprise Linux Server, because of the <code class="option">--unrestricted</code> option, but only <code class="systemitem">john</code> can edit the menu entry as a superuser has been defined. When a superuser is defined then all records are protected against unauthorized changes and all records are protected for booting if they do <span class="bold bold"><strong>not</strong></span> have the <code class="option">--unrestricted</code> parameter
+ </div></li></ul></div><div class="para">
+
+ </div><div class="para">
+ If you do not specify a user for a menu entry, or make use of the <code class="option">--unrestricted</code> option, then only the superuser will have access to the system.
+ </div><div class="para">
+ After you have made changes in the template file the GRUB 2 configuration file must be updated.
+ </div><div class="para">
+ Update the <code class="filename">grub.cfg</code> file by running the <code class="command">grub2-mkconfig <code class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div class="para">
+ On UEFI-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></div><div class="section" id="sec-Password_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.3.2. Password Encryption</h3></div></div></div><div class="para">
+ By default, passwords are saved in plain text in GRUB 2 scripts. Although the files cannot be accessed on boot without the correct password, security can be improved by encrypting the password using the <code class="command">grub2-mkpasswd-pbkdf2</code> command. This command converts a desired password into a long hash, which is placed in the GRUB 2 scripts instead of the plain-text password.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To generate an encrypted password, run the <code class="command">grub2-mkpasswd-pbkdf2</code> command on the command line as <code class="systemitem">root</code>.
+ </div></li><li class="step"><div class="para">
+ Enter the desired password when prompted and repeat it. The command then outputs your password in an encrypted form.
+ </div></li><li class="step"><div class="para">
+ Copy the hash, and paste it in the template file where you configured the users, that is, either in <code class="filename">/etc/grub.d/01_users</code> or <code class="filename">/etc/grub.d/40_custom</code>.
+ </div><div class="para">
+ The following format applies for the <code class="filename">01_users</code> file:
+<pre class="screen">cat <<EOF
+set superusers="john"
+password_pbkdf2 john grub.pbkdf2.sha512.10000.19074739ED80F115963D984BDCB35AA671C24325755377C3E9B014D862DA6ACC77BC110EED41822800A87FD3700C037320E51E9326188D53247EC0722DDF15FC.C56EC0738911AD86CEA55546139FEBC366A393DF9785A8F44D3E51BF09DB980BAFEF85281CBBC56778D8B19DC94833EA8342F7D73E3A1AA30B205091F1015A85
+EOF</pre>
+ </div><div class="para">
+ The following format applies for the <code class="filename">40_custom</code> file:
+<pre class="screen">set superusers="john"
+password_pbkdf2 john grub.pbkdf2.sha512.10000.19074739ED80F115963D984BDCB35AA671C24325755377C3E9B014D862DA6ACC77BC110EED41822800A87FD3700C037320E51E9326188D53247EC0722DDF15FC.C56EC0738911AD86CEA55546139FEBC366A393DF9785A8F44D3E51BF09DB980BAFEF85281CBBC56778D8B19DC94833EA8342F7D73E3A1AA30B205091F1015A85</pre>
+ </div></li></ol></div></div></div><div class="section" id="sec-Reinstalling_GRUB_2"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.4. Reinstalling GRUB 2</h2></div></div></div><div class="para">
+ Reinstalling GRUB 2 is a convenient way to fix certain problems usually caused by an incorrect installation of GRUB 2, missing files, or a broken system. Other reasons to reinstall GRUB 2 include the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Upgrading from the previous version of GRUB.
+ </div></li><li class="listitem"><div class="para">
+ The user requires the GRUB 2 boot loader to control installed operating systems. However, some operating systems are installed with their own boot loaders. Reinstalling GRUB 2 returns control to the desired operating system.
+ </div></li><li class="listitem"><div class="para">
+ Adding the boot information to another drive.
+ </div></li></ul></div><div class="section" id="sec-Using_the_grub2-install_Command"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.4.1. Using the grub2-install Command</h3></div></div></div><div class="para">
+ When using the <code class="command">grub2-install</code> command, the boot information is updated and missing files are restored. Note that the files are restored only if they are not corrupted. If the <code class="filename">/boot/grub2/</code> directory is missing, it will be recreated.
+ </div><div class="para">
+ Use the <code class="command">grub2-install <device></code> command to reinstall GRUB 2 if the system is operating normally. For example:
+ </div><pre class="screen">~]# <code class="command">grub2-install</code> <code class="filename">/dev/sda</code></pre></div><div class="section" id="sec-Resetting_and_Reinstalling_GRUB_2"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.4.2. Resetting and Reinstalling GRUB 2</h3></div></div></div><div class="para">
+ This method completely removes all GRUB 2 configuration files and system settings. Apply this method to reset all configuration settings to their default values. Removing of the configuration files and subsequent reinstalling of GRUB 2 fixes failures caused by corrupted files and incorrect configuration. To do so, as <code class="systemitem">root</code>, follow these steps:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Run the <code class="command">rm /etc/grub.d/*</code> command;
+ </div></li><li class="step"><div class="para">
+ Run the <code class="command">rm /etc/sysconfig/grub</code> command;
+ </div></li><li class="step"><div class="para">
+ For EFI systems <span class="bold bold"><strong>only</strong></span>, run the following command:
+<pre class="screen">~]# <code class="command">yum reinstall grub2-efi shim</code></pre>
+
+ </div></li><li class="step"><div class="para">
+ Update the <code class="filename">grub.cfg</code> file by running the <code class="command">grub2-mkconfig <code class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div class="para">
+ On UEFI-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></li><li class="step"><div class="para">
+ Now follow the procedure in <a class="xref" href="#sec-Using_the_grub2-install_Command">Section 20.4.1, “Using the grub2-install Command”</a> to restore GRUB2 on the <code class="filename">/boot/</code> partition.
+ </div></li></ol></div></div></div><div class="section" id="sec-GRUB_2_over_Serial_Console"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.5. GRUB 2 over Serial Console</h2></div></div></div><div class="para">
+ If you use computers with no display or keyboard, it can be very useful to control the machines through serial communications.
+ </div><div class="section" id="sec-Configuring_GRUB_2"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.5.1. Configuring GRUB 2</h3></div></div></div><div class="para">
+ In order to use GRUB 2 over a serial line, add the following two lines in the <code class="filename">/etc/default/grub</code> file:
+ </div><pre class="programlisting">
+GRUB_TERMINAL="serial"
+GRUB_SERIAL_COMMAND="serial --speed=9600 --unit=0 --word=8 --parity=no --stop=1"
+</pre><div class="para">
+ The first line disables the graphical terminal. Note that specifying the <code class="literal">GRUB_TERMINAL</code> key overrides values of <code class="literal">GRUB_TERMINAL_INPUT</code> and <code class="literal">GRUB_TERMINAL_OUTPUT</code>. On the second line, adjust the baud rate, parity, and other values to fit your environment and hardware. A much higher baud rate, for example <code class="literal">115200</code>, is preferable for tasks such as following log files. Once you have completed the changes in the <code class="filename">/etc/default/grub</code> file, it is necessary to update the GRUB 2 configuration file.
+ </div><div class="para">
+ Update the <code class="filename">grub.cfg</code> file by running the <code class="command">grub2-mkconfig <code class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div class="para">
+ On UEFI-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ In order to access the grub terminal over a serial connection an additional option must be added to a kernel definition to make that particular kernel monitor a serial connection. For example: <pre class="synopsis">console=<em class="replaceable"><code>ttyS0,9600n8</code></em></pre> Where <code class="option">console=ttyS0</code> is the serial terminal to be used, <code class="option">9600</code> is the baud rate, <code class="option">n</code> is for no parity, and <code class="option">8</code> is the word length in bits. A much higher baud rate, for example <code class="literal">115200</code>, is preferable for tasks such as following log files.
+ </div><div class="para">
+ For more information on adding kernel options, see <a class="xref" href="#sec-Editing_an_Entry">Section 20.2.2, “Editing an Entry”</a>. For more information on serial console settings, see <a href="https://www.kernel.org/doc/Documentation/serial-console.txt">https://www.kernel.org/doc/Documentation/serial-console.txt</a>
+ </div></div></div></div><div class="section" id="sec-Using_screen_to_Connect_to_the_Serial_Console"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.5.2. Using screen to Connect to the Serial Console</h3></div></div></div><div class="para">
+ The <span class="application"><strong>screen</strong></span> tool serves as a capable serial terminal. To install it, run as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">yum install screen</code></pre><div class="para">
+ To connect to your machine using the serial console, run the following command:
+ </div><pre class="screen">~]$ <code class="command">screen</code> <code class="filename">/dev/<console_port></code></pre><div class="para">
+ By default, if no option is specified, <span class="application"><strong>screen</strong></span> uses the standard 9600 baud rate. To set a different baud rate, run:
+ </div><pre class="screen">~]$ <code class="command">screen</code> <code class="filename">/dev/<console_port></code> <code class="option">115200</code></pre><div class="para">
+ To end the session in <span class="application"><strong>screen</strong></span>, press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>a</strong></span>, type <code class="literal">:quit</code> and press <span class="keycap"><strong>Enter</strong></span>.
+ </div><div class="para">
+ See the <code class="filename">screen(1)</code> manual page for additional options and detailed information.
+ </div></div></div><div class="section" id="sec-Terminal_Menu_Editing_During_Boot"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.6. Terminal Menu Editing During Boot</h2></div></div></div><div class="para">
+ Menu entries can be modified and arguments passed to the kernel on boot. This is done using the menu entry editor interface, which is triggered when pressing the <span class="keycap"><strong>e</strong></span> key on a selected menu entry in the boot loader menu. The <span class="keycap"><strong>Esc</strong></span> key discards any changes and reloads the standard menu interface. The <span class="keycap"><strong>c</strong></span> key loads the command line interface.
+ </div><div class="para">
+ The command line interface is the most basic GRUB interface, but it is also the one that grants the most control. The command line makes it possible to type any relevant GRUB commands followed by the <span class="keycap"><strong>Enter</strong></span> key to execute them. This interface features some advanced features similar to <span class="application"><strong>shell</strong></span>, including <span class="keycap"><strong>Tab</strong></span> key completion based on context, and <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>a</strong></span> to move to the beginning of a line and <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>e</strong></span> to move to the end of a line. In addition, the <span class="keycap"><strong>arrow</strong></span>, <span class="keycap"><strong>Home</strong></span>, <span class="keycap"><strong>End</strong></span>, and <span class="keycap"><strong>Delete</strong></span> keys work as t
hey do in the bash shell.
+ </div><div class="section" id="sec-Booting_to_Rescue_Mode"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.6.1. Booting to Rescue Mode</h3></div></div></div><div class="para">
+ Rescue mode provides a convenient single-user environment and allows you to repair your system in situations when it is unable to complete a normal booting process. In rescue mode, the system attempts to mount all local file systems and start some important system services, but it does not activate network interfaces or allow more users to be logged into the system at the same time. In Fedora, rescue mode is equivalent to single user mode and requires the <code class="systemitem">root</code> password.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To enter rescue mode during boot, on the GRUB 2 boot screen, press the <span class="keycap"><strong>e</strong></span> key for edit.
+ </div></li><li class="step"><div class="para">
+ Add the following parameter at the end of the <code class="literal">linux</code> line on 64-Bit IBM Power Series, the <code class="literal">linux16</code> line on x86-64 BIOS-based systems, or the <code class="literal">linuxefi</code> line on UEFI systems:
+ </div><pre class="screen">systemd.unit=rescue.target</pre><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>a</strong></span> and <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>e</strong></span> to jump to the start and end of the line, respectively. On some systems, <span class="keycap"><strong>Home</strong></span> and <span class="keycap"><strong>End</strong></span> might also work.
+ </div><div class="para">
+ Note that equivalent parameters, <em class="parameter"><code>1</code></em>, <em class="parameter"><code>s</code></em>, and <em class="parameter"><code>single</code></em>, can be passed to the kernel as well.
+ </div></li><li class="step"><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>x</strong></span> to boot the system with the parameter.
+ </div></li></ol></div></div><div class="section" id="sec-Booting_to_Emergency_Mode"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.6.2. Booting to Emergency Mode</h3></div></div></div><div class="para">
+ Emergency mode provides the most minimal environment possible and allows you to repair your system even in situations when the system is unable to enter rescue mode. In emergency mode, the system mounts the <code class="systemitem">root</code> file system only for reading, does not attempt to mount any other local file systems, does not activate network interfaces, and only starts few essential services. In Fedora, emergency mode requires the <code class="systemitem">root</code> password.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To enter emergency mode, on the GRUB 2 boot screen, press the <span class="keycap"><strong>e</strong></span> key for edit.
+ </div></li><li class="step"><div class="para">
+ Add the following parameter at the end of the <code class="literal">linux</code> line on 64-Bit IBM Power Series, the <code class="literal">linux16</code> line on x86-64 BIOS-based systems, or the <code class="literal">linuxefi</code> line on UEFI systems:
+ </div><pre class="screen">systemd.unit=emergency.target</pre><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>a</strong></span> and <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>e</strong></span> to jump to the start and end of the line, respectively. On some systems, <span class="keycap"><strong>Home</strong></span> and <span class="keycap"><strong>End</strong></span> might also work.
+ </div><div class="para">
+ Note that equivalent parameters, <em class="parameter"><code>emergency</code></em> and <em class="parameter"><code>-b</code></em>, can be passed to the kernel as well.
+ </div></li><li class="step"><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>x</strong></span> to boot the system with the parameter.
+ </div></li></ol></div></div><div class="section" id="sec-Changing_and_Resetting_the_Root_Password"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.6.3. Changing and Resetting the Root Password</h3></div></div></div><div class="para">
+ Setting up the <code class="systemitem">root</code> password is a mandatory part of the Fedora installation. If you forget or lose the <code class="systemitem">root</code> password it is possible to reset it, however users who are members of the wheel group can change the <code class="systemitem">root</code> password as follows:
+<pre class="screen">~]$ <code class="command">sudo passwd root</code></pre>
+
+ </div><div class="para">
+ Note that in GRUB 2, resetting the password is no longer performed in single-user mode as it was in GRUB included in Fedora 15 and Red Hat Enterprise Linux 6. The <code class="systemitem">root</code> password is now required to operate in <code class="literal">single-user</code> mode as well as in <code class="literal">emergency</code> mode.
+ </div><div class="para">
+ Two procedures for resetting the <code class="systemitem">root</code> password are shown here:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a class="xref" href="#proc-Resetting_the_Root_Password_Using_an_Installation_Disk">Procedure 20.1, “Resetting the Root Password Using an Installation Disk”</a> takes you to a shell prompt, without having to edit the grub menu. It is the shorter of the two procedures and it is also the recommended method. You can use a server boot disk or a netinstall installation disk.
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="#proc-Resetting_the_Root_Password_Using_rd.break">Procedure 20.2, “Resetting the Root Password Using rd.break”</a> makes use of <code class="command">rd.break</code> to interrupt the boot process before control is passed from <code class="systemitem">initramfs</code> to <code class="systemitem">systemd</code>. The disadvantage of this method is that it requires more steps, includes having to edit the GRUB menu, and involves choosing between a possibly time consuming SELinux file relabel or changing the SELinux enforcing mode and then restoring the SELinux security context for <code class="filename">/etc/shadow/</code> when the boot completes.
+ </div></li></ul></div><div class="procedure" id="proc-Resetting_the_Root_Password_Using_an_Installation_Disk"><h6>Procedure 20.1. Resetting the Root Password Using an Installation Disk</h6><ol class="1"><li class="step"><div class="para">
+ Start the system and when BIOS information is displayed, select the option for a boot menu and select to boot from the installation disk.
+ </div></li><li class="step"><div class="para">
+ Choose <span class="guimenuitem"><strong>Troubleshooting</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Choose <span class="guimenuitem"><strong>Rescue a Fedora-Server System</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Choose <span class="guimenuitem"><strong>Continue</strong></span> which is the default option. At this point you will be promoted for a passphrase if an encrypted file system is found.
+ </div></li><li class="step"><div class="para">
+ Press <span class="keycap"><strong>OK</strong></span> to acknowledge the information displayed until the shell prompt appears.
+ </div></li><li class="step"><div class="para">
+ Change the file system <code class="systemitem">root</code> as follows:
+<pre class="screen">sh-4.2# <code class="command">chroot /mnt/sysimage</code></pre>
+
+ </div></li><li class="step"><div class="para">
+ Enter the <code class="command">passwd</code> command and follow the instructions displayed on the command line to change the <code class="systemitem">root</code> password.
+ </div></li><li class="step"><div class="para">
+ Remove the <code class="filename">autorelable</code> file to prevent a time consuming SELinux relabel of the disk:
+<pre class="screen">sh-4.2# <code class="command">rm -f /.autorelabel</code></pre>
+
+ </div></li><li class="step"><div class="para">
+ Enter the <code class="command">exit</code> command to exit the <code class="command">chroot</code> environment.
+ </div></li><li class="step"><div class="para">
+ Enter the <code class="command">exit</code> command again to resume the initialization and finish the system boot.
+ </div></li></ol></div><div class="procedure" id="proc-Resetting_the_Root_Password_Using_rd.break"><h6>Procedure 20.2. Resetting the Root Password Using rd.break</h6><ol class="1"><li class="step"><div class="para">
+ Start the system and, on the GRUB 2 boot screen, press the <span class="keycap"><strong>e</strong></span> key for edit.
+ </div></li><li class="step"><div class="para">
+ Remove the <code class="option">rhgb</code> and <code class="option">quiet</code> parameters from the end, or near the end, of the <code class="literal">linux16</code> line, or <code class="literal">linuxefi</code> on UEFI systems.
+ </div><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>a</strong></span> and <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>e</strong></span> to jump to the start and end of the line, respectively. On some systems, <span class="keycap"><strong>Home</strong></span> and <span class="keycap"><strong>End</strong></span> might also work.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The <code class="option">rhgb</code> and <code class="option">quiet</code> parameters must be removed in order to enable system messages.
+ </div></div></div></li><li class="step"><div class="para">
+ Add the following parameters at the end of the <code class="literal">linux</code> line on 64-Bit IBM Power Series, the <code class="literal">linux16</code> line on x86-64 BIOS-based systems, or the <code class="literal">linuxefi</code> line on UEFI systems:
+<pre class="screen">rd.break enforcing=0</pre>
+ Adding the <code class="option">enforcing=0</code> option enables omitting the time consuming SELinux relabeling process.
+ </div><div class="para">
+ The <code class="systemitem">initramfs</code> will stop before passing control to the Linux <span class="package">kernel</span>, enabling you to work with the <code class="systemitem">root</code> file system.
+ </div><div class="para">
+ Note that the <code class="systemitem">initramfs</code> prompt will appear on the last console specified on the Linux line.
+ </div></li><li class="step"><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>x</strong></span> to boot the system with the changed parameters.
+ </div><div class="para">
+ With an encrypted file system, a password is required at this point. However the password prompt might not appear as it is obscured by logging messages. You can press the <span class="keycap"><strong>Backspace</strong></span> key to see the prompt. Release the key and enter the password for the encrypted file system, while ignoring the logging messages.
+ </div><div class="para">
+ The <code class="systemitem">initramfs</code> <code class="systemitem">switch_root</code> prompt appears.
+ </div></li><li class="step"><div class="para">
+ The file system is mounted read-only on <code class="filename">/sysroot/</code>. You will not be allowed to change the password if the file system is not writable.
+ </div><div class="para">
+ Remount the file system as writable:
+<pre class="screen">switch_root:/# <code class="command">mount -o remount,rw /sysroot</code></pre>
+
+ </div></li><li class="step"><div class="para">
+ The file system is remounted with write enabled.
+ </div><div class="para">
+ Change the file system's <code class="systemitem">root</code> as follows:
+<pre class="screen">switch_root:/# <code class="command">chroot /sysroot</code></pre>
+ The prompt changes to <code class="computeroutput">sh-4.2#</code>.
+ </div></li><li class="step"><div class="para">
+ Enter the <code class="command">passwd</code> command and follow the instructions displayed on the command line to change the <code class="systemitem">root</code> password.
+ </div><div class="para">
+ Note that if the system is not writable, the <span class="application"><strong>passwd</strong></span> tool fails with the following error:
+ </div><pre class="screen">Authentication token manipulation error</pre></li><li class="step"><div class="para">
+ Updating the password file results in a file with the incorrect SELinux security context. To relabel all files on next system boot, enter the following command:
+<pre class="screen">sh-4.2# <code class="command">touch /.autorelabel</code></pre>
+ Alternatively, to save the time it takes to relabel a large disk, you can omit this step provided you included the <code class="option">enforcing=0</code> option in step 3.
+ </div></li><li class="step"><div class="para">
+ Remount the file system as read only:
+<pre class="screen">sh-4.2# <code class="command">mount -o remount,ro /</code></pre>
+
+ </div></li><li class="step"><div class="para">
+ Enter the <code class="command">exit</code> command to exit the <code class="command">chroot</code> environment.
+ </div></li><li class="step"><div class="para">
+ Enter the <code class="command">exit</code> command again to resume the initialization and finish the system boot.
+ </div><div class="para">
+ With an encrypted file system, a pass word or phrase is required at this point. However the password prompt might not appear as it is obscured by logging messages. You can press and hold the <span class="keycap"><strong>Backspace</strong></span> key to see the prompt. Release the key and enter the password for the encrypted file system, while ignoring the logging messages.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that the SELinux relabeling process can take a long time. A system reboot will occur automatically when the process is complete.
+ </div></div></div></li><li class="step"><div class="para">
+ If you added the <code class="option">enforcing=0</code> option in step 3 and omitted the <code class="command">touch /.autorelabel</code> command in step 8, enter the following command to restore the <code class="filename">/etc/shadow</code> file's SELinux security context:
+<pre class="screen">~]# <code class="command">restorcon /etc/shadow</code></pre>
+ Enter the following commands to turn SELinux policy enforcement back on and verify that it is on:
+<pre class="screen">~]# <code class="command">setenforce 1</code>
+~]# <code class="command">getenforce</code>
+Enforcing</pre>
+
+ </div></li></ol></div></div></div><div class="section" id="sec-UEFI_Secure_Boot"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.7. UEFI Secure Boot</h2></div></div></div><div class="para">
+ The Secure Boot technology ensures that the system firmware checks whether the system boot loader is signed with a cryptographic key authorized by a database contained in the firmware. With signature verification in the next-stage boot loader, kernel, and, potentially, user space, it is possible to prevent the execution of unsigned code.
+ </div><div class="para">
+ Secure Boot is the boot path validation component of the Unified Extensible Firmware Interface (UEFI) specification. The specification defines:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ a programming interface for cryptographically protected UEFI variables in non-volatile storage,
+ </div></li><li class="listitem"><div class="para">
+ how the trusted X.509 root certificates are stored in UEFI variables,
+ </div></li><li class="listitem"><div class="para">
+ validation of UEFI applications like boot loaders and drivers,
+ </div></li><li class="listitem"><div class="para">
+ procedures to revoke known-bad certificates and application hashes.
+ </div></li></ul></div><div class="para">
+ UEFI Secure Boot does not prevent the installation or removal of second-stage boot loaders, nor require explicit user confirmation of such changes. Signatures are verified during booting, not when the boot loader is installed or updated. Therefore, UEFI Secure Boot does not stop boot path manipulations, it simplifies the detection of changes and prevents the system from executing a modified boot path once such a modification has occurred.
+ </div><div class="section" id="sec-UEFI_Secure_Boot_Support_in_Fedora"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.7.1. UEFI Secure Boot Support in Fedora</h3></div></div></div><div class="para">
+ Fedora includes support for the UEFI Secure Boot feature, which means that Fedora can be installed and run on systems where UEFI Secure Boot is enabled. On UEFI-based systems with the Secure Boot technology enabled, all drivers that are loaded must be signed with a valid certificate, otherwise the system will not accept them. All drivers provided by Red Hat are signed by the UEFI CA certificate.
+ </div><div class="para">
+ If you want to load externally built drivers — drivers that are not provided on the Fedora Linux DVD — you must make sure these drivers are signed as well.
+ </div><div class="para">
+
+ </div></div></div><div class="section" id="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.8. Additional Resources</h2></div></div></div><div class="para">
+ Please see the following resources for more information on the GRUB 2 boot loader:
+ </div><h3 id="bh-Working_with_the_GRUB_2_Boot_Loader-Installed_Documentation">Installed Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/grub2-tools-<version-number></code> — This directory contains information about using and configuring GRUB 2. <code class="literal"><version-number></code> corresponds to the version of the GRUB 2 package installed.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">info grub2</code> — The GRUB 2 info page contains a tutorial, a user reference manual, a programmer reference manual, and a FAQ document about GRUB 2 and its usage.
+ </div></li></ul></div><h3 id="bh-Working_with_the_GRUB_2_Boot_Loader-External_Documentation">External Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://docs.fedoraproject.org/install-guide"> Fedora Installation Guide</a> — The Installation Guide provides basic information on GRUB 2, for example, installation, terminology, interfaces, and commands.
+ </div></li></ul></div></div></div><div xml:lang="en-US" class="chapter" id="ch-Manually_Upgrading_the_Kernel" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 21. Manually Upgrading the Kernel</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#s1-kernel-packages">21.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="#s1-kernel-preparing">21.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="#s1-kernel-download">21.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="#s1-kernel-perform-upgrade">21.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="#sec-Verifying_the_Initial_RAM_Disk_Image">21.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="#s1-kernel-boot-loader">21.6. Verifying the Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="#s3-ker
nel-boot-loader-grub">21.6.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-iseries">21.6.2. Configuring the OS/400 Boot Loader</a></span></dt><dt><span class="section"><a href="#s2-kernel-boot-loader-pseries">21.6.3. Configuring the YABOOT Boot Loader</a></span></dt></dl></dd></dl></div><a id="idm261685518208" class="indexterm"></a><a id="idm261735895072" class="indexterm"></a><a id="idm261760095792" class="indexterm"></a><a id="idm261758623632" 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="idm225465042800" class="indexterm"></a><a id="idm225504201360" 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">
+ </div><a id="idm261718055024" class="indexterm"></a><a id="idm261753840512" 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="idm225435439920" class="indexterm"></a><div class="para">
+ </div></div></div><a id="idm261756243856" class="indexterm"></a><div class="para">
For more information on installing kernel packages with <span class="application"><strong>Yum</strong></span>, see <a class="xref" href="#sec-Updating_Packages">Section 5.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">20.1. Overview of Kernel Packages</h2></div></div></div><a id="idm225457845328" class="indexterm"></a><a id="idm225457843888" class="indexterm"></a><a id="idm225433711600" class="indexterm"></a><a id="idm225433709712" class="indexterm"></a><a id="idm225445408336" class="indexterm"></a><a id="idm225445406448" class="indexterm"></a><a id="idm225444009392" class="indexterm"></a><a id="idm225444007472" class="indexterm"></a><a id="idm225479740528" class="indexterm"></a><a id="idm225479738608" class="indexterm"></a><a id="idm225426381200" class="indexterm"></a><a id="idm225426379280" class="indexterm"></a><a id="idm225408429200" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s1-kernel-packages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.1. Overview of Kernel Packages</h2></div></div></div><a id="idm261729637280" class="indexterm"></a><a id="idm261729635840" class="indexterm"></a><a id="idm261738799712" class="indexterm"></a><a id="idm261738797824" class="indexterm"></a><a id="idm261747273824" class="indexterm"></a><a id="idm261754582224" class="indexterm"></a><a id="idm261754580304" class="indexterm"></a><a id="idm261745267264" class="indexterm"></a><a id="idm261745265344" class="indexterm"></a><a id="idm261754139488" class="indexterm"></a><a id="idm261754137568" 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.
@@ -9921,16 +11479,16 @@ samples % symbol name
</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>/Documentation/</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">20.2. Preparing to Upgrade</h2></div></div></div><a id="idm225499636176" class="indexterm"></a><a id="idm225499635216" class="indexterm"></a><a id="idm225444151728" class="indexterm"></a><a id="idm225444150288" class="indexterm"></a><div class="para">
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-abi-whitelists</span> — Contains information pertaining to the Fedora kernel ABI, including a lists of kernel symbols that are needed by external Linux kernel modules and a <span class="package">yum</span> plug-in to aid enforcement.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-tools</span> — Contains tools for manipulating the Linux kernel and supporting documentation.
+ </div></li></ul></div></div><div class="section" id="s1-kernel-preparing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.2. Preparing to Upgrade</h2></div></div></div><a id="idm261727692624" class="indexterm"></a><a id="idm261727691664" class="indexterm"></a><a id="idm261727689744" class="indexterm"></a><a id="idm261760072000" class="indexterm"></a><div class="para">
Before upgrading the kernel, it is recommended that you take some precautionary steps.
</div><div class="para">
First, ensure that working boot media exists for the system in case a problem occurs. If the boot loader is not configured properly to boot the new kernel, you can use this media to boot into Fedora.
@@ -9965,69 +11523,71 @@ samples % symbol name
</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 might differ:
</div><pre class="screen">~]# <code class="command">yum list installed "kernel-*"</code>
-Loaded plugins: langpacks, refresh-packagekit
+Loaded plugins: langpacks
Installed Packages
-kernel.x86_64 3.16.7-200.fc20 @updates
-kernel.x86_64 3.17.2-200.fc20 @updates
-kernel.x86_64 3.17.3-200.fc20 @updates
-kernel-doc.noarch 3.17.3-200.fc20 @updates
-kernel-modules-extra.x86_64 3.16.7-200.fc20 @updates
-kernel-modules-extra.x86_64 3.17.2-200.fc20 @updates
-kernel-modules-extra.x86_64 3.17.3-200.fc20 @updates</pre><div class="para">
- From the output, determine which packages need to be downloaded for the kernel upgrade. For a single processor system, the only required package is the <span class="package">kernel</span> package. See <a class="xref" href="#s1-kernel-packages">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">20.3. Downloading the Upgraded Kernel</h2></div></div></div><a id="idm225444016240" class="indexterm"></a><a id="idm225481094496" class="indexterm"></a><a id="idm225481093088" class="indexterm"></a><a id="idm225481091232" class="indexterm"></a><div class="para">
+kernel.x86_64 3.17.4-302.fc21 @updates
+kernel.x86_64 3.17.6-300.fc21 @updates
+kernel.x86_64 3.17.7-300.fc21 @updates
+kernel-core.x86_64 3.17.4-302.fc21 @updates
+kernel-core.x86_64 3.17.6-300.fc21 @updates
+kernel-core.x86_64 3.17.7-300.fc21 @updates
+kernel-modules.x86_64 3.17.4-302.fc21 @updates
+kernel-modules.x86_64 3.17.6-300.fc21 @updates
+kernel-modules.x86_64 3.17.7-300.fc21 @updates</pre><div class="para">
+ From the output, determine which packages need to be downloaded for the kernel upgrade. For a single processor system, the only required package is the <span class="package">kernel</span> package. See <a class="xref" href="#s1-kernel-packages">Section 21.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">21.3. Downloading the Upgraded Kernel</h2></div></div></div><a id="idm261725535184" class="indexterm"></a><a id="idm261720546720" class="indexterm"></a><a id="idm261720545312" class="indexterm"></a><a id="idm261754738496" 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 — See <a href="http://fedoraproject.org/wiki/FSA">http://fedoraproject.org/wiki/FSA</a> for information on Security Advisories, including kernel upgrades that fix security issues.
</div></li><li class="listitem"><div class="para">
Via Fedora Update System — Download and install the kernel RPM packages. For more information, refer to <a href="http://admin.fedoraproject.org/updates/">http://admin.fedoraproject.org/updates/</a>.
</div></li></ul></div><div class="para">
- To install the kernel manually, continue to <a class="xref" href="#s1-kernel-perform-upgrade">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">20.4. Performing the Upgrade</h2></div></div></div><a id="idm225479879456" class="indexterm"></a><div class="para">
+ To install the kernel manually, continue to <a class="xref" href="#s1-kernel-perform-upgrade">Section 21.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">21.4. Performing the Upgrade</h2></div></div></div><a id="idm261726515568" class="indexterm"></a><div class="para">
After retrieving all of the necessary packages, it is time to upgrade the existing kernel.
</div><div class="important"><div class="admonition_header"><h2>Keep the old kernel when performing the upgrade</h2></div><div class="admonition"><div class="para">
It is strongly recommended that you keep the old kernel in case there are problems with the new kernel.
</div></div></div><div class="para">
At a shell prompt, change to the directory that contains the kernel RPM packages. Use <code class="option">-i</code> argument with the <code class="command">rpm</code> command to keep the old kernel. Do <span class="emphasis"><em>not</em></span> use the <code class="option">-U</code> option, since it overwrites the currently installed kernel, which creates boot loader problems. For example:
</div><pre class="screen">~]# <code class="command">rpm -ivh kernel-<em class="replaceable"><code>kernel_version</code></em>.<em class="replaceable"><code>arch</code></em>.rpm </code></pre><div class="para">
- The next step is to verify that the initial RAM disk image has been created. See <a class="xref" href="#sec-Verifying_the_Initial_RAM_Disk_Image">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">20.5. Verifying the Initial RAM Disk Image</h2></div></div></div><a id="idm225474337696" class="indexterm"></a><div class="para">
+ The next step is to verify that the initial RAM disk image has been created. See <a class="xref" href="#sec-Verifying_the_Initial_RAM_Disk_Image">Section 21.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">21.5. Verifying the Initial RAM Disk Image</h2></div></div></div><a id="idm261714447456" 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 21 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">the section called “ Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i ”</a>), you can create an <code class="systemitem">initramfs</code> by running the <code class="command">dracut</code> command. However, you usually don't need to create an <code class="systemitem">initramfs</code> manually: this step is automatically performed if the kernel and its associated packages are installed or upgraded from RPM packages distributed by The Fedora Project.
</div><div class="para">
On architectures that use the GRUB 2 boot loader, you can verify that an <code class="systemitem">initramfs</code> corresponding to your current kernel version exists and is specified correctly in the <code class="filename">/boot/grub2/grub.cfg</code> configuration file by following this procedure:
- </div><div class="procedure" id="procedure-Verifying_the_Initial_RAM_Disk_Image"><h6>Procedure 20.1. Verifying the Initial RAM Disk Image</h6><ol class="1"><li class="step"><div class="para">
+ </div><div class="procedure" id="procedure-Verifying_the_Initial_RAM_Disk_Image"><h6>Procedure 21.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><div class="example" id="ex-Ensuring_that_the_kernel_and_initramfs_versions_match"><h6>Example 20.1. Ensuring that the kernel and initramfs versions match</h6><div class="example-contents"><pre class="screen">~]# <code class="command">ls /boot/</code>
-config-3.16.7-200.fc20.x86_64
-config-3.17.2-200.fc20.x86_64
-config-3.17.3-200.fc20.x86_64
+ </div><div class="example" id="ex-Ensuring_that_the_kernel_and_initramfs_versions_match"><h6>Example 21.1. Ensuring that the kernel and initramfs versions match</h6><div class="example-contents"><pre class="screen">~]# <code class="command">ls /boot/</code>
+config-3.17.4-302.fc21.x86_64
+config-3.17.6-300.fc21.x86_64
+config-3.17.7-300.fc21.x86_64
efi
elf-memtest86+-5.01
extlinux
grub2
-initramfs-0-rescue-d54d78fd40ab445a9556279010454c22.img
-initramfs-3.16.7-200.fc20.x86_64.img
-initramfs-3.17.2-200.fc20.x86_64.img
-initramfs-3.17.3-200.fc20.x86_64.img
+initramfs-0-rescue-db90b4e3715b42daa871351439343ca4.img
+initramfs-3.17.4-302.fc21.x86_64.img
+initramfs-3.17.6-300.fc21.x86_64.img
+initramfs-3.17.7-300.fc21.x86_64.img
initrd-plymouth.img
lost+found
memtest86+-5.01
-System.map-3.16.7-200.fc20.x86_64
-System.map-3.17.2-200.fc20.x86_64
-System.map-3.17.3-200.fc20.x86_64
-vmlinuz-0-rescue-d54d78fd40ab445a9556279010454c22
-vmlinuz-3.16.7-200.fc20.x86_64
-vmlinuz-3.17.2-200.fc20.x86_64
-vmlinuz-3.17.3-200.fc20.x86_64</pre></div></div><br class="example-break" /><div class="para">
- <a class="xref" href="#ex-Ensuring_that_the_kernel_and_initramfs_versions_match">Example 20.1, “Ensuring that the kernel and initramfs versions match”</a> shows that:
+System.map-3.17.4-302.fc21.x86_64
+System.map-3.17.6-300.fc21.x86_64
+System.map-3.17.7-300.fc21.x86_64
+vmlinuz-0-rescue-db90b4e3715b42daa871351439343ca4
+vmlinuz-3.17.4-302.fc21.x86_64
+vmlinuz-3.17.6-300.fc21.x86_64
+vmlinuz-3.17.7-300.fc21.x86_64</pre></div></div><br class="example-break" /><div class="para">
+ <a class="xref" href="#ex-Ensuring_that_the_kernel_and_initramfs_versions_match">Example 21.1, “Ensuring that the kernel and initramfs versions match”</a> shows that:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
we have three kernels installed (or, more correctly, three kernel files are present in the <code class="filename">/boot/</code> directory),
</div></li><li class="listitem"><div class="para">
- the latest kernel is <code class="filename">vmlinuz-3.17.3-200.fc20.x86_64</code>, and
+ the latest kernel is <code class="filename">vmlinuz-3.17.7-300.fc21.x86_64</code>, and
</div></li><li class="listitem"><div class="para">
- an <code class="systemitem">initramfs</code> file matching our kernel version, <code class="filename">initramfs-3.17.3-200.fc20.x86_64.img</code>, also exists.
+ an <code class="systemitem">initramfs</code> file matching our kernel version, <code class="filename">initramfs-3.17.7-300.fc21.x86_64.img</code>, also exists.
</div></li></ul></div><div class="important" id="important-initrd_files_in_the__boot_directory_are_not_the_same_as_initramfs_files"><div class="admonition_header"><h2>initrd files in the /boot/ directory are not the same as initramfs files</h2></div><div class="admonition"><div class="para">
In the <code class="filename">/boot/</code> directory you might find several <code class="filename">initrd-<em class="replaceable"><code>kernel_version</code></em>kdump.img</code> files. These are special files created by the <code class="systemitem">kdump</code> mechanism for kernel debugging purposes, are not used to boot the system, and can safely be ignored. For more information on <code class="systemitem">kdump</code>, see the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Kernel_Crash_Dump_Guide/">Red Hat Enterprise Linux 7 Kernel Crash Dump Guide</a>.
</div></div></div></li><li class="step"><div class="para">
@@ -10035,35 +11595,35 @@ vmlinuz-3.17.3-200.fc20.x86_64</pre></div></div><br class="example-break" /><div
</div><pre class="screen">~]# <code class="command">dracut</code></pre><div class="para">
You must use the <code class="option">--force</code> option if you want <code class="command">dracut</code> to overwrite an existing <code class="filename">initramfs</code> (for example, if your <code class="filename">initramfs</code> has become corrupt). Otherwise <code class="command">dracut</code> will refuse to overwrite the existing <code class="filename">initramfs</code> file:
</div><pre class="screen">~]# <code class="command">dracut</code>
-F: Will not override existing initramfs (/boot/initramfs-3.17.3-200.fc20.x86_64.img) without --force</pre><div class="para">
+F: Will not override existing initramfs (/boot/initramfs-3.17.7-300.fc21.x86_64.img) without --force</pre><div class="para">
You can create an initramfs in the current directory by calling <code class="command">dracut <em class="replaceable"><code>initramfs_name</code></em> <em class="replaceable"><code>kernel_version</code></em></code>, for example:
</div><pre class="screen">~]# <code class="command">dracut "initramfs-$(uname -r).img" $(uname -r)</code></pre><div class="para">
If you need to specify specific kernel modules to be preloaded, add the names of those modules (minus any file name suffixes such as <code class="filename">.ko</code>) inside the parentheses of the <code class="computeroutput">add_dracutmodules="<em class="replaceable"><code>module</code></em> [<span class="optional"><em class="replaceable"><code>more_modules</code></em></span>]"</code> directive of the <code class="filename">/etc/dracut.conf</code> configuration file. You can list the file contents of an <code class="filename">initramfs</code> image file created by dracut by using the <code class="command">lsinitrd <em class="replaceable"><code>initramfs_file</code></em></code> command:
- </div><pre class="screen">~]# <code class="command">lsinitrd /boot/initramfs-3.17.3-200.fc20.x86_64.img</code>
-Image: /boot/initramfs-3.17.3-200.fc20.x86_64.img: 18M
+ </div><pre class="screen">~]# <code class="command">lsinitrd /boot/initramfs-3.17.7-300.fc21.x86_64.img</code>
+Image: /boot/initramfs-3.17.7-300.fc21.x86_64.img: 18M
========================================================================
-Version: dracut-037-11.git20140402.fc20
+Version: dracut-038-31.git20141204.fc21
<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em></pre><div class="para">
See <code class="command">man dracut</code> and <code class="command">man dracut.conf</code> for more information on options and usage.
</div></li><li class="step"><div class="para">
Examine the <code class="filename">/boot/grub2/grub.cfg</code> configuration file to ensure that an <code class="computeroutput"><code class="filename">initramfs-<em class="replaceable"><code>kernel_version</code></em>.img</code></code> file exists for the kernel version you are booting. For example:
</div><pre class="screen">~]# <code class="command">grep initramfs /boot/grub2/grub.cfg</code>
- initrd /initramfs-3.17.3-200.fc20.x86_64.img
- initrd /initramfs-3.17.2-200.fc20.x86_64.img
- initrd /initramfs-3.16.7-200.fc20.x86_64.img
- initrd /initramfs-0-rescue-d54d78fd40ab445a9556279010454c22.img</pre><div class="para">
- See <a class="xref" href="#s1-kernel-boot-loader">Section 20.6, “Verifying the Boot Loader”</a> for more information on how to read and update the <code class="filename">/boot/grub2/grub.cfg</code> file.
- </div></li></ol></div><h3 id="bh-Verifying_the_Initial_RAM_Disk_Image_and_Kernel_on_IBM_eServer_System_i"> Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i </h3><a id="idm225370983168" class="indexterm"></a><div class="para">
+ initrd16 /initramfs-3.17.7-300.fc21.x86_64.img
+ initrd16 /initramfs-3.17.6-300.fc21.x86_64.img
+ initrd16 /initramfs-3.17.4-302.fc21.x86_64.img
+ initrd16 /initramfs-0-rescue-db90b4e3715b42daa871351439343ca4.img</pre><div class="para">
+ See <a class="xref" href="#s1-kernel-boot-loader">Section 21.6, “Verifying the Boot Loader”</a> for more information on how to read and update the <code class="filename">/boot/grub2/grub.cfg</code> file.
+ </div></li></ol></div><h3 id="bh-Verifying_the_Initial_RAM_Disk_Image_and_Kernel_on_IBM_eServer_System_i"> Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i </h3><a id="idm261728090112" class="indexterm"></a><div class="para">
On IBM eServer System i machines, the initial RAM disk and kernel files are combined into a single file, which is created with the <code class="command">addRamDisk</code> command. This step is performed automatically if the kernel and its associated packages are installed or upgraded from the RPM packages distributed by The Fedora Project; thus, it does not need to be executed manually. To verify that it was created, run the following command as <code class="systemitem">root</code> to make sure the <code class="filename">/boot/vmlinitrd-<em class="replaceable"><code>kernel_version</code></em></code> file already exists:
- </div><pre class="screen"><code class="command">ls -l /boot</code></pre><div class="para">
+ </div><pre class="screen"><code class="command">ls -l /boot/</code></pre><div class="para">
The <em class="replaceable"><code>kernel_version</code></em> should match the version of the kernel just installed.
- </div></div><div class="section" id="s1-kernel-boot-loader"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.6. Verifying the Boot Loader</h2></div></div></div><a id="idm225445142560" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s1-kernel-boot-loader"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.6. Verifying the Boot Loader</h2></div></div></div><a id="idm261750787616" class="indexterm"></a><div class="para">
When you install a kernel using <code class="command">rpm</code>, the kernel package creates an entry in the boot loader configuration file for that new kernel. However, <code class="command">rpm</code> does <span class="emphasis"><em>not</em></span> configure the new kernel to boot as the default kernel. You must do this manually when installing a new kernel with <code class="command">rpm</code>.
</div><div class="para">
It is always recommended to double-check the boot loader configuration file after installing a new kernel with <code class="command">rpm</code> to ensure that the configuration is correct. Otherwise, the system might not be able to boot into Fedora properly. If this happens, boot the system with the boot media created earlier and re-configure the boot loader.
</div><div class="para">
In the following table, find your system's architecture to determine the boot loader it uses, and then click on the "See" link to jump to the correct instructions for your system.
- </div><div class="table" id="tb-grub-arch-loaders"><h6>Table 20.1. Boot loaders by architecture</h6><div class="table-contents"><table summary="Boot loaders by architecture" border="1"><colgroup><col width="25%" class="architecture" /><col width="25%" class="bootloader" /><col width="50%" class="refer-to" /></colgroup><thead><tr><th class="">
+ </div><div class="table" id="tb-grub-arch-loaders"><h6>Table 21.1. Boot loaders by architecture</h6><div class="table-contents"><table summary="Boot loaders by architecture" border="1"><colgroup><col width="25%" class="architecture" /><col width="25%" class="bootloader" /><col width="50%" class="refer-to" /></colgroup><thead><tr><th class="">
Architecture
</th><th class="">
Boot Loader
@@ -10074,36 +11634,36 @@ Version: dracut-037-11.git20140402.fc20
</td><td class="">
GRUB 2
</td><td class="">
- <a class="xref" href="#s3-kernel-boot-loader-grub">Section 20.6.1, “Configuring the GRUB 2 Boot Loader”</a>
+ <a class="xref" href="#s3-kernel-boot-loader-grub">Section 21.6.1, “Configuring the GRUB 2 Boot Loader”</a>
</td></tr><tr><td class="">
AMD AMD64 <span class="emphasis"><em>or</em></span> Intel 64
</td><td class="">
GRUB 2
</td><td class="">
- <a class="xref" href="#s3-kernel-boot-loader-grub">Section 20.6.1, “Configuring the GRUB 2 Boot Loader”</a>
+ <a class="xref" href="#s3-kernel-boot-loader-grub">Section 21.6.1, “Configuring the GRUB 2 Boot Loader”</a>
</td></tr><tr><td class="">
IBM eServer System i
</td><td class="">
OS/400
</td><td class="">
- <a class="xref" href="#s2-kernel-boot-loader-iseries">Section 20.6.2, “Configuring the OS/400 Boot Loader”</a>
+ <a class="xref" href="#s2-kernel-boot-loader-iseries">Section 21.6.2, “Configuring the OS/400 Boot Loader”</a>
</td></tr><tr><td class="">
IBM eServer System p
</td><td class="">
YABOOT
</td><td class="">
- <a class="xref" href="#s2-kernel-boot-loader-pseries">Section 20.6.3, “Configuring the YABOOT Boot Loader”</a>
+ <a class="xref" href="#s2-kernel-boot-loader-pseries">Section 21.6.3, “Configuring the YABOOT Boot Loader”</a>
</td></tr><tr><td class="">
IBM System z
</td><td class="">
z/IPL
</td><td class="">
—
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="s3-kernel-boot-loader-grub"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.6.1. Configuring the GRUB 2 Boot Loader</h3></div></div></div><a id="idm225424952256" class="indexterm"></a><a id="idm225424950816" class="indexterm"></a><div class="para">
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="s3-kernel-boot-loader-grub"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">21.6.1. Configuring the GRUB 2 Boot Loader</h3></div></div></div><a id="idm261741227568" class="indexterm"></a><a id="idm261724804288" class="indexterm"></a><div class="para">
Fedora 21 is distributed with GRUB 2, which reads its configuration from the <code class="filename">/boot/grub2/grub.cfg</code> file. This file is generated by the <span class="application"><strong>grub2-mkconfig</strong></span> utility based on Linux kernels located in the <code class="filename">/boot</code> directory, template files located in <code class="filename">/etc/grub.d/</code>, and custom settings in the <code class="filename">/etc/default/grub</code> file and is automatically updated each time you install a new kernel from an RPM package. To update this configuration file manually, type the following at a shell prompt as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">grub2-mkconfig</code> <code class="option">-o</code> <code class="option">/boot/grub2/grub.cfg</code></pre><div class="para">
- Among various code snippets and directives, the <code class="filename">/boot/grub2/grub.cfg</code> configuration file contains one or more <code class="literal">menuentry</code> blocks, each representing a single GRUB 2 boot menu entry. These blocks always start with the <code class="literal">menuentry</code> keyword followed by a title, list of options, and opening curly bracket, and end with a closing curly bracket. Anything between the opening and closing bracket should be indented. For example, the following is a sample <code class="literal">menuentry</code> block for Fedora 17 with Linux kernel 3.4.0-1.fc17.x86_64:
- </div><pre class="programlisting">menuentry 'Fedora (3.4.0-1.fc17.x86_64)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-77ba9149-751a-48e0-974f-ad94911734b9' {
+ Among various code snippets and directives, the <code class="filename">/boot/grub2/grub.cfg</code> configuration file contains one or more <code class="literal">menuentry</code> blocks, each representing a single GRUB 2 boot menu entry. These blocks always start with the <code class="literal">menuentry</code> keyword followed by a title, list of options, and opening curly bracket, and end with a closing curly bracket. Anything between the opening and closing bracket should be indented. For example, the following is a sample <code class="literal">menuentry</code> block for Fedora 21 with Linux kernel 3.17.6-300.fc21.x86_64:
+ </div><pre class="programlisting">menuentry 'Fedora (3.17.6-300.fc21.x86_64) 21 (Twenty One)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.17.4-301.fc21.x86_64-advanced-effee860-8d55-4e4a-995e-b4c88f9ac9f0' {
load_video
set gfxpayload=keep
insmod gzio
@@ -10111,27 +11671,25 @@ Version: dracut-037-11.git20140402.fc20
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
- search --no-floppy --fs-uuid --set=root --hint='hd0,msdos1' 4ea24c68-ab10-47d4-8a6b-b8d3a002acba
+ search --no-floppy --fs-uuid --set=root --hint='hd0,msdos1' f19c92f4-9ead-4207-b46a-723b7a2c51c8
else
- search --no-floppy --fs-uuid --set=root 4ea24c68-ab10-47d4-8a6b-b8d3a002acba
+ search --no-floppy --fs-uuid --set=root f19c92f4-9ead-4207-b46a-723b7a2c51c8
fi
- echo 'Loading Fedora (3.4.0-1.fc17.x86_64)'
- linux /vmlinuz-3.4.0-1.fc17.x86_64 root=/dev/mapper/vg_fedora-lv_root ro rd.md=0 rd.dm=0 SYSFONT=True rd.lvm.lv=vg_fedora/lv_swap KEYTABLE=us rd.lvm.lv=vg_fedora/lv_root rd.luks=0 LANG=en_US.UTF-8 rhgb quiet
- echo 'Loading initial ramdisk ...'
- initrd /initramfs-3.4.0-1.fc17.x86_64.img
+ linux16 /vmlinuz-3.17.6-300.fc21.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
+ initrd16 /initramfs-3.17.6-300.fc21.x86_64.img
}</pre><div class="para">
- Each <code class="literal">menuentry</code> block that represents an installed Linux kernel contains <code class="literal">linux</code> and <code class="literal">initrd</code> directives followed by the path to the kernel and the <code class="systemitem">initramfs</code> image respectively. If a separate <code class="filename">/boot</code> partition was created, the paths to the kernel and the <code class="systemitem">initramfs</code> image are relative to <code class="filename">/boot</code>. In the example above, the <code class="literal">initrd /initramfs-3.4.0-1.fc17.x86_64.img</code> line means that the <code class="systemitem">initramfs</code> image is actually located at <code class="filename">/boot/initramfs-3.4.0-1.fc17.x86_64.img</code> when the root file system is mounted, and likewise for the kernel path.
+ Each <code class="literal">menuentry</code> block that represents an installed Linux kernel contains <code class="literal">linux</code> and <code class="literal">initrd</code> directives followed by the path to the kernel and the <code class="systemitem">initramfs</code> image respectively. If a separate <code class="filename">/boot</code> partition was created, the paths to the kernel and the <code class="systemitem">initramfs</code> image are relative to <code class="filename">/boot</code>. In the example above, the <code class="literal">initrd16 /initramfs-3.17.6-300.fc21.x86_64.img</code> line means that the <code class="systemitem">initramfs</code> image is actually located at <code class="filename">/boot/initramfs-3.17.6-300.fc21.x86_64.img</code> when the root file system is mounted, and likewise for the kernel path.
</div><div class="para">
- The kernel version number as given on the <code class="literal">linux /vmlinuz-<em class="replaceable"><code>kernel_version</code></em></code> line must match the version number of the <code class="systemitem">initramfs</code> image given on the <code class="literal">initrd /initramfs-<em class="replaceable"><code>kernel_version</code></em>.img</code> line of each <code class="literal">menuentry</code> block. For more information on how to verify the initial RAM disk image, refer to <a class="xref" href="#procedure-Verifying_the_Initial_RAM_Disk_Image">Procedure 20.1, “Verifying the Initial RAM Disk Image”</a>.
+ The kernel version number as given on the <code class="literal">linux /vmlinuz-<em class="replaceable"><code>kernel_version</code></em></code> line must match the version number of the <code class="systemitem">initramfs</code> image given on the <code class="literal">initrd /initramfs-<em class="replaceable"><code>kernel_version</code></em>.img</code> line of each <code class="literal">menuentry</code> block. For more information on how to verify the initial RAM disk image, refer to <a class="xref" href="#procedure-Verifying_the_Initial_RAM_Disk_Image">Procedure 21.1, “Verifying the Initial RAM Disk Image”</a>.
</div><div class="note" id="note-The_initrd_directive_in_grub.cfg_refers_to_an_initramfs_image"><div class="admonition_header"><h2>The initrd directive in grub.cfg refers to an initramfs image</h2></div><div class="admonition"><div class="para">
In <code class="literal">menuentry</code> blocks, the <code class="computeroutput">initrd</code> directive must point to the location (relative to the <code class="filename">/boot</code> directory if it is on a separate partition) of the <code class="filename">initramfs</code> file corresponding to the same kernel version. This directive is called <code class="literal">initrd</code> because the previous tool which created initial RAM disk images, <code class="command">mkinitrd</code>, created what were known as <code class="systemitem">initrd</code> files. The <code class="filename">grub.cfg</code> directive remains <code class="systemitem">initrd</code> to maintain compatibility with other tools. The file-naming convention of systems using the <code class="command">dracut</code> utility to create the initial RAM disk image is <code class="filename">initramfs-<em class="replaceable"><code>kernel_version</code></em>.img</code>.
</div><div class="para">
- For information on using <span class="application"><strong>Dracut</strong></span>, refer to <a class="xref" href="#sec-Verifying_the_Initial_RAM_Disk_Image">Section 20.5, “Verifying the Initial RAM Disk Image”</a>.
+ 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 21.5, “Verifying the Initial RAM Disk Image”</a>.
</div></div></div><div class="para">
After installing a new kernel with <code class="command">rpm</code>, verify that <code class="filename">/boot/grub2/grub.cfg</code> is correct and reboot the computer into the new kernel. Ensure your hardware is detected by watching the boot process output. If GRUB 2 presents an error and is unable to boot into the new kernel, it is often easiest to try to boot into an alternative or older kernel so that you can fix the problem. Alternatively, use the boot media you created earlier to boot the system.
</div><div class="important"><div class="admonition_header"><h2>Causing the GRUB 2 boot menu to display</h2></div><div class="admonition"><div class="para">
If you set the <code class="option">GRUB_TIMEOUT</code> option in the <code class="filename">/etc/default/grub</code> file to <code class="constant">0</code>, GRUB 2 will not display its list of bootable kernels when the system starts up. In order to display this list when booting, press and hold any alphanumeric key while and immediately after BIOS information is displayed, and GRUB 2 will present you with the GRUB menu.
- </div></div></div></div><div class="section" id="s2-kernel-boot-loader-iseries"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.6.2. Configuring the OS/400 Boot Loader</h3></div></div></div><a id="idm225479656272" class="indexterm"></a><a id="idm225454469280" class="indexterm"></a><div class="para">
+ </div></div></div></div><div class="section" id="s2-kernel-boot-loader-iseries"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">21.6.2. Configuring the OS/400 Boot Loader</h3></div></div></div><a id="idm261745023648" class="indexterm"></a><a id="idm261745022208" 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).
@@ -10139,7 +11697,7 @@ Version: dracut-037-11.git20140402.fc20
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">20.6.3. Configuring the YABOOT Boot Loader</h3></div></div></div><div class="para">
+ </div></div><div class="section" id="s2-kernel-boot-loader-pseries"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">21.6.3. Configuring the YABOOT Boot Loader</h3></div></div></div><div class="para">
IBM eServer System p uses YABOOT as its boot loader. YABOOT uses <code class="filename">/etc/aboot.conf</code> as its configuration file. Confirm that the file contains an <code class="computeroutput">image</code> section with the same version as the <span class="package">kernel</span> package just installed, and likewise for the <code class="systemitem">initramfs</code> image:
</div><pre class="screen">boot=/dev/sda1 init-message=Welcome to Fedora! Hit <TAB> for boot options
partition=2 timeout=30 install=/usr/lib/yaboot/yaboot delay=10 nonvram
@@ -10156,7 +11714,7 @@ image=/vmlinuz-2.6.32-19.EL
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 class="toc"><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="#s
1-kernel-modules-additional-resources">21.7. Additional Resources</a></span></dt></dl></div><a id="idm225464253616" class="indexterm"></a><a id="idm225408393584" class="indexterm"></a><a id="idm225463768896" class="indexterm"></a><div class="para">
+ </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 22. Working with Kernel Modules</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="#sec-Displaying_Information_About_a_Module">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="#sec-Loading_a_Module">22.3. Loading a Module</a></span></dt><dt><span class="section"><a href="#sec-Unloading_a_Module">22.4. Unloading a Module</a></span></dt><dt><span class="section"><a href="#sec-Setting_Module_Parameters">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="#sec-Persistent_Module_Loading">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="#s
ect-signing-kernel-modules-for-secure-boot">22.7. Signing Kernel Modules for Secure Boot</a></span></dt><dd><dl><dt><span class="section"><a href="#sect-prerequisites">22.7.1. Prerequisites</a></span></dt><dt><span class="section"><a href="#sect-kernel-module-authentication">22.7.2. Kernel Module Authentication</a></span></dt><dt><span class="section"><a href="#sect-generating-a-public-private-x509-key-pair">22.7.3. Generating a Public and Private X.509 Key Pair</a></span></dt><dt><span class="section"><a href="#sect-enrolling-public-key-on-target-system">22.7.4. Enrolling Public Key on Target System</a></span></dt><dt><span class="section"><a href="#sect-signing-kernel-module-with-the-private-key">22.7.5. Signing Kernel Module with the Private Key</a></span></dt><dt><span class="section"><a href="#sect-loading-signed-kernel-module">22.7.6. Loading Signed Kernel Module</a></span></dt></dl></dd><dt><span class="section"><a href="#s1-kernel-modules-additional-resources">22.8.
Additional Resources</a></span></dt></dl></div><a id="idm261651018576" class="indexterm"></a><a id="idm261719755520" class="indexterm"></a><a id="idm261761408208" 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,
@@ -10179,7 +11737,7 @@ image=/vmlinuz-2.6.32-19.EL
</div><pre class="screen">~]# <code class="command">yum install kmod</code>
</pre><div class="para">
For more information on installing packages with Yum, see <a class="xref" href="#sec-Installing">Section 5.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">21.1. Listing Currently-Loaded Modules</h2></div></div></div><a id="idm225474255632" class="indexterm"></a><a id="idm225474253744" class="indexterm"></a><a id="idm225463390784" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="sec-Listing_Currently-Loaded_Modules"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">22.1. Listing Currently-Loaded Modules</h2></div></div></div><a id="idm261749637968" class="indexterm"></a><a id="idm261749636080" class="indexterm"></a><a id="idm261693432928" 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>
@@ -10221,31 +11779,31 @@ nf_nat 21798 4 nf_nat_ipv4,nf_nat_ipv6,ip6table_nat,iptable_nat
</div></li><li class="listitem"><div class="para">
the amount of memory it uses; and,
</div></li><li class="listitem"><div class="para">
- the sum total of processes that are using the module and other modules which depend on it, followed by a list of the names of those modules, if there are any. Using this list, you can first unload all the modules depending the module you want to unload. For more information, see <a class="xref" href="#sec-Unloading_a_Module">Section 21.4, “Unloading a Module”</a>.
- </div></li></ul></div><a id="idm225480405344" class="indexterm"></a><div class="para">
+ the sum total of processes that are using the module and other modules which depend on it, followed by a list of the names of those modules, if there are any. Using this list, you can first unload all the modules depending the module you want to unload. For more information, see <a class="xref" href="#sec-Unloading_a_Module">Section 22.4, “Unloading a Module”</a>.
+ </div></li></ul></div><a id="idm261721010256" 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">21.2. Displaying Information About a Module</h2></div></div></div><a id="idm225444809648" class="indexterm"></a><a id="idm225435355248" class="indexterm"></a><a id="idm225435353168" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="sec-Displaying_Information_About_a_Module"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">22.2. Displaying Information About a Module</h2></div></div></div><a id="idm261721005680" class="indexterm"></a><a id="idm261651042320" class="indexterm"></a><a id="idm261651040240" class="indexterm"></a><div class="para">
You can display detailed information about a kernel module by running the <code class="command">modinfo <em class="replaceable"><code>module_name</code></em></code> command.
</div><div class="note" id="note-Module_names_do_not_end_in_.ko"><div class="admonition_header"><h2>Module names do not end in .ko</h2></div><div class="admonition"><div class="para">
When entering the name of a kernel module as an argument to one of the <span class="application"><strong>kmod</strong></span> utilities, do not append a <code class="filename">.ko</code> extension to the end of the name. Kernel module names do not have extensions; their corresponding files do.
- </div></div></div><div class="example" id="ex-Listing_information_about_a_kernel_module_with_lsmod"><h6>Example 21.1. Listing information about a kernel module with lsmod</h6><div class="example-contents"><div class="para">
+ </div></div></div><div class="example" id="ex-Listing_information_about_a_kernel_module_with_lsmod"><h6>Example 22.1. Listing information about a kernel module with lsmod</h6><div class="example-contents"><div class="para">
To display information about the <code class="systemitem">e1000e</code> module, which is the Intel PRO/1000 network driver, run:
</div><pre class="screen">~]# <code class="command">modinfo e1000e</code>
-filename: /lib/modules/3.15.6-200.fc20.x86_64/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
+filename: /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
version: 2.3.2-k
license: GPL
description: Intel(R) PRO/1000 Network Driver
author: Intel Corporation, <linux.nics at intel.com>
-srcversion: AB1D5F954DC03B1296E61BD
+srcversion: 2FBED3F5E2EF40112284D95
alias: pci:v00008086d00001503sv*sd*bc*sc*i*
alias: pci:v00008086d00001502sv*sd*bc*sc*i*
<em class="lineannotation"><span class="lineannotation">[some <code class="literal">alias</code> lines omitted]</span></em>
alias: pci:v00008086d0000105Esv*sd*bc*sc*i*
depends: ptp
intree: Y
-vermagic: 3.15.6-200.fc20.x86_64 SMP mod_unload
+vermagic: 3.17.4-302.fc21.x86_64 SMP mod_unload
signer: Fedora kernel signing key
-sig_key: 5B:F5:46:43:B9:B1:61:72:B2:43:6D:40:A5:6F:75:0A:D1:58:1D:80
+sig_key: 1F:C9:E6:8F:74:19:55:63:48:FD:EE:2F:DE:B7:FF:9D:A6:33:7B:BF
sig_hashalgo: sha256
parm: debug:Debug level (0=none,...,16=all) (int)
parm: copybreak:Maximum size of packet that is copied to a new buffer on receive (uint)
@@ -10276,7 +11834,7 @@ parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the
<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">
+ </div></li></ul></div><div class="example" id="ex-Listing_module_parameters"><h6>Example 22.2. Listing module parameters</h6><div class="example-contents"><div class="para">
You can list all parameters that the module supports by using the <code class="option">-p</code> option. However, because useful value type information is omitted from <code class="command">modinfo -p</code> output, it is more useful to run:
</div><pre class="screen">~]# <code class="command">modinfo e1000e | grep "^parm" | sort</code>
parm: copybreak:Maximum size of packet that is copied to a new buffer on receive (uint)
@@ -10290,27 +11848,26 @@ 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">21.3. Loading a Module</h2></div></div></div><a id="idm225439765936" class="indexterm"></a><a id="idm225439764016" class="indexterm"></a><a id="idm225460614512" class="indexterm"></a><div class="para">
+parm: WriteProtectNVM:Write-protect NVM [WARNING: disabling this can lead to corrupted NVM] (array of int)</pre></div></div><br class="example-break" /></dd></dl></div></div><div class="section" id="sec-Loading_a_Module"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">22.3. Loading a Module</h2></div></div></div><a id="idm261728766688" class="indexterm"></a><a id="idm261743156720" class="indexterm"></a><a id="idm261743154640" 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="idm225371382720" class="indexterm"></a><div class="para">
+</pre><a id="idm261747957136" class="indexterm"></a><div class="para">
By default, <code class="command">modprobe</code> attempts to load the module from <code class="filename">/lib/modules/<em class="replaceable"><code>kernel_version</code></em>/kernel/drivers/</code>. In this directory, each type of module has its own subdirectory, such as <code class="filename">net/</code> and <code class="filename">scsi/</code>, for network and SCSI interface drivers respectively.
</div><div class="para">
Some modules have dependencies, which are other kernel modules that must be loaded before the module in question can be loaded. The <code class="command">modprobe</code> command always takes dependencies into account when performing operations. When you ask <code class="command">modprobe</code> to load a specific kernel module, it first examines the dependencies of that module, if there are any, and loads them if they are not already loaded into the kernel. <code class="command">modprobe</code> resolves dependencies recursively: it will load all dependencies of dependencies, and so on, if necessary, thus ensuring that all dependencies are always met.
</div><div class="para">
You can use the <code class="option">-v</code> (or <code class="option">--verbose</code>) option to cause <code class="command">modprobe</code> to display detailed information about what it is doing, which can include loading module dependencies.
- </div><div class="example" id="ex-modprobe_-v_shows_module_dependencies_as_they_are_loaded"><h6>Example 21.3. modprobe -v shows module dependencies as they are loaded</h6><div class="example-contents"><div class="para">
+ </div><div class="example" id="ex-modprobe_-v_shows_module_dependencies_as_they_are_loaded"><h6>Example 22.3. modprobe -v shows module dependencies as they are loaded</h6><div class="example-contents"><div class="para">
You can load the <code class="systemitem">Fibre Channel over Ethernet</code> module verbosely by typing the following at a shell prompt:
</div><pre class="screen">~]# <code class="command">modprobe -v fcoe</code>
-insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/scsi_tgt.ko
-insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/scsi_transport_fc.ko
-insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/libfc/libfc.ko
-insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/fcoe/libfcoe.ko
-insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko</pre><div class="para">
+insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/scsi_transport_fc.ko.xz
+insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/libfc/libfc.ko.xz
+insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/fcoe/libfcoe.ko.xz
+insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko.xz</pre><div class="para">
In this example, you can see that <code class="command">modprobe</code> loaded the <code class="systemitem">scsi_tgt</code>, <code class="systemitem">scsi_transport_fc</code>, <code class="systemitem">libfc</code> and <code class="systemitem">libfcoe</code> modules as dependencies before finally loading <code class="systemitem">fcoe</code>. Also note that <code class="command">modprobe</code> used the more primitive <code class="command">insmod</code> command to insert the modules into the running kernel.
- </div></div></div><br class="example-break" /><a id="idm225467889408" class="indexterm"></a><a id="idm225467887328" 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">
+ </div></div></div><br class="example-break" /><a id="idm261721610064" class="indexterm"></a><a id="idm261744372944" 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">21.4. Unloading a Module</h2></div></div></div><a id="idm225498865248" class="indexterm"></a><a id="idm225498863808" class="indexterm"></a><a id="idm225452959792" class="indexterm"></a><div class="para">
+ </div></div></div></div><div class="section" id="sec-Unloading_a_Module"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">22.4. Unloading a Module</h2></div></div></div><a id="idm261746968320" class="indexterm"></a><a id="idm261746966880" class="indexterm"></a><a id="idm261746964800" 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">
@@ -10322,8 +11879,8 @@ insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko</pre
</div></li><li class="listitem"><div class="para">
any module that <code class="systemitem">wacom</code>, through the dependency tree, depends on indirectly.
</div></li></ul></div><div class="para">
- See <a class="xref" href="#sec-Listing_Currently-Loaded_Modules">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">
+ See <a class="xref" href="#sec-Listing_Currently-Loaded_Modules">Section 22.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 22.4. Unloading a kernel module</h6><div class="example-contents"><div class="para">
For example, if you want to unload the <code class="systemitem">firewire_ohci</code> module, your terminal session might look similar to this:
</div><pre class="screen">~]# <code class="command">modinfo -F depends firewire_ohci</code>
firewire-core
@@ -10340,15 +11897,15 @@ rmmod firewire_ohci
rmmod firewire_core
rmmod crc_itu_t</pre><div class="para">
The output shows that modules are unloaded in the reverse order that they are loaded, given that no processes depend on any of the modules being unloaded.
- </div></div></div><br class="example-break" /><a id="idm225466327984" class="indexterm"></a><a id="idm225437750000" 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">
+ </div></div></div><br class="example-break" /><a id="idm261745854992" class="indexterm"></a><a id="idm261745852912" 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">21.5. Setting Module Parameters</h2></div></div></div><a id="idm225443099424" class="indexterm"></a><a id="idm225436188240" class="indexterm"></a><div class="para">
+ </div></div></div></div><div class="section" id="sec-Setting_Module_Parameters"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">22.5. Setting Module Parameters</h2></div></div></div><a id="idm261680978672" class="indexterm"></a><a id="idm261680977232" 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="example" id="ex-Supplying_optional_parameters_when_loading_a_kernel_module"><h6>Example 21.5. Supplying optional parameters when loading a kernel module</h6><div class="example-contents"><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 22.6, “Persistent Module Loading”</a>, though the following information is a prerequisite.
+ </div></li></ol></div><div class="example" id="ex-Supplying_optional_parameters_when_loading_a_kernel_module"><h6>Example 22.5. Supplying optional parameters when loading a kernel module</h6><div class="example-contents"><div class="para">
You can use <code class="command">modprobe</code> to load a kernel module with custom parameters using the following command line format:
</div><pre class="screen">~]# <code class="command">modprobe <em class="replaceable"><code>module_name</code></em> [<span class="optional"><em class="replaceable"><code>parameter</code></em>=<em class="replaceable"><code>value</code></em></span>] </code>
</pre></div></div><br class="example-break" /><div class="para">
@@ -10367,24 +11924,348 @@ rmmod crc_itu_t</pre><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">
+ </div><div class="procedure" id="proc-Loading_a_Kernel_Module_with_Custom_Parameters"><h6>Procedure 22.1. Loading a Kernel Module with Custom Parameters</h6><ol class="1"><li class="step" id="proc-step1-Loading_a_Kernel_Module_with_Custom_Parameters"><div class="para">
First, ensure the module is not already loaded into the kernel:
</div><pre class="screen">~]# <code class="command">lsmod |grep e1000e</code>
~]# </pre><div class="para">
- Output would indicate that the module is already loaded into the kernel, in which case you must first unload it before proceeding. See <a class="xref" href="#sec-Unloading_a_Module">Section 21.4, “Unloading a Module”</a> for instructions on safely unloading it.
+ Output would indicate that the module is already loaded into the kernel, in which case you must first unload it before proceeding. See <a class="xref" href="#sec-Unloading_a_Module">Section 22.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 turn on debug, you would run, as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">modprobe e1000e InterruptThrottleRate=3000,3000,3000 debug=1</code>
</pre><div class="para">
This example illustrates passing multiple values to a single parameter by separating them with commas and omitting any spaces between them.
- </div></li></ol></div></div><div class="section" id="sec-Persistent_Module_Loading"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.6. Persistent Module Loading</h2></div></div></div><a id="idm225452305072" class="indexterm"></a><a id="idm225466358208" 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 the <code class="systemitem">systemd-modules-load.service</code> daemon by creating a <code class="filename"><em class="replaceable"><code>program</code></em>.conf</code> file in the <code class="filename">/etc/modules-load.d/</code> directory, where <em class="replaceable"><code>program</code></em> is any descriptive name of your choice. The files in <code class="filename">/etc/modules-load.d/</code> are text files that list the modules to be loaded, one per line.
- </div><div class="example" id="ex-A_Text_File_to_Load_a_Module"><h6>Example 21.6. A Text File to Load a Module</h6><div class="example-contents"><div class="para">
+ </div></li></ol></div></div><div class="section" id="sec-Persistent_Module_Loading"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">22.6. Persistent Module Loading</h2></div></div></div><a id="idm261720464384" class="indexterm"></a><a id="idm261720462464" class="indexterm"></a><div class="para">
+ As shown in <a class="xref" href="#ex-Listing_information_about_a_kernel_module_with_lsmod">Example 22.1, “Listing information about a kernel module with lsmod”</a>, many kernel modules are loaded automatically at boot time. You can specify additional modules to be loaded by the <code class="systemitem">systemd-modules-load.service</code> daemon by creating a <code class="filename"><em class="replaceable"><code>program</code></em>.conf</code> file in the <code class="filename">/etc/modules-load.d/</code> directory, where <em class="replaceable"><code>program</code></em> is any descriptive name of your choice. The files in <code class="filename">/etc/modules-load.d/</code> are text files that list the modules to be loaded, one per line.
+ </div><div class="example" id="ex-A_Text_File_to_Load_a_Module"><h6>Example 22.6. A Text File to Load a Module</h6><div class="example-contents"><div class="para">
To create a file to load the <code class="filename">virtio-net.ko</code> module, create a file <code class="filename">/etc/modules-load.d/virtio-net.conf</code> with the following content:
</div><pre class="screen"># Load virtio-net.ko at boot
virtio-net</pre></div></div><br class="example-break" /><div class="para">
See the <code class="filename">modules-load.d(5)</code> and <code class="filename">systemd-modules-load.service(8)</code> man pages for more information.
- </div></div><div class="section" id="s1-kernel-modules-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.7. Additional Resources</h2></div></div></div><div class="para">
+ </div></div><div class="section" id="sect-signing-kernel-modules-for-secure-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">22.7. Signing Kernel Modules for Secure Boot</h2></div></div></div><div class="para">
+ Fedora includes support for the UEFI Secure Boot feature, which means that Fedora can be installed and run on systems where UEFI Secure Boot is enabled. <a href="#ftn.idm261731318688" class="footnote"><sup class="footnote" id="idm261731318688">[2]</sup></a> When Secure Boot is enabled, the EFI operating system boot loaders, the Fedora kernel, and all kernel modules must be signed with a private key and authenticated with the corresponding public key. The Fedora distribution includes signed boot loaders, signed kernels, and signed kernel modules. In addition, the signed first-stage boot loader and the signed kernel include embedded Fedora public keys. These signed executable binaries and embedded keys enable Fedora to install, boot, and run with the Microsoft UEFI Secure Boot CA keys that are provided by the UEFI firmware on systems that support UEFI Secure Boot.<a href="#ftn.idm261731317152" class="footnote"><sup class="footnote" id="idm261731317152">[3]</sup></a>
+ </div><div class="para">
+ The information provided in the following sections describes steps necessary to enable you to self-sign privately built kernel modules for use with Fedora on UEFI-based systems where Secure Boot is enabled. These sections also provide an overview of available options for getting your public key onto the target system where you want to deploy your kernel module.
+ </div><div class="section" id="sect-prerequisites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.1. Prerequisites</h3></div></div></div><div class="para">
+ In order to enable signing of externally built modules, the tools listed in the following table are required to be installed on the system.
+ </div><div class="table" id="table-required-tools"><h6>Table 22.1. Required Tools</h6><div class="table-contents"><table summary="Required Tools" border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><thead><tr><th class="" align="left">
+ Tool
+ </th><th class="" align="left">
+ Provided by Package
+ </th><th class="" align="left">
+ Used on
+ </th><th class="" align="left">
+ Purpose
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ <code class="command">openssl</code>
+ </td><td class="" align="left">
+ <span class="package">openssl</span>
+ </td><td class="" align="left">
+ Build system
+ </td><td class="" align="left">
+ Generates public and private X.509 key pair
+ </td></tr><tr><td class="" align="left">
+ <code class="command">sign-file</code>
+ </td><td class="" align="left">
+ <span class="package">kernel-devel</span>
+ </td><td class="" align="left">
+ Build system
+ </td><td class="" align="left">
+ Perl script used to sign kernel modules
+ </td></tr><tr><td class="" align="left">
+ <code class="command">perl</code>
+ </td><td class="" align="left">
+ <span class="package">perl</span>
+ </td><td class="" align="left">
+ Build system
+ </td><td class="" align="left">
+ Perl interpreter used to run the signing script
+ </td></tr><tr><td class="" align="left">
+ <code class="command">mokutil</code>
+ </td><td class="" align="left">
+ <span class="package">mokutil</span>
+ </td><td class="" align="left">
+ Target system
+ </td><td class="" align="left">
+ Optional tool used to manually enroll the public key
+ </td></tr><tr><td class="" align="left">
+ <code class="command">keyctl</code>
+ </td><td class="" align="left">
+ <span class="package">keyutils</span>
+ </td><td class="" align="left">
+ Target system
+ </td><td class="" align="left">
+ Optional tool used to display public keys in the system key ring
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that the build system, where you build and sign your kernel module, does not need to have UEFI Secure Boot enabled and does not even need to be a UEFI-based system.
+ </div></div></div></div><div class="section" id="sect-kernel-module-authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.2. Kernel Module Authentication</h3></div></div></div><div class="para">
+ In Fedora, when a kernel module is loaded, the module's signature is checked using the public X.509 keys on the kernel's system key ring, excluding those keys that are on the kernel's system black list key ring.
+ </div><div class="section" id="sect-sources-for-public-keys-used-to-authenticate-kernel-modules"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">22.7.2.1. Sources For Public Keys Used To Authenticate Kernel Modules</h4></div></div></div><div class="para">
+ During boot, the kernel loads X.509 keys into the system key ring or the system black list key ring from a set of persistent key stores as shown in <a class="xref" href="#table-sources-for-system-key-rings">Table 22.2, “Sources For System Key Rings”</a>
+ </div><div class="table" id="table-sources-for-system-key-rings"><h6>Table 22.2. Sources For System Key Rings</h6><div class="table-contents"><table summary="Sources For System Key Rings" border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><thead><tr><th class="" align="left">
+ Source of X.509 Keys
+ </th><th class="" align="left">
+ User Ability to Add Keys
+ </th><th class="" align="left">
+ UEFI Secure Boot State
+ </th><th class="" align="left">
+ Keys Loaded During Boot
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ Embedded in kernel
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2" align="left">
+ UEFI Secure Boot "db"
+ </td><td class="" rowspan="2" align="left">
+ Limited
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2" align="left">
+ UEFI Secure Boot "dbx"
+ </td><td class="" rowspan="2" align="left">
+ Limited
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2" align="left">
+ Embedded in <code class="systemitem">shim.efi</code> boot loader
+ </td><td class="" rowspan="2" align="left">
+ No
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2" align="left">
+ Machine Owner Key (MOK) list
+ </td><td class="" rowspan="2" align="left">
+ Yes
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Note that if the system is not UEFI-based or if UEFI Secure Boot is not enabled, then only the keys that are embedded in the kernel are loaded onto the system key ring and you have no ability to augment that set of keys without rebuilding the kernel. The system black list key ring is a list of X.509 keys which have been revoked. If your module is signed by a key on the black list then it will fail authentication even if your public key is in the system key ring.
+ </div><div class="para">
+ You can display information about the keys on the system key rings using the <code class="command">keyctl</code> utility. The following is abbreviated example output from a Fedora system where UEFI Secure Boot is not enabled.
+ </div><pre class="screen">~]# <code class="command">keyctl list %:.system_keyring</code>
+1 key in keyring:
+ 61139991: ---lswrv 0 0 asymmetric: Fedora kernel signing key: 1fc9e68f7419556348fdee2fdeb7ff9da6337b</pre><div class="para">
+ The following is abbreviated example output from a Fedora system where UEFI Secure Boot is enabled.
+ </div><pre class="screen">~]# <code class="command">keyctl list %:.system_keyring</code>
+6 keys in keyring:
+...asymmetric: Red Hat Enterprise Linux Driver Update Program (key 3): bf57f3e87...
+...asymmetric: Red Hat Secure Boot (CA key 1): 4016841644ce3a810408050766e8f8a29...
+...asymmetric: Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed...
+...asymmetric: Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e...
+...asymmetric: Red Hat Enterprise Linux kernel signing key: 4249689eefc77e95880b...
+...asymmetric: Red Hat Enterprise Linux kpatch signing key: 4d38fd864ebe18c5f0b7...</pre><div class="para">
+ The above output shows the addition of two keys from the UEFI Secure Boot "db" keys plus the <code class="computeroutput">Red Hat Secure Boot (CA key 1)</code> which is embedded in the <code class="systemitem">shim.efi</code> boot loader. You can also look for the kernel console messages that identify the keys with an UEFI Secure Boot related source, that is UEFI Secure Boot db, embedded shim, and MOK list.
+ </div><pre class="screen">~]# <code class="command">dmesg | grep 'EFI: Loaded cert'</code>
+[5.160660] EFI: Loaded cert 'Microsoft Windows Production PCA 2011: a9290239...
+[5.160674] EFI: Loaded cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309b...
+[5.165794] EFI: Loaded cert 'Red Hat Secure Boot (CA key 1): 4016841644ce3a8...</pre></div><div class="section" id="sect-kernel-module-authentication-requirements"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">22.7.2.2. Kernel Module Authentication Requirements </h4></div></div></div><div class="para">
+ If UEFI Secure Boot is enabled or if the <code class="option">module.sig_enforce</code> kernel parameter has been specified, then only signed kernel modules that are authenticated using a key on the system key ring can be successfully loaded.<a href="#ftn.idm261748354784" class="footnote"><sup class="footnote" id="idm261748354784">[4]</sup></a> If UEFI Secure Boot is disabled and if the <code class="option">module.sig_enforce</code> kernel parameter has not been specified, then unsigned kernel modules and signed kernel modules without a public key can be successfully loaded. This is summarized in <a class="xref" href="#table-kernel-module-authentication-requirements-for-loading">Table 22.3, “Kernel Module Authentication Requirements for Loading”</a>.
+ </div><div class="table" id="table-kernel-module-authentication-requirements-for-loading"><h6>Table 22.3. Kernel Module Authentication Requirements for Loading</h6><div class="table-contents"><table summary="Kernel Module Authentication Requirements for Loading" border="1"><colgroup><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /></colgroup><thead><tr><th class="" align="left">
+ Module Signed
+ </th><th class="" align="left">
+ Public Key Found and Signature Valid
+ </th><th class="" align="left">
+ UEFI Secure Boot State
+ </th><th class="" align="left">
+ module.sig_enforce
+ </th><th class="" align="left">
+ Module Load
+ </th><th class="" align="left">
+ Kernel Tainted
+ </th></tr></thead><tbody><tr><td class="" rowspan="3" align="left">
+ Unsigned
+ </td><td class="" rowspan="3" align="left">
+ -
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ </td></tr><tr><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ -
+ </td></tr><tr><td class="" rowspan="3" align="left">
+ Signed
+ </td><td class="" rowspan="3" align="left">
+ No
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ -
+ </td></tr><tr><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ -
+ </td></tr><tr><td class="" rowspan="3" align="left">
+ Signed
+ </td><td class="" rowspan="3" align="left">
+ Yes
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ No
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Subsequent sections will describe how to generate a public and private X.509 key pair, how to use the private key to sign a kernel module, and how to enroll the public key into a source for the system key ring.
+ </div></div></div><div class="section" id="sect-generating-a-public-private-x509-key-pair"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.3. Generating a Public and Private X.509 Key Pair</h3></div></div></div><div class="para">
+ You need to generate a public and private X.509 key pair that will be used to sign a kernel module after it has been built. The corresponding public key will be used to authenticate the kernel module when it is loaded.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ The <code class="command">openssl</code> tool can be used to generate a key pair that satisfies the requirements for kernel module signing in Fedora. Some of the parameters for this key generation request are best specified with a configuration file; follow the example below to create your own configuration file.
+ </div><pre class="screen">~]# <code class="command">cat << EOF > <em class="replaceable"><code>configuration_file</code></em>.config</code>
+[ req ]
+default_bits = 4096
+distinguished_name = req_distinguished_name
+prompt = no
+string_mask = utf8only
+x509_extensions = myexts
+
+[ req_distinguished_name ]
+O = <em class="replaceable"><code>Organization</code></em>
+CN = <em class="replaceable"><code>Organization signing key</code></em>
+emailAddress = <em class="replaceable"><code>E-mail address</code></em>
+
+[ myexts ]
+basicConstraints=critical,CA:FALSE
+keyUsage=digitalSignature
+subjectKeyIdentifier=hash
+authorityKeyIdentifier=keyid
+EOF</pre></li><li class="step"><div class="para">
+ After you have created the configuration file, you can create an X.509 public and private key pair. The public key will be written to the <code class="filename"><em class="replaceable"><code>public_key</code></em>.der</code> file and the private key will be written to the <code class="filename"><em class="replaceable"><code>private_key</code></em>.priv</code> file.
+ </div><pre class="screen">~]# <code class="command">openssl req -x509 -new -nodes -utf8 -sha256 -days 36500 \ > -batch -config <em class="replaceable"><code>configuration_file</code></em>.config -outform DER \ > -out <em class="replaceable"><code>public_key</code></em>.der \ > -keyout <em class="replaceable"><code>private_key</code></em>.priv</code></pre></li><li class="step"><div class="para">
+ Enroll your public key on all systems where you want to authenticate and load your kernel module.
+ </div></li></ol></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Take proper care to guard the contents of your private key. In the wrong hands, the key could be used to compromise any system which has your public key.
+ </div></div></div></div><div class="section" id="sect-enrolling-public-key-on-target-system"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.4. Enrolling Public Key on Target System</h3></div></div></div><div class="para">
+ When Fedora boots on a UEFI-based system with Secure Boot enabled, all keys that are in the Secure Boot db key database, but not in the dbx database of revoked keys, are loaded onto the system keyring by the kernel. The system keyring is used to authenticate kernel modules.
+ </div><div class="section" id="sect-factory-firmware-image-including-public-key"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">22.7.4.1. Factory Firmware Image Including Public Key</h4></div></div></div><div class="para">
+ To facilitate authentication of your kernel module on your systems, consider requesting your system vendor to incorporate your public key into the UEFI Secure Boot key database in their factory firmware image.
+ </div></div><div class="section" id="sect-executable-key-enrollment-image-adding-public-key"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">22.7.4.2. Executable Key Enrollment Image Adding Public Key</h4></div></div></div><div class="para">
+ It is possible to add a key to an existing populated and active Secure Boot key database. This can be done by writing and providing an EFI executable <span class="emphasis"><em>enrollment</em></span> image. Such an enrollment image contains a properly formed request to append a key to the Secure Boot key database. This request must include data that is properly signed by the private key that corresponds to a public key that is already in the system's Secure Boot Key Exchange Key (KEK) database. Additionally, this EFI image must be signed by a private key that corresponds to a public key that is already in the key database.
+ </div><div class="para">
+ It is also possible to write an enrollment image that runs under Fedora. However, the Fedora image must be properly signed by a private key that corresponds to a public key that is already in the KEK database.
+ </div><div class="para">
+ The construction of either type of key enrollment images requires assistance from the platform vendor.
+ </div></div><div class="section" id="sect-system-administrator-manually-adding-public-key-to-the-mok-list"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">22.7.4.3. System Administrator Manually Adding Public Key to the MOK List</h4></div></div></div><div class="para">
+ The Machine Owner Key (MOK) facility is a feature that is supported by Fedora and can be used to augment the UEFI Secure Boot key database. When Fedora boots on a UEFI-enabled system with Secure Boot enabled, the keys on the MOK list are also added to the system keyring in addition to the keys from the key database. The MOK list keys are also stored persistently and securely in the same fashion as the Secure Boot key database keys, but these are two separate facilities. The MOK facility is supported by shim.efi, MokManager.efi, grubx64.efi, and the Fedora <code class="command">mokutil</code> utility.
+ </div><div class="para">
+ The major capability provided by the MOK facility is the ability to add public keys to the MOK list without needing to have the key chain back to another key that is already in the KEK database. However, enrolling a MOK key requires manual interaction by a <span class="emphasis"><em>physically present</em></span> user at the UEFI system console on each target system. Nevertheless, the MOK facility provides an excellent method for testing newly generated key pairs and testing kernel modules signed with them.
+ </div><div class="para">
+ Follow these steps to add your public key to the MOK list:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Request addition of your public key to the MOK list using a Fedora userspace utility:
+ </div><pre class="screen">~]# <code class="command">mokutil <code class="option">--import</code> <code class="filename">my_signing_key_pub.der</code></code></pre><div class="para">
+ You will be asked to enter and confirm a password for this MOK enrollment request.
+ </div></li><li class="step"><div class="para">
+ Reboot the machine.
+ </div></li><li class="step"><div class="para">
+ The pending MOK key enrollment request will be noticed by <code class="systemitem">shim.efi</code> and it will launch <code class="systemitem">MokManager.efi</code> to allow you to complete the enrollment from the UEFI console. You will need to enter the password you previously associated with this request and confirm the enrollment. Your public key is added to the MOK list, which is persistent.
+ </div></li></ol></div><div class="para">
+ Once a key is on the MOK list, it will be automatically propagated to the system key ring on this and subsequent boots when UEFI Secure Boot is enabled.
+ </div></div></div><div class="section" id="sect-signing-kernel-module-with-the-private-key"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.5. Signing Kernel Module with the Private Key</h3></div></div></div><div class="para">
+ There are no extra steps required to prepare your kernel module for signing. You build your kernel module normally. Assuming an appropriate Makefile and corresponding sources, follow these steps to build your module and sign it:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Build your <code class="filename">my_module.ko</code> module the standard way:
+ </div><pre class="screen">~]# <code class="command">make -C /usr/src/kernels/$(uname -r) M=$PWD modules</code></pre></li><li class="step"><div class="para">
+ Sign your kernel module with your private key. This is done with a Perl script. Note that the script requires that you provide both the files that contain your private and the public key as well as the kernel module file that you want to sign.
+ </div><pre class="screen">~]# <code class="command">perl /usr/src/kernels/$(uname -r)/scripts/sign-file \ > sha256 \ > my_signing_key.priv \ > my_signing_key_pub.der \ > my_module.ko</code></pre></li></ol></div><div class="para">
+ Your kernel module is in ELF image format and this script computes and appends the signature directly to the ELF image in your <code class="filename">my_module.ko</code> file. The <code class="command">modinfo</code> utility can be used to display information about the kernel module's signature, if it is present. For information on using the utility, see <a class="xref" href="#sec-Displaying_Information_About_a_Module">Section 22.2, “Displaying Information About a Module”</a>.
+ </div><div class="para">
+ Note that this appended signature is not contained in an ELF image section and is not a formal part of the ELF image. Therefore, tools such as <code class="command">readelf</code> will not be able to display the signature on your kernel module.
+ </div><div class="para">
+ Your kernel module is now ready for loading. Note that your signed kernel module is also loadable on systems where UEFI Secure Boot is disabled or on a non-UEFI system. That means you do not need to provide both a signed and unsigned version of your kernel module.
+ </div></div><div class="section" id="sect-loading-signed-kernel-module"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.6. Loading Signed Kernel Module</h3></div></div></div><div class="para">
+ Once your public key is enrolled and is in the system keyring, the normal kernel module loading mechanisms will work transparently. In the following example, you will use <code class="command">mokutil</code> to add your public key to the MOK list and you will manually load your kernel module with <code class="command">modprobe</code>.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Optionally, you can verify that your kernel module will not load before you have enrolled your public key. First, verify what keys have been added to the system key ring on the current boot by running the <code class="command">keyctl list %:.system_keyring</code> as root. Since your public key has not been enrolled yet, it should not be displayed in the output of the command.
+ </div></li><li class="step"><div class="para">
+ Request enrollment of your public key.
+ </div><pre class="screen">~]# <code class="command">mokutil --import <em class="replaceable"><code>my_signing_key_pub</code></em>.der</code></pre></li><li class="step"><div class="para">
+ Reboot, and complete the enrollment at the UEFI console.
+ </div><pre class="screen">~]# <code class="command">reboot</code></pre></li><li class="step"><div class="para">
+ After the system reboots, verify the keys on the system key ring again.
+ </div><pre class="screen">~]# <code class="command">keyctl list %:.system_keyring</code></pre></li><li class="step"><div class="para">
+ You should now be able to load your kernel module successfully.
+ </div><pre class="screen">~]# <code class="command">modprobe -v <em class="replaceable"><code>my_module</code></em></code>
+insmod /lib/modules/3.17.4-302.fc21.x86_64/extra/<em class="replaceable"><code>my_module</code></em>.ko
+~]# <code class="command">lsmod | grep <em class="replaceable"><code>my_module</code></em></code>
+<em class="replaceable"><code>my_module</code></em> 12425 0</pre></li></ol></div></div></div><div class="section" id="s1-kernel-modules-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">22.8. Additional Resources</h2></div></div></div><div class="para">
For more information on kernel modules and their utilities, see the following resources.
</div><h3 id="bh-Manual_Page_Documentation">Manual Page Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="filename">lsmod(8)</code> — The manual page for the <code class="command">lsmod</code> command.
@@ -10400,385 +12281,276 @@ virtio-net</pre></div></div><br class="example-break" /><div class="para">
<code class="filename">mii-tool(8)</code> — The manual page for the <code class="command">mii-tool</code> command.
</div></li></ul></div><h3 id="bh-Installable_and_External_Documentation">Installable and External Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://tldp.org/HOWTO/Module-HOWTO/">Linux Loadable Kernel Module HOWTO</a> — The <em class="citetitle">Linux Loadable Kernel Module HOWTO</em> from the Linux Documentation Project contains further information on working with kernel modules.
- </div></li></ul></div></div></div></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="idm225464380640" class="indexterm"></a><a id="idm225474980112" class="indexterm"></a><div class="para">
- The <em class="firstterm">RPM Package Manager</em> (RPM) is an open packaging system
- <a id="idm225477639936" 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></li></ul></div></div><div class="footnotes"><br /><hr width="100" align="left" /><div id="ftn.idm261731318688" class="footnote"><div class="para"><a href="#idm261731318688" class="para"><sup class="para">[2] </sup></a>
+ Fedora does not require the use of Secure Boot on UEFI systems.
+ </div></div><div id="ftn.idm261731317152" class="footnote"><div class="para"><a href="#idm261731317152" class="para"><sup class="para">[3] </sup></a>
+ Not all UEFI-based systems include support for Secure Boot.
+ </div></div><div id="ftn.idm261748354784" class="footnote"><div class="para"><a href="#idm261748354784" class="para"><sup class="para">[4] </sup></a>
+ Provided that the public key is not on the system black list key ring.
+ </div></div></div></div></div><div xml:lang="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="idm261755194032" class="indexterm"></a><a id="idm261692934512" class="indexterm"></a><a id="idm261748912768" class="indexterm"></a><div class="para">
+ The <em class="firstterm">RPM Package Manager</em> (<span class="application"><strong>RPM</strong></span>) is an open packaging system that runs on Fedora as well as other Linux and UNIX systems. Red Hat and the Fedora Project encourage other vendors to use <span class="application"><strong>RPM</strong></span> for their own products. <span class="application"><strong>RPM</strong></span> is distributed under the terms of the <em class="firstterm">GPL</em> (<em class="firstterm">GNU General Public License</em>).
</div><div class="para">
- The RPM package format has been improved for Fedora 21. 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="idm225480174352" 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. See <a class="xref" href="#ch-yum">Chapter 5, <em>Yum</em></a>.
+ The <span class="application"><strong>RPM Package Manager</strong></span> only works with packages built in the <span class="emphasis"><em>RPM format</em></span>. <span class="application"><strong>RPM</strong></span> itself is provided as the pre-installed <span class="package">rpm</span> package. For the end user, <span class="application"><strong>RPM</strong></span> makes system updates easy. Installing, uninstalling, and upgrading <span class="application"><strong>RPM</strong></span> packages can be accomplished with short commands. <span class="application"><strong>RPM</strong></span> maintains a database of installed packages and their files, so you can make queries and verify installed files on your system. There are several applications, such as <span class="application"><strong>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span>, that can make working with packages in the <span class="application"><strong>RPM</strong></span> format e
ven easier.
+ </div><div class="warning" id="warning-Use_Yum_Instead_of_RPM_Whenever_Possible"><div class="admonition_header"><h2>Use Yum Instead of RPM Whenever Possible</h2></div><div class="admonition"><a id="idm261718107200" class="indexterm"></a><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 <span class="application"><strong>RPM</strong></span>. <span class="application"><strong>Yum</strong></span> also performs and tracks complicated system-dependency resolutions. <span class="application"><strong>Yum</strong></span> maintains the system integrity and forces a system integrity check if packages are installed or removed using another application, such as <span class="application"><strong>RPM</strong></span>, instead of <span class="application"><strong>Yum</strong></span>. For these reasons, it is highly recommended that you use <span class="application"><strong>Yum</strong></span> instead of <span class="application"><strong>RPM</strong></span> whenever possible to perform package-management tasks. See <a class="xref" href="#ch-yum">Chapter 5, <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.
- </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="idm225456718384" 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">A.1. RPM Design Goals</h2></div></div></div><a id="idm225502896416" class="indexterm"></a><div class="para">
- To understand how to use RPM, it can be helpful to understand the design goals of RPM:
- </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Upgradability
- <a id="idm225502893568" 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="idm225375649232" 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="idm225467563632" 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="idm225461762736" 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.
+ During upgrades, <span class="application"><strong>RPM</strong></span> handles configuration files carefully, so that you never lose your customizations — something that you cannot accomplish with regular <code class="filename">.tar.gz</code> files.
+ </div><a id="idm261757358480" class="indexterm"></a><div class="para">
+ For the developer, <span class="application"><strong>RPM</strong></span> enables software source code to be packaged into source and binary packages for end users. This process is quite simple and is driven from a single file and optional patches that you create. This clear delineation between pristine sources and your patches along with build instructions eases the maintenance of the package as new versions of the software are released.
+ </div><div class="note" id="note-Root_Permissions"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Because <span class="application"><strong>RPM</strong></span> can make changes to the system itself, performing operations like installing, upgrading, downgrading, and uninstalling binary packages system-wide requires <code class="systemitem">root</code> privileges in most cases.
+ </div></div></div><div class="section" id="s1-rpm-design"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.1. RPM Design Goals</h2></div></div></div><a id="idm261750353952" class="indexterm"></a><div class="para">
+ To understand how to use <span class="application"><strong>RPM</strong></span>, it is helpful to understand the design goals of <span class="application"><strong>RPM</strong></span>:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261750350176" class="indexterm"></a>
+ Upgradability </span></dt><dd><div class="para">
+ With <span class="application"><strong>RPM</strong></span>, you can upgrade individual components of your system without a complete reinstallation. When you get a new release of an operating system based on <span class="application"><strong>RPM</strong></span>, such as Fedora, you do not need to reinstall a fresh copy of the operating system on your machine (as you might need to with operating systems based on other packaging systems). <span class="application"><strong>RPM</strong></span> allows for intelligent, fully-automated, in-place upgrades of your system. In addition, configuration files in packages are preserved across upgrades, so you do not lose your customizations. There are no special upgrade files needed to upgrade a package because the same <span class="application"><strong>RPM</strong></span> file is used to both install and upgrade the package on the system.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261740821920" class="indexterm"></a>
+ Powerful Querying </span></dt><dd><div class="para">
+ <span class="application"><strong>RPM</strong></span> is designed to provide powerful querying options. You can perform searches on your copy of the database for packages or even just certain files. You can also easily find out what package a file belongs to and where the package came from. The files an <span class="application"><strong>RPM</strong></span> package contains are in a compressed archive, with a custom binary header containing useful information about the package and its contents, allowing you to query individual packages quickly and easily.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261720852368" class="indexterm"></a>
+ System Verification </span></dt><dd><div class="para">
+ Another powerful <span class="application"><strong>RPM</strong></span> feature is the ability to verify packages. It allows you to verify that the files installed on the system are the same as the ones supplied by a given package. If an inconsistency is detected, <span class="application"><strong>RPM</strong></span> notifies you, and you can reinstall the package if necessary. Any configuration files that you modified are preserved during reinstallation.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261756773360" class="indexterm"></a>
+ Pristine Sources </span></dt><dd><div class="para">
+ A crucial design goal was to allow the use of <span class="emphasis"><em>pristine</em></span> software sources, as distributed by the original authors of the software. With <span class="application"><strong>RPM</strong></span>, you have the pristine sources along with any patches that were used, plus complete build instructions. This is an important advantage for several reasons. For instance, if a new version of a program is released, you do not necessarily have to start from scratch to get it to compile. You can look at the patch to see what you <span class="emphasis"><em>might</em></span> need to do. All the compiled-in defaults, and all of the changes that were made to get the software to build properly, are easily visible using this technique.
+ </div><div class="para">
+ The goal of keeping sources pristine may seem important only for developers, but it results in higher quality software for end users.
</div></dd></dl></div></div><div class="section" id="s1-rpm-using"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.2. Using RPM</h2></div></div></div><div class="para">
- RPM has five basic modes of operation
- <a id="idm225461051312" 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">A.2.1. Finding RPM Packages</h3></div></div></div><a id="idm225472178176" class="indexterm"></a><a id="idm225472176736" 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 Fedora 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="idm225468561328" class="indexterm"></a>
- <a id="idm225468559920" 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="idm225481802608" class="indexterm"></a>
- <a id="idm225481801200" class="indexterm"></a>
- . See <a class="xref" href="#ch-yum">Chapter 5, <em>Yum</em></a> for details on how to use the official Fedora package repositories.
- </div></li><li class="listitem"><div class="para">
- The active Fedora mirrors contains many installable RPMs: <a href="http://mirrors.fedoraproject.org/publiclist/">http://mirrors.fedoraproject.org/publiclist/</a>.
- </div></li><li class="listitem"><div class="para">
- Unofficial, third-party repositories not affiliated with The Fedora Project also provide RPM packages.
- </div><div class="important"><div class="admonition_header"><h2>Third-party repositories and package compatibility</h2></div><div class="admonition"><div class="para">
- When considering third-party repositories for use with your Fedora system, pay close attention to the repository's web site with regard to package compatibility before adding the repository as a package source. Alternate package repositories may offer different, incompatible versions of the same software, including packages already included in the Fedora repositories.
- </div></div></div></li></ul></div></div><div class="section" id="sec-Installing_and_Upgrading"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">A.2.2. Installing and Upgrading</h3></div></div></div><a id="idm225447608112" class="indexterm"></a><a id="idm225447606672" class="indexterm"></a><a id="idm225447605232" class="indexterm"></a><a id="idm225470282144" class="indexterm"></a><div class="para">
- RPM packages typically have file names
- <a id="idm225470280416" class="indexterm"></a>
- like <code class="filename">tree-1.5.3-2.fc21.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">fc21</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:
+ <span class="application"><strong>RPM</strong></span> has five basic modes of operation
+ <a id="idm261730936304" class="indexterm"></a>
+ (not counting package building): installing, uninstalling, upgrading, querying, and verifying. This section contains an overview of each mode. For complete details and options, try <code class="command">rpm --help</code> or see <span class="citerefentry"><span class="refentrytitle">rpm</span>(8)</span>. Also, see <a class="xref" href="#s1-rpm-additional-resources">Section A.5, “Additional Resources”</a> for more information on <span class="application"><strong>RPM</strong></span>.
+ </div><div class="section" id="sec-Installing_and_Upgrading"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">A.2.1. Installing and Upgrading Packages</h3></div></div></div><a id="idm261737027248" class="indexterm"></a><a id="idm261649672256" class="indexterm"></a><a id="idm261649670816" class="indexterm"></a><a id="idm261649669376" class="indexterm"></a><a id="idm261649667936" class="indexterm"></a><div class="para">
+ <span class="application"><strong>RPM</strong></span> packages typically have file names in the following form:
+ </div><pre class="synopsis">package_name-version-release-operating_system-CPU_architecture.rpm</pre><div class="para">
+ For example the <code class="filename">tree-1.7.0-3.fc21.x86_64.rpm</code> file name includes the package name (<code class="filename">tree</code>), version (<code class="filename">1.7.0</code>), release (<code class="filename">3</code>), operating system major version (<code class="filename">fc21</code>) and <acronym class="acronym">CPU</acronym> architecture (<code class="filename">x86_64</code>).
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When installing a package, ensure it is compatible with your operating system and processor architecture. This can usually be determined by checking the package name. For example, the file name of an <span class="application"><strong>RPM</strong></span> package compiled for the AMD64/Intel 64 computer architectures ends with <code class="filename">x86_64.rpm</code>.
+ </div></div></div><div class="para">
+ The <code class="option">-U</code> (or <code class="option">--upgrade</code>) option has two functions, it can be used to:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- upgrade an existing but older package on the system to a newer version, or
+ upgrade an existing 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.
+ install a package 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.
+ The <code class="command">rpm -U <em class="replaceable"><code>package.rpm</code></em></code> command is therefore able to either <span class="emphasis"><em>upgrade</em></span> or <span class="emphasis"><em>install</em></span>, depending on the presence of an older version of <em class="replaceable"><code>package.rpm</code></em> on the system.
</div><div class="para">
- Assuming the <code class="filename">tree-1.5.3-2.fc21.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.fc21.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">
+ Assuming the <code class="filename">tree-1.7.0-3.fc21.x86_64.rpm</code> package is in the current directory, log in as <code class="systemitem">root</code> and type the following command at a shell prompt to either upgrade or install the <span class="package">tree</span> package:
+ </div><pre class="screen">~]# <code class="command">rpm -Uvh tree-1.7.0-3.fc21.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:
+ If the upgrade or installation is successful, the following output is displayed:
</div><pre class="screen">Preparing... ########################################### [100%]
1:tree ########################################### [100%]</pre><div class="warning" id="warning-Always_use_the_-i_install_option_to_install_new_kernel_packages"><div class="admonition_header"><h2>Always use the -i (install) option to install new kernel packages!</h2></div><div class="admonition"><div class="para">
- <code class="command">rpm</code> provides two different options for installing packages: the aforementioned <code class="option">-U</code> option (which historically stands for <span class="emphasis"><em>upgrade</em></span>), and the <code class="option">-i</code> option, 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>.
+ <code class="command">rpm</code> provides two different options for installing packages: the aforementioned <code class="option">-U</code> option (which historically stands for <span class="emphasis"><em>upgrade</em></span>), and the <code class="option">-i</code> option (which historically stands for <span class="emphasis"><em>install</em></span>). Because the <code class="option">-U</code> option includes both install and upgrade functions, the use of <code class="command">rpm -Uvh</code> with all packages, <span class="emphasis"><em>except <span class="package">kernel</span> packages</em></span>, is recommended.
</div><div class="para">
- You should always use the <code class="option">-i</code> option to 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>.
+ You should always use the <code class="option">-i</code> option to <span class="emphasis"><em>install</em></span> a new kernel package instead of upgrading it. This is because using the <code class="option">-U</code> option to upgrade a kernel package removes the previous (older) kernel package, which could render the system unable to boot if there is a problem with the new kernel. Therefore, use the <code class="command">rpm -i <em class="replaceable"><code>kernel_package</code></em> </code> command to install a new kernel <span class="emphasis"><em>without replacing any older <span class="package">kernel</span> packages</em></span>. For more information on installing <span class="package">kernel</span> packages, see <a class="xref" href="#ch-Manually_Upgrading_the_Kernel">Chapter 21, <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.fc21.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.fc21.x86_64.rpm: Header V3 RSA/SHA256 signature: BAD,
-key ID d22e77f2</pre><div class="para">
+ The signature of a package is checked automatically when installing or upgrading a package. The signature confirms that the package was signed by an authorized party. If the verification of the signature fails, an error message is displayed.
+ </div><div class="para">
If you do not have the appropriate key installed to verify the signature, the message contains the word <code class="computeroutput">NOKEY</code>:
- </div><pre class="screen">warning: tree-1.5.2.2-4.fc21.x86_64.rpm: Header V3 RSA/SHA1 signature: NOKEY, key ID 57bbccba</pre><div class="para">
- See <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">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="idm225462155536" class="indexterm"></a>
- <a id="idm225462154096" class="indexterm"></a>
- , the following output is displayed:
+ </div><pre class="screen">warning: tree-1.7.0-3.fc21.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 431d51: NOKEY</pre><div class="para">
+ See <a class="xref" href="#s1-check-rpm-sig">Section A.3.2, “Checking Package Signatures”</a> for more information on checking package signatures.
+ </div><div class="section" id="s3-rpm-errors"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">A.2.1.1. Replacing Already-Installed Packages</h4></div></div></div><a id="idm261728039904" class="indexterm"></a><a id="idm261728038464" class="indexterm"></a><div class="para">
+ If a package of the same name and version is already installed, the following output is displayed:
</div><pre class="screen">Preparing... ########################################### [100%]
- package tree-1.5.3-2.fc21.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.fc21.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">A.2.2.2. Conflicting Files</h4></div></div></div><a id="idm225444134336" 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="idm225444131984" class="indexterm"></a>
- <a id="idm225444828688" class="indexterm"></a>
- , the following is displayed:
- </div><pre class="screen">Preparing... ##################################################
- file /usr/bin/foobar from install of foo-1.0-1.fc21.x86_64 conflicts
-with file from package bar-3.1.1.fc21.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.fc21.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">A.2.2.3. Unresolved Dependency</h4></div></div></div><a id="idm225474839328" class="indexterm"></a><a id="idm225474837888" class="indexterm"></a><div class="para">
- RPM packages may sometimes depend on other packages
- <a id="idm225507677376" class="indexterm"></a>
- <a id="idm225507675936" 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.fc21.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.fc21.x86_64.rpm bar-3.1.1.fc21.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.fc21.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">A.2.3. Configuration File Changes</h3></div></div></div><a id="idm225458582560" class="indexterm"></a><a id="idm225458581152" class="indexterm"></a><div class="para">
- Because RPM performs intelligent upgrading of packages with configuration files
- <a id="idm225427386608" 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.fc21.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.fc21.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">A.2.4. Uninstalling</h3></div></div></div><a id="idm225446887328" class="indexterm"></a><a id="idm225446885888" class="indexterm"></a><a id="idm225436098800" class="indexterm"></a><a id="idm225436096880" 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.fc21.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.
+ package tree-1.7.0-3.fc21.x86_64 is already installed</pre><div class="para">
+ To install the package anyway, use the <code class="option">--replacepkgs</code> option, which tells <span class="application"><strong>RPM</strong></span> to ignore the error:
+ </div><pre class="screen">~]# <code class="command">rpm -Uvh --replacepkgs tree-1.7.0-3.fc21.x86_64.rpm</code></pre><div class="para">
+ This option is helpful if files installed from the package were deleted or if you want the original configuration files to be installed.
+ </div><div class="para">
+ If you attempt an upgrade to an <span class="emphasis"><em>older</em></span> version of a package (that is, if a newer version of the package is already installed), <span class="application"><strong>RPM</strong></span> informs you that a newer version is already installed. To force <span class="application"><strong>RPM</strong></span> to perform the downgrade, use the <code class="command">--oldpackage</code> option:
+ </div><pre class="synopsis"><code class="command">rpm -Uvh --oldpackage <em class="replaceable"><code>older_package.rpm</code></em></code></pre></div><div class="section" id="s3-rpm-conflicting-files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">A.2.1.2. Resolving File Conflicts</h4></div></div></div><a id="idm261783578048" class="indexterm"></a><a id="idm261680131792" class="indexterm"></a><a id="idm261680130352" class="indexterm"></a><div class="para">
+ If you attempt to install a package that contains a file that has already been installed by another package, a conflict message is displayed. To make <span class="application"><strong>RPM</strong></span> ignore this error, use the <code class="command">--replacefiles</code> option:
+ </div><pre class="synopsis"><code class="command">rpm -Uvh --replacefiles <em class="replaceable"><code>package.rpm</code></em></code></pre></div><div class="section" id="s3-rpm-unresolved-dependency"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">A.2.1.3. Satisfying Unresolved Dependencies</h4></div></div></div><a id="idm261731733680" class="indexterm"></a><a id="idm261731732240" class="indexterm"></a><a id="idm261731730800" class="indexterm"></a><a id="idm261738288640" class="indexterm"></a><div class="para">
+ <span class="application"><strong>RPM</strong></span> packages sometimes depend on other packages, which means that they require other packages to be installed to run properly. If you try to install a package that has an unresolved dependency, a message about a failed dependency is displayed.
+ </div><div class="para">
+ Find the suggested package(s) on the Fedora installation media or on one of the active Fedora mirrors and add it to the installation command. To determine which package contains the required file, use the <code class="option">--whatprovides</code> option:
+ </div><pre class="synopsis"><code class="command">rpm -q --whatprovides "<em class="replaceable"><code>required_file</code></em>"</code></pre><div class="para">
+ If the package that contains <em class="replaceable"><code>required_file</code></em> is in the <span class="application"><strong>RPM</strong></span> database, the name of the package is displayed.
+ </div><div class="warning" id="warning-Forcing_Package_Installation"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Although you can <span class="emphasis"><em>force</em></span> <code class="command">rpm</code> to install a package that has an unresolved dependency (using the <code class="option">--nodeps</code> option), this is <span class="emphasis"><em>not</em></span> recommended and will usually result in the installed software failing to run. Installing packages with <code class="option">--nodeps</code> can cause applications to misbehave or terminate unexpectedly. It can also cause serious package-management problems or system failure. For these reasons, heed the warnings about missing dependencies. The <span class="application"><strong>Yum</strong></span> package manager performs automatic dependency resolution and fetches dependencies from on-line repositories.
+ </div></div></div></div><div class="section" id="sec-Configuration_File_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">A.2.1.4. Preserving Changes in Configuration Files</h4></div></div></div><a id="idm261732568544" class="indexterm"></a><a id="idm261732567136" class="indexterm"></a><a id="idm261732565248" class="indexterm"></a><div class="para">
+ Because <span class="application"><strong>RPM</strong></span> performs intelligent upgrading of packages with configuration files, you may see the following message:
+ </div><pre class="screen">saving <em class="replaceable"><code>/etc/configuration_file.conf</code></em> as <em class="replaceable"><code>/etc/configuration_file.conf</code></em>.rpmsave</pre><div class="para">
+ This message means that the changes you made to the configuration file may not be <span class="emphasis"><em>forward-compatible</em></span> with the new configuration file in the package, so <span class="application"><strong>RPM</strong></span> saved your original file and installed a new one. You should investigate the differences between the two configuration files and resolve them as soon as possible to ensure that your system continues to function properly.
+ </div><div class="para">
+ Alternatively, <span class="application"><strong>RPM</strong></span> may save the package's <span class="emphasis"><em>new</em></span> configuration file as, for example, <code class="filename"><em class="replaceable"><code>configuration_file.conf</code></em>.rpmnew</code> and leave the configuration file you modified untouched. You should still resolve any conflicts between your modified configuration file and the new one, usually by merging changes from the old one to the new one, for example using the <code class="command">diff</code> program.
+ </div></div></div><div class="section" id="s2-rpm-uninstalling"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">A.2.2. Uninstalling Packages</h3></div></div></div><a id="idm261718641568" class="indexterm"></a><a id="idm261718640128" class="indexterm"></a><a id="idm261718638688" class="indexterm"></a><a id="idm261653391920" class="indexterm"></a><div class="para">
+ Uninstalling a package is just as simple as installing one. Type the following command at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code class="command">rpm -e <em class="replaceable"><code>package</code></em></code></pre><div class="note"><div class="admonition_header"><h2>rpm -e and package name errors</h2></div><div class="admonition"><div class="para">
+ Note that the command expects only the package <span class="emphasis"><em>name</em></span>, not the name of the original package <span class="emphasis"><em>file</em></span>. If you attempt to uninstall a package using the <code class="command">rpm -e</code> command and provide the original full file name, you receive a package-name error.
</div></div></div><div class="para">
You can encounter dependency errors when uninstalling a package if another installed package depends on the one you are trying to remove. For example:
- </div><pre class="screen">
-<code class="command">rpm -e ghostscript</code>
+ </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.fc21.x86_64
- libgs.so.8()(64bit) is needed by (installed) foomatic-4.0.3-1.fc21.x86_64
- libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.4-5.fc21.x86_64
- ghostscript is needed by (installed) printer-filters-1.1-4.fc21.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.fc21.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">A.2.5. Freshening</h3></div></div></div><a id="idm225434665568" class="indexterm"></a><a id="idm225434664128" 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.fc21.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">A.2.6. Querying</h3></div></div></div><a id="idm225477869376" class="indexterm"></a><a id="idm225477867936" 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.fc21.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">A.2.7. Verifying</h3></div></div></div><a id="idm225471996160" class="indexterm"></a><a id="idm225444591552" 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.fc21.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:
+ ghostscript is needed by (installed) ghostscript-cups-9.07-16.fc21.x86_64
+ ghostscript is needed by (installed) foomatic-4.0.9-6.fc21.x86_64
+ libgs.so.9()(64bit) is needed by (installed) libspectre-0.2.7-4.fc21.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.9-15.fc21.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed) cups-filters-1.0.35-15.fc21.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 you can <span class="emphasis"><em>force</em></span> <code class="command">rpm</code> to uninstall a package that has unresolved dependencies (using the <code class="option">--nodeps</code> option), this is <span class="emphasis"><em>not</em></span> recommended. Removing packages with <code class="option">--nodeps</code> can cause applications from the packages whose dependencies are removed to misbehave or terminate unexpectedly. It can also cause serious package-management problems or system failure. For these reasons, heed the warnings about failed dependencies.
+ </div></div></div></div><div class="section" id="s2-rpm-freshening"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">A.2.3. Freshening Packages</h3></div></div></div><a id="idm261740871008" class="indexterm"></a><a id="idm261740869568" class="indexterm"></a><div class="para">
+ Freshening is similar to upgrading, except that only installed packages are upgraded. Type the following command at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code class="command">rpm -Fvh <em class="replaceable"><code>package.rpm</code></em></code></pre><div class="para">
+ The <code class="option">-F</code> (or <code class="option">--freshen</code>) option compares the versions of the packages specified on the command line with the versions of packages that are already installed on the system. When a newer version of an already-installed package is processed by the <code class="option">--freshen</code> option, it is upgraded to the newer version. However, the <code class="option">--freshen</code> option does not install a package if no previously-installed package of the same name exists. This differs from regular upgrading, as an upgrade installs all specified packages regardless of whether or not older versions of the packages are already installed.
+ </div><div class="para">
+ Freshening works for single packages or package groups. For example, freshening can help if you download a large number of different packages, and you only want to upgrade those packages that are already installed on the system. In this case, issue the following command with the <code class="filename">*.rpm</code> global expression:
+ </div><pre class="screen">~]# <code class="command">rpm -Fvh *.rpm</code></pre><div class="para">
+ <span class="application"><strong>RPM</strong></span> then automatically upgrades only those packages that are already installed.
+ </div></div><div class="section" id="s2-rpm-querying"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">A.2.4. Querying Packages</h3></div></div></div><a id="idm261649738032" class="indexterm"></a><a id="idm261649736752" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>RPM</strong></span> database stores information about all <span class="application"><strong>RPM</strong></span> packages installed on the system. It is stored in the <code class="filename">/var/lib/rpm/</code> directory and is used for many things, including querying what packages are installed, what version each package is, and for calculating changes to files in packages since their installation. To query this database, use the <code class="command">rpm</code> command with the <code class="option">-q</code> (or <code class="option">--query</code>) option:
+ </div><pre class="synopsis"><code class="command">rpm -q <em class="replaceable"><code>package_name</code></em></code></pre><div class="para">
+ This command displays the package name, version, and release number of the installed package <em class="replaceable"><code>package_name</code></em>. For example:
+ </div><pre class="screen">~]$ <code class="command">rpm -q tree</code>
+tree-1.7.0-3.fc21.x86_64</pre><div class="para">
+ See the <code class="computeroutput">Package Selection Options</code> subheading in the <span class="citerefentry"><span class="refentrytitle">rpm</span>(8)</span> manual page for a list of options that can be used to further refine or qualify your query. Use options listed below the <code class="computeroutput">Package Query Options</code> subheading to specify what information to display about the queried packages.
+ </div></div><div class="section" id="s2-rpm-verifying"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">A.2.5. Verifying Packages</h3></div></div></div><a id="idm261751070688" class="indexterm"></a><a id="idm261733557168" class="indexterm"></a><div class="para">
+ Verifying a package is comparing information about files on the system installed from a package with the same information from the original package. Among other parameters, verifying compares the file size, MD5 sum, permissions, type, owner, and the group of each file.
+ </div><div class="para">
+ Use the <code class="command">rpm</code> command with the <code class="option">-V</code> (or <code class="option">--verify</code>) option to verify packages. For example:
+ </div><pre class="screen">~]$ <code class="command">rpm -V tree</code></pre><div class="para">
+ See the <code class="computeroutput">Package Selection Options</code> subheading in the <span class="citerefentry"><span class="refentrytitle">rpm</span>(8)</span> manual page for a list of options that can be used to further refine or qualify your query. Use options listed below the <code class="computeroutput">Verify Options</code> subheading to specify what characteristics to verify in the queried packages.
+ </div><div class="para">
+ If everything verifies properly, there is no output. If there are any discrepancies, they are displayed. The output consists of lines similar to these:
+ </div><pre class="screen">~]# <code class="command">rpm -V abrt</code>
+S.5....T. c /etc/abrt/abrt.conf
+.M....... /var/spool/abrt-upload</pre><div class="para">
+ The format of the output is a string of nine characters followed by an optional attribute marker and the name of the processed file.
+ </div><div class="para">
+ The first nine characters are the results of tests performed on the file. Each test is the comparison of one attribute of the file to the value of that attribute as recorded in the <span class="application"><strong>RPM</strong></span> database. A single period (<code class="computeroutput">.</code>) means the test passed, and the question-mark character (<code class="computeroutput">?</code>) signifies that the test could not be performed. The following table lists symbols that denote specific discrepancies:
+ </div><div class="table" id="tab-rpm-verification-symbols"><h6>Table A.1. RPM Verification Symbols</h6><div class="table-contents"><a id="idm261744747344" class="indexterm"></a><table summary="RPM Verification Symbols" border="1"><colgroup><col width="20%" class="symbol" /><col width="80%" class="description" /></colgroup><thead><tr><th class="">
+ Symbol
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="computeroutput">S</code>
+ </td><td class="">
+ file size differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">M</code>
+ </td><td class="">
+ mode differs (includes permissions and file type)
+ </td></tr><tr><td class="">
+ <code class="computeroutput">5</code>
+ </td><td class="">
+ digest (formerly MD5 sum) differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">D</code>
+ </td><td class="">
+ device major/minor number mismatch
+ </td></tr><tr><td class="">
+ <code class="computeroutput">L</code>
+ </td><td class="">
+ <span class="citerefentry"><span class="refentrytitle">readLink</span>(2)</span> path mismatch
+ </td></tr><tr><td class="">
+ <code class="computeroutput">U</code>
+ </td><td class="">
+ user ownership differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">G</code>
+ </td><td class="">
+ group ownership differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">T</code>
+ </td><td class="">
+ mtime differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">P</code>
+ </td><td class="">
+ capabilities differ
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The attribute marker, if present, describes the purpose of the given file. The following table lists the available attribute markers:
+ </div><div class="table" id="tab-rpm-verification-markers"><h6>Table A.2. RPM Verification Symbols</h6><div class="table-contents"><a id="idm261709620448" class="indexterm"></a><table summary="RPM Verification Symbols" border="1"><colgroup><col width="20%" class="marker" /><col width="80%" class="description" /></colgroup><thead><tr><th class="">
+ Marker
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="computeroutput">c</code>
+ </td><td class="">
+ configuration file
+ </td></tr><tr><td class="">
+ <code class="computeroutput">d</code>
+ </td><td class="">
+ documentation file
+ </td></tr><tr><td class="">
+ <code class="computeroutput">l</code>
+ </td><td class="">
+ license file
+ </td></tr><tr><td class="">
+ <code class="computeroutput">r</code>
+ </td><td class="">
+ readme file
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ If you see any output, use your best judgment to determine if you should remove the package, reinstall it, or fix the problem in another way.
+ </div></div></div><div class="section" id="s1-find-verify-rpm"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.3. Finding and Verifying RPM Packages</h2></div></div></div><a id="idm261753247696" class="indexterm"></a><div class="para">
+ Before using any <span class="application"><strong>RPM</strong></span> packages, you must know where to find them and be able to verify if you can trust them.
+ </div><div class="section" id="s2-rpm-finding"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">A.3.1. Finding RPM Packages</h3></div></div></div><a id="idm261721620896" class="indexterm"></a><a id="idm261721619488" class="indexterm"></a><div class="para">
+ Although there are many <span class="application"><strong>RPM</strong></span> repositories on the Internet, for security and compatibility reasons, you should consider installing only official Fedora-provided RPM packages. The following is a list of sources for <span class="application"><strong>RPM</strong></span> packages:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <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
+ <a id="idm261721615536" class="indexterm"></a>
+ <a id="idm261735305600" class="indexterm"></a>
+ Official Fedora installation media.
</div></li><li class="listitem"><div class="para">
- <code class="computeroutput">U</code> — user
+ <a id="idm261735303264" class="indexterm"></a>
+ <a id="idm261735301856" class="indexterm"></a>
+ Official <span class="application"><strong>RPM</strong></span> repositories provided with the <span class="application"><strong>Yum</strong></span> package manager. See <a class="xref" href="#ch-yum">Chapter 5, <em>Yum</em></a> for details on how to use the official Fedora package repositories.
</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 class="section" id="s1-check-rpm-sig"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.3. Checking a Package's Signature</h2></div></div></div><a id="idm225413402960" class="indexterm"></a><div class="para">
- To verify that a package has not been corrupted or tampered with, examine the checksum by typing the following command at a 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">
- If the message <code class="computeroutput"><em class="replaceable"><code><rpm_file></code></em>: sha1 md5 OK</code> (specifically the <code class="computeroutput">OK</code> part of it) is displayed, 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="idm225457902544" class="indexterm"></a><a id="idm225457901104" class="indexterm"></a><a id="idm225445169536" 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">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">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.org/en/keys</a>.
- </div></div></div><div class="section" id="s1-rpm-impressing"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.4. Practical and Common Examples of RPM Usage</h2></div></div></div><a id="idm225458291856" class="indexterm"></a><a id="idm225474664528" 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.
+ Unofficial, third-party repositories not affiliated with The Fedora Project also provide RPM packages.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When considering third-party repositories for use with your Fedora system, pay close attention to the repository's web site with regard to package compatibility before adding the repository as a package source. Alternate package repositories may offer different, incompatible versions of the same software, including packages already included in the Fedora repositories.
+ </div></div></div></li></ul></div></div><div class="section" id="s1-check-rpm-sig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">A.3.2. Checking Package Signatures</h3></div></div></div><a id="idm261785222368" class="indexterm"></a><a id="idm261746192032" class="indexterm"></a><a id="idm261746190624" class="indexterm"></a><div class="para">
+ <span class="application"><strong>RPM</strong></span> packages can be signed using <span class="application"><strong>GNU Privacy Guard</strong></span> (or <span class="application"><strong>GPG</strong></span>), which helps you make certain that downloaded packages are trustworthy. <span class="application"><strong>GPG</strong></span> is a tool for secure communication. With <span class="application"><strong>GPG</strong></span>, you can authenticate the validity of documents and encrypt or decrypt data.
+ </div><div class="para">
+ To verify that a package has not been corrupted or tampered with, check its <span class="application"><strong>GPG</strong></span> signature by using the <code class="command">rpmkeys</code> command with the <code class="option">-K</code> (or <code class="option">--checksig</code>) option:
+ </div><pre class="synopsis"><code class="command">rpmkeys -K <em class="replaceable"><code>package.rpm</code></em></code></pre><div class="para">
+ Note that the <span class="application"><strong>Yum</strong></span> package manager performs automatic checking of <span class="application"><strong>GPG</strong></span> signatures during installations and upgrades.
+ </div><div class="para">
+ <span class="application"><strong>GPG</strong></span> is installed by default, as well as a set of Red Hat keys for verifying packages. To import additional keys for use with <span class="application"><strong>RPM</strong></span>, see <a class="xref" href="#s2-keys-importing">Section A.3.2.1, “Importing GPG Keys”</a>.
+ </div><div class="section" id="s2-keys-importing"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">A.3.2.1. Importing GPG Keys</h4></div></div></div><div class="para">
+ To verify Red Hat packages, a Red Hat <span class="application"><strong>GPG</strong></span> key needs to be installed. A set of basic keys is installed by default. To view a list of installed keys, execute the following command at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">rpm -qa gpg-pubkey*</code></pre><div class="para">
+ To display details about a specific key, use <code class="command">rpm -qi</code> followed by the output from the previous command. For example:
+ </div><pre class="screen">~]$ <code class="command">rpm -qi gpg-pubkey-fd431d51-4ae0493b</code></pre><div class="para">
+ Use the <code class="command">rpmkeys</code> command with the <code class="option">--import</code> option to install a new key for use with <span class="application"><strong>RPM</strong></span>. The default location for storing <span class="application"><strong>RPM</strong></span> <acronym class="acronym">GPG</acronym> keys is the <code class="filename">/etc/pki/rpm-gpg/</code> directory. To import new keys, use a command like the following as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">rpmkeys --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release</code></pre><div class="para">
+ See the <a href="https://access.redhat.com/security/team/key/">Product Signing (GPG) Keys</a> article on the Red Hat Customer Portal for additional information about Red Hat package-signing practices.
+ </div></div></div></div><div class="section" id="s1-rpm-usage-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.4. Common Examples of RPM Usage</h2></div></div></div><a id="idm261692680320" class="indexterm"></a><a id="idm261692678880" class="indexterm"></a><div class="para">
+ <span class="application"><strong>RPM</strong></span> is a useful tool for both managing your system and diagnosing and fixing problems. See the following examples for an overview of some of the most-used options.
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- 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="idm225460949488" class="indexterm"></a><a id="idm225460948080" 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.
+ To verify your entire system and see what files are missing, issue the following command as <code class="systemitem">root</code>:
+ </div><a id="idm261707940368" class="indexterm"></a><a id="idm261707938960" class="indexterm"></a><pre class="synopsis"><code class="command">rpm -Va</code></pre><div class="para">
+ If some files are missing or appear corrupted, consider reinstalling relevant packages.
</div></li><li class="listitem"><div class="para">
- At some point, you might see a file that you do not recognize. To find out which package owns it, enter:
- </div><a id="idm225499900080" class="indexterm"></a><a id="idm225499898672" 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.fc21.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.
+ To determine which package owns a file, enter:
+ </div><a id="idm261735778928" class="indexterm"></a><a id="idm261735777520" class="indexterm"></a><pre class="synopsis"><code class="command">rpm -qf <em class="replaceable"><code>file</code></em></code></pre></li><li class="listitem"><div class="para">
+ To verify the package that owns a particular file, enter as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code class="command">rpm -Vf <em class="replaceable"><code>file</code></em></code></pre></li><li class="listitem"><div class="para">
+ To locate documentation files that are a part of a package to which a file belongs, enter:
+ </div><a id="idm261744293536" class="indexterm"></a><a id="idm261744292096" class="indexterm"></a><a id="idm261744290688" class="indexterm"></a><pre class="synopsis"><code class="command">rpm -qdf <em class="replaceable"><code>file</code></em></code></pre></li><li class="listitem"><div class="para">
+ To find information about a (non-installed) package file, use the following command:
+ </div><a id="idm261745899280" class="indexterm"></a><a id="idm261745897872" class="indexterm"></a><pre class="synopsis"><code class="command">rpm -qip <em class="replaceable"><code>package.rpm</code></em></code></pre></li><li class="listitem"><div class="para">
+ To list files contained in a package, use:
+ </div><a id="idm261777126608" class="indexterm"></a><a id="idm261777125168" class="indexterm"></a><pre class="synopsis"><code class="command">rpm -qlp <em class="replaceable"><code>package.rpm</code></em></code></pre></li></ul></div><div class="para">
+ See the <span class="citerefentry"><span class="refentrytitle">rpm</span>(8)</span> manual page for more options.
+ </div></div><div class="section" id="s1-rpm-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.5. Additional Resources</h2></div></div></div><a id="idm261741221504" class="indexterm"></a><div class="para">
+ <span class="application"><strong>RPM</strong></span> is a complex utility with many options and methods for querying, installing, upgrading, and removing packages. See the following resources to learn more about <span class="application"><strong>RPM</strong></span>.
+ </div><h3 id="brid-rpm-resources-installed">Installed Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">rpm --help</code> — This command displays a quick reference of <span class="application"><strong>RPM</strong></span> parameters.
</div></li><li class="listitem"><div class="para">
- 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="idm225449658880" class="indexterm"></a><a id="idm225449657440" class="indexterm"></a><a id="idm225449656032" 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-ng/BUGS
-/usr/share/doc/procps-ng/FAQ
-/usr/share/doc/procps-ng/NEWS
-/usr/share/doc/procps-ng/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="idm225468329440" class="indexterm"></a><a id="idm225468328032" class="indexterm"></a><pre class="screen">
-<code class="command">rpm -qip crontabs-1.10-31.fc21.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="idm225467640304" class="indexterm"></a><a id="idm225467638864" class="indexterm"></a><pre class="screen">
-<code class="command">rpm -qlp crontabs-1.10-31.fc21.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">A.5. Additional Resources</h2></div></div></div><a id="idm225463755888" class="indexterm"></a><div class="para">
- RPM is an extremely complex utility with many options and methods for querying, installing, upgrading, and removing packages. See 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">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">A.5.2. Useful Websites</h3></div></div></div><div class="itemizedlist"><a id="idm225478376832" class="indexterm"></a><ul><li class="listitem"><div class="para">
- The RPM website — <a href="http://www.rpm.org/">http://www.rpm.org/</a>
- </div></li><li class="listitem"><div class="para">
- The RPM mailing list can be subscribed to, and its archives read from, here — <a href="http://www.redhat.com/mailman/listinfo/rpm-list/">https://lists.rpm.org/mailman/listinfo/rpm-list</a>
- </div></li></ul></div></div><div class="section" id="s2-rpm-related-books"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">A.5.3. Related Books</h3></div></div></div><a id="idm225447672816" class="indexterm"></a><a id="idm225447671376" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <em class="citetitle">Maximum RPM</em> — <a href="http://www.rpm.org/max-rpm/">http://www.rpm.org/max-rpm/</a> </span></dt><dd><div class="para">
- The <em class="citetitle">Maximum RPM</em> book, which you can read online, covers everything from general RPM usage to building your own RPMs to programming with rpmlib.
- </div></dd><dt class="varlistentry"><span class="term"> <em class="citetitle">Fedora RPM Guide</em> — <a href="http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html">http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/RPM_Guide/index.html</a> </span></dt><dd><div class="para">
- The <em class="citetitle">Fedora RPM Guide</em> by Eric Foster-Johnson is an excellent resource on all details of the RPM package format and the RPM package management utility.
- </div></dd></dl></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 summary="Revision History"><tr><th align="left" valign="top" colspan="3"><strong>Revision History</strong></th></tr><tr><td align="left">Revision 1-2</td><td align="left">Tue Dec 9 2014</td><td align="left"><span class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></span></td></tr><tr><td align="left" colspan="3">
+ <span class="citerefentry"><span class="refentrytitle">rpm</span>(8)</span> — The <span class="application"><strong>RPM</strong></span> manual page offers an overview of all available <span class="application"><strong>RPM</strong></span> parameters.
+ </div></li></ul></div><h3 id="brid-rpm-resources-online">Online Documentation</h3><div class="itemizedlist"><a id="idm261729556512" class="indexterm"></a><a id="idm261729555072" class="indexterm"></a><ul><li class="listitem"><div class="para">
+ The <span class="application"><strong>RPM</strong></span> website — <a href="http://www.rpm.org/">http://www.rpm.org/</a>
+ </div></li><li class="listitem"><div class="para">
+ The <span class="application"><strong>RPM</strong></span> mailing list — <a href="http://lists.rpm.org/mailman/listinfo/rpm-list">http://lists.rpm.org/mailman/listinfo/rpm-list</a>
+ </div></li></ul></div><h3 id="brid-rpm-resources-also">See Also</h3><div class="itemizedlist"><a id="idm261776985440" class="indexterm"></a><ul><li class="listitem"><div class="para">
+ <a class="xref" href="#ch-yum">Chapter 5, <em>Yum</em></a> describes how to use the <span class="application"><strong>Yum</strong></span> package manager to search, install, update, and uninstall packages on the command line.
+ </div></li></ul></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 summary="Revision History"><tr><th align="left" valign="top" colspan="3"><strong>Revision History</strong></th></tr><tr><td align="left">Revision 1-2.1</td><td align="left">Wed Mar 4 2015</td><td align="left"><span class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td>Added "Working with the GRUB 2 Boot Loader" chapter.</td></tr></table>
+
+ </td></tr><tr><td align="left">Revision 1-2</td><td align="left">Tue Dec 9 2014</td><td align="left"><span class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></span></td></tr><tr><td align="left" colspan="3">
<table border="0" summary="Simple list" class="simplelist"><tr><td>Fedora 21 release of the <em class="citetitle">System Administrator's Guide</em>.</td></tr></table>
</td></tr><tr><td align="left">Revision 1-1</td><td align="left">Thu Aug 9 2012</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">
@@ -10789,4 +12561,4 @@ your system.</pre></li><li class="listitem"><div class="para">
</td></tr></table></div>
- </div></div><div class="index" id="idm225402575664"><div class="titlepage"><div><div><h1 class="title">Index</h1></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 Configura
tion</a></dt><dt> /dev/oprofile/ , <a class="indexterm" href="#s1-oprofile-dev-oprofile">Understanding /dev/oprofile/ </a></dt><dt>/dev/shm, <a class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</a></dt><dt>/run, <a class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</a></dt><dt>/sys/fs/cgroup, <a class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</a></dt><dt> /var/spool/anacron , <a class="indexterm" href="#s2-configuring-anacron-jobs">Configuring Anacron Jobs</a></dt><dt> /var/spool/cron , <a class="indexterm" href="#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt></dl></div><div class="indexdiv"><h3></h3><dl><dt> (see OProfile)</dt></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>adding</dt><dd><dl><dt>group, <a class="indexterm" href="#s2-users-tools-groups-add">Adding a New Group</a></dt><dt>user, <a class="indexterm" href="#s2-users-tools-users-add">Adding a New User</a></dt></dl></dd><dt>anacro
n, <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>installable documentation, <a class="indexterm" href="#s2-apache-resources">Additional Resources</a></dt><dt>installed documentation, <a class="indexterm" href="#s2-apache-resources">Additional Resources</a></dt><dt>useful websites, <a class="indexterm" href="#s2-apache-resources">Additional Resources</a></dt></dl></dd><dt>checking configuration, <a class="indexterm" href="#s2-apache-editing">Editing the Configuration Files</a></dt><dt>checking status, <a class="i
ndexterm" href="#s3-apache-running-status">Verifying 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">Common 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 cl
ass="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">Co
mmon 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-directives">Common httpd.conf Directives</a></dt><dt>ErrorDocument, <a class="indexterm" h
ref="#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" href="#s3-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>Keep
Alive, <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 Dir
ectives</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-di
rectives">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 Directives</a></dt><dt>/var/www/cgi-bin/, <a class="indexterm" href="#s3-apache-httpdcon
f-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 class="indexterm" href="#s2-apache-editing">Editing the Configuration Files</a>, <a c
lass="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_rewrite, <a class="indexterm" href="#s3-apache-httpdconf-directives">Commo
n 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">Restarting 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-ap
ache-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.4</dt><dd><dl><dt>changes, <a class="indexterm" href="#s2-apache-changes">Notable Changes</a></dt><dt>updating from version 2.2, <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="indexte
rm" href="#s1-autotasks-additional-resources">Additional Resources</a></dt></dl></dd><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-autotasks-additional-resources">Additional Resources</a></dt></dl></dd><dt>blkid, <a class="indexterm" href="#s2-sysinfo-filesystems-blkid">Using the blkid Command</a></dt><dt>boot loader</dt><dd><dl><dt>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-tools-password-aging">Enabling Password Aging</a></dt></dl></dd><dt>Configuration File Changes, <a class="indexterm" href="#sec-Preserving_Configuration_File_Changes">Preserving Configuration File Changes</a></dt><dt>CPU usage, <a class="indexterm" href="#s1-sysinfo-cpu">Viewing CPU Usage</a></dt><dt>cron, <a class="indexterm" href="#s1-autotasks-cron-anacron">Cron 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><dt>CUPS (see Printer C
onfiguration)</dt></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>df, <a class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</a></dt><dt>directory server (see OpenLDAP)</dt><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>drivers (see kernel module)</dt><dt>du, <a class="indexterm" href="#s2-sysinfo-filesystems-du">Using the du Command</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>ECDSA keys</dt><dd><dl><dt>generating, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><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>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" href="#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 Filters</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>expiration of password, forcing, <a class="indexterm" href="#s2-users-tools-password-aging">Enabling Password Aging</a></dt></dl></div><div class="ind
exdiv"><h3>F</h3><dl><dt> Fedora Hat RPM Guide , <a class="indexterm" href="#s2-rpm-related-books">Related Books</a></dt><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="#idm225449959504">We Need 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 Options</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 systems, <a class="indexterm" href="#s1-sysinfo-filesystems">Viewing Block Devices and File Systems</a></dt><dt>findmnt, <a class="indexterm" href="#s2-sysinfo-filesystems-findmnt">Using the findmnt Command</a></dt><dt>findsmb, <a class="indexterm" href="#s3-samba-connect-share-cmdline">Command Line</a></dt><dt> findsmb program, <a class="indexterm" href="#s2-samba-programs">Samba Distribution Programs</a></dt><dt>free, <a class="indexterm" href="#s2-sysinfo-memory-usage-
free">Using the free Command</a></dt><dt>FTP, <a class="indexterm" href="#s1-FTP">FTP</a></dt><dd><dl><dt>(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></dl></div><div class=
"indexdiv"><h3>G</h3><dl><dt> gnome-system-log (see Log File Viewer )</dt><dt>gnome-system-monitor, <a class="indexterm" href="#s2-sysinfo-system-processes-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="#s2-sysinfo-memory-usage-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="#s2-sysinfo-cpu-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="#s2-sysinfo-filesystems-system_monitor">Using the System Monitor Tool</a></dt><dt>GnuPG</dt><dd><dl><dt>checking RPM package signatures, <a class="indexterm" href="#s1-check-rpm-sig">Checking a Package's Signature</a></dt></dl></dd><dt>group configuration</dt><dd><dl><dt>groupadd, <a class="indexterm" href="#s2-users-tools-groups-add">Adding a New Group</a></dt><dt>viewing list of groups, <a class="indexterm" href="#s1-users-configui">Using the User Manager Tool</a></dt></dl></dd><dt>groups (see group configuration)</dt><dd><dl><dt>additional resourc
es, <a class="indexterm" href="#s1-users-groups-additional-resources">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#s1-users-groups-additional-resources">Additional Resources</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-tools-groups-directories">Creating Group Directories</a></dt><dt>tools for management of</dt><dd><dl><dt>groupadd, <a class="indexterm" href="#s2-users-groups-private-groups">User Private Groups</a>, <a class="indexterm" href="#s1-users-tools">Using Command Line Tools</a></dt><dt>system-config-users, <a class="indexterm" href="#s2-users-groups-private-groups">User Private Groups</a></dt><dt>User Manager, <a class="indexterm" href="#s1-users-tools">Using Command Line Tools<
/a></dt></dl></dd><dt>user private, <a class="indexterm" href="#s2-users-groups-private-groups">User Private Groups</a></dt></dl></dd><dt>GRUB 2 boot loader</dt><dd><dl><dt>configuration file, <a class="indexterm" href="#s3-kernel-boot-loader-grub">Configuring the GRUB 2 Boot Loader</a></dt><dt>configuring, <a class="indexterm" href="#s3-kernel-boot-loader-grub">Configuring the GRUB 2 Boot Loader</a></dt></dl></dd><dt>GUI, <a class="indexterm" href="#ch-Opening_GUI_Applications">Opening Graphical Applications</a></dt></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>hardware</dt><dd><dl><dt>viewing, <a class="indexterm" href="#s1-sysinfo-hardware">Viewing Hardware Information</a></dt></dl></dd><dt>HTTP server (see Apache HTTP Server)</dt><dt>httpd (see Apache HTTP Server)</dt></dl></div><div class="indexdiv"><h3>I</h3><dl><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>i
nitial 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 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>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-Man
ually_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_Upgrading_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 U
pgrade</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 Upgrading the Kernel</a></dt></dl></dd><dt>kernel module</dt><dd><dl><dt>definition, <a class="indexterm" href="#ch-Working_with_Kernel_Modules">Working with Kernel Modules</a></dt><dt>directories</dt><dd><dl><dt>/etc/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>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-Lo
aded 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>supplying, <a class="indexterm" href="#sec-Setting_Module_Parameters">Setting Module Parameters</a></dt></dl></dd><dt>unloading, <a class="indexterm" href="#sec-Unloading_a_Module">Unloading a Module</a></dt><dt>utilities</dt><dd><dl><dt>insmod, <a class="indexterm" href="#sec-Loading_a_Module">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">Dis
playing 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-firmw
are</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, <a class="indexterm" href="#ch-System_Locale_and_Keyboard_Configuration">System Locale and Keyboard Configuration</a></dt><dd><dl><dt>layout, <a class="indexterm" href="#s1-Changing_the_Keyboard_Layout">Changing the Keyboard Layout</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>L</h3><dl><dt>LDAP (see OpenLDAP)</dt><dt>localectl (see keyboard configuration)</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-logfile
s-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="indexterm" 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>lsblk, <a class="indexterm" href="#s2-sysinfo-filesystems-lsblk">Using the lsblk Command</a></dt><dt>lscpu, <a class="indexterm" href="#s2-sysinfo-hardware-lscpu">Using the lscpu Command</a></dt><dt>lsmod, <a class="indexterm" href="#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded Modules</a></dt><dd><dl><dt>(see also kernel module)</dt></dl></dd><dt>lspci, <a class="indexterm" href="#s2-sysinfo-hardware-lspci">Using the lspci Command</a></dt><dt>lspcmcia, <a class="indexterm" href="#s2-sysinfo-hardware-lspcmcia">Using the lspcmcia Command<
/a></dt><dt>lsusb, <a class="indexterm" href="#s2-sysinfo-hardware-lsusb">Using the lsusb Command</a></dt></dl></div><div class="indexdiv"><h3>M</h3><dl><dt>Mail 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">Viewing 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></dl></div><div class="indexdiv"><h3>N</h3><dl><dt> net program, <a class="indexterm" href="#s2-samba-programs">Samba Distribution Programs</a></dt><dt> nmblookup program, <a class="indexterm" href="#s2-samba-programs">Samba Distribution Programs</a></dt></dl></div><div class="indexdiv"><h3>O</h3><dl><dt> opannotate (see OProfile)</dt><dt> opcontrol (see OProfile)</dt><dt>OpenLDAP</dt><dd><dl><dt
>checking status, <a class="indexterm" href="#s3-ldap-running-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 Configurati
on</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>install
ation, <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="#s
3-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>ECDSA keys</dt><dd><dl><dt>generating, <a class=
"indexterm" href="#s3-ssh-configuration-keypairs-generating">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>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-agent, <a class="indexterm" href="#s3-ssh-configuration-keypairs-agent">Configuring ssh-agent</a></dt><dt>ssh-keygen</dt><dd><dl><dt>ECDSA, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt><dt>RSA, <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 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> ophelp , <a class="indexterm" href="#s2-oprofile-events">Setting Events to Monitor</a></dt><dt> opreport (see OProfile)</dt><dt>OProfile, <a class="indexterm" href="#ch-OProfile">OProfile</a></dt><dd><dl><dt> /dev/oprofile/ , <a class="indexterm" href="#s1-oprofile-dev-oprofile">Understanding /dev/oprofile/ </a></dt><dt>additional resources, <a class="indexterm" href="#s1-oprofile-additional-resources">Additional Resources</a></dt><dt>configuring, <a class="indexterm" href="#s1-oprofile-configuring">Configuring OProfile</a></dt><dd><dl><dt>separating profiles, <a class="indexterm" href="#s2-oprofile-starting-separate">Separating Kernel and User-space Profiles</a></dt></dl></dd><dt>e
vents</dt><dd><dl><dt>sampling rate, <a class="indexterm" href="#s3-oprofile-events-sampling">Sampling Rate</a></dt><dt>setting, <a class="indexterm" href="#s2-oprofile-events">Setting Events to Monitor</a></dt></dl></dd><dt>Java, <a class="indexterm" href="#s1-oprofile-java-support">OProfile Support for Java</a></dt><dt>monitoring the kernel, <a class="indexterm" href="#s2-oprofile-kernel">Specifying the Kernel</a></dt><dt> opannotate , <a class="indexterm" href="#s2-oprofile-reading-opannotate">Using opannotate </a></dt><dt> opcontrol , <a class="indexterm" href="#s1-oprofile-configuring">Configuring OProfile</a></dt><dd><dl><dt> --no-vmlinux , <a class="indexterm" href="#s2-oprofile-kernel">Specifying the Kernel</a></dt><dt> --start , <a class="indexterm" href="#s1-oprofile-starting">Starting and Stopping OProfile</a></dt><dt> --vmlinux= , <a class="indexterm" href="#s2-oprofile-kernel">Specifying the Kernel</a></dt></dl></dd><dt> ophelp , <a class="indexterm" href="#s2-o
profile-events">Setting Events to Monitor</a></dt><dt> opreport , <a class="indexterm" href="#s2-oprofile-reading-opreport">Using opreport </a>, <a class="indexterm" href="#s2-oprofile-module-output">Getting more detailed output on the modules</a></dt><dd><dl><dt>on a single executable, <a class="indexterm" href="#s2-oprofile-reading-opreport-single">Using opreport on a Single Executable</a></dt></dl></dd><dt> oprofiled , <a class="indexterm" href="#s1-oprofile-starting">Starting and Stopping OProfile</a></dt><dd><dl><dt>log file, <a class="indexterm" href="#s1-oprofile-starting">Starting and Stopping OProfile</a></dt></dl></dd><dt>overview of tools, <a class="indexterm" href="#s1-oprofile-overview-tools">Overview of Tools</a></dt><dt>reading data, <a class="indexterm" href="#s1-oprofile-analyzing-data">Analyzing the Data</a></dt><dt>saving data, <a class="indexterm" href="#s1-oprofile-saving-data">Saving Data</a></dt><dt>starting, <a class="indexterm" href="#s1-oprofile-sta
rting">Starting and Stopping OProfile</a></dt><dt>SystemTap, <a class="indexterm" href="#s1-oprofile-and-systemtap">OProfile and SystemTap</a></dt><dt>unit mask, <a class="indexterm" href="#s3-oprofile-events-unit-masks">Unit Masks</a></dt></dl></dd><dt> oprofiled (see OProfile)</dt><dt> oprof_start , <a class="indexterm" href="#s1-oprofile-gui">Graphical Interface</a></dt><dt>OS/400 boot loader</dt><dd><dl><dt>configuration file, <a class="indexterm" href="#s2-kernel-boot-loader-iseries">Configuring the OS/400 Boot Loader</a></dt><dt>configuring, <a class="indexterm" href="#s2-kernel-boot-loader-iseries">Configuring the OS/400 Boot Loader</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>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>packages</dt><dd><dl><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</dt><dd><dl><dt>yum info, <a class="indexterm" href="#sec-Displaying_Package_Information">Displaying Package Information</a></dt></dl></dd><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>Fedora installation media, <a class="indexterm" href="#s2-rpm-finding">Finding RPM Packages</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>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-Inst
alling">Installing Packages</a></dt><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 Pa
ckages</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 grouplist, <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>obtaining list of files, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Us
age</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>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 d
ependencies, <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 for packages with Yum</dt><dd><dl><dt>yum search, <a class="indexterm" href="#sec-Searching_Packages">Searching Packages</a></dt></dl></dd><dt>searching packages with Yum</dt><d
d><dl><dt>yum search, <a class="indexterm" href="#sec-Searching_Packages">Searching Packages</a></dt></dl></dd><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>upgrading RPM, <a class="indexterm" href="#sec-Installing_and_Upgrading">Installing and Upgrading</a></dt><dt>Yum instead of RPM, <a class="indexterm" href="#ch-RPM">RPM</a></dt></dl></dd><dt>partx, <a class="indexterm" href="#s2-sysinfo-filesystems-partx">Using the partx Command</a></dt><dt>password</dt><dd><dl><dt>aging, <a class="indexterm" href="#s2-users-tools-password-aging">Enabling Password Aging</a></dt><dt>expire, <a class="indexterm" href="#s2-users-tools-password-aging">Enabling Password Aging</a></dt></dl></dd><dt>passwords</dt><dd><dl><dt>shadow, <a class="indexterm" href="#s2-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>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>Printer Configuration</dt><dd><dl><dt>CUPS, <a class="indexterm" href="#sec-Printer_Configuration">Printer Configuration</a></dt><dt>IPP Printers, <a class="indexterm" href="#s1-printing-ipp-printer">Adding an IPP Printer</a></dt><dt>LDP/LPR Printers, <a class="indexterm" href="#sec-printing-LPDLPR-printer">Adding an LPD/LPR Host or Printer</a></dt><dt>Local Printers, <a class="indexterm" href="#sec-Adding_Other_Printer">Adding a Local Printer</a></dt><dt>New Printer, <a class="indexterm" href="#sec-Setting_Printer">Starting Printer
Setup</a></dt><dt>Print Jobs, <a class="indexterm" href="#s1-printing-managing">Managing Print Jobs</a></dt><dt>Samba Printers, <a class="indexterm" href="#s1-printing-smb-printer">Adding a Samba (SMB) printer</a></dt><dt>Settings, <a class="indexterm" href="#idm225437009232">The Settings Page</a></dt><dt>Sharing Printers, <a class="indexterm" href="#sec-Sharing_Printers">Sharing Printers</a></dt></dl></dd><dt>printers (see Printer Configuration)</dt><dt>processes, <a class="indexterm" href="#s1-sysinfo-system-processes">Viewing 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" href="#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>deliv
ering, <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="indexterm" href="#s3-email-procmail-recipes-special">Special Conditions and Actions</a></dt></dl></dd></dl></dd><dt>ps, <a class="indexterm" href="#s2-sysinfo-system-processes-ps">Using
the ps Command</a></dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>RAM, <a class="indexterm" href="#s1-sysinfo-memory-usage">Viewing Memory Usage</a></dt><dt>rcp, <a class="indexterm" href="#s2-ssh-clients-scp">Using the scp Utility</a></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> 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="indexter
m" 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">Prac
tical and Common Examples of RPM Usage</a></dt><dt>documentation with, <a class="indexterm" href="#s1-rpm-impressing">Practical and Common Examples of RPM Usage</a></dt><dt>failed dependencies, <a class="indexterm" href="#s3-rpm-unresolved-dependency">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></dt><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> 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 Information Database
s</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-services">Samba Da
emons</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> smbs
pool , <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>Samba Printers, <a class="indexterm" href="#s1-printing-smb-printer">Adding a Samba (SMB) printer</a></dt><dt>Security Modes, <a class="indexterm" href="#s2-samba-security-modes">Samba 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 Security 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">Starti
ng and Stopping Samba</a></dt><dt>reloading, <a class="indexterm" href="#s2-samba-startstop">Starting 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 Server 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> security plug-in (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-chan
ges">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="#s2-users-groups-shadow-utilities">Shadow Passwords</a></dt></dl></dd><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><dt> 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><d
t>connection 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-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>stunnel, <a class="indexterm" href="#s3-email-security-servers">Securing Email Client Communications</a></dt><dt>system analysis</dt><dd><dl><dt>OProfile (see OProfile)</dt></dl></dd><dt>system information</dt><dd><dl><dt>cpu usage, <a class="indexterm" href="#s1-sysinfo-cpu">Viewing CPU Usage</a></dt><dt>file systems, <a class="indexterm" href="#s1-sysinfo-filesystems">Viewing Block Devices and File Systems</a></dt><dd><dl><dt>/dev/shm, <a class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</a></dt><dt>/run, <a
class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</a></dt><dt>/sys/fs/cgroup, <a class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</a></dt></dl></dd><dt>gathering, <a class="indexterm" href="#ch-System_Monitoring_Tools">System Monitoring Tools</a></dt><dt>hardware, <a class="indexterm" href="#s1-sysinfo-hardware">Viewing Hardware Information</a></dt><dt>memory usage, <a class="indexterm" href="#s1-sysinfo-memory-usage">Viewing Memory Usage</a></dt><dt>processes, <a class="indexterm" href="#s1-sysinfo-system-processes">Viewing System Processes</a></dt><dd><dl><dt>currently running, <a class="indexterm" href="#s2-sysinfo-system-processes-top">Using the top Command</a></dt></dl></dd></dl></dd><dt>System Monitor, <a class="indexterm" href="#s2-sysinfo-system-processes-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="#s2-sysinfo-memory-usage-system_monitor">Using the System Monitor Tool</a>, <a class="ind
exterm" href="#s2-sysinfo-cpu-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="#s2-sysinfo-filesystems-system_monitor">Using the System Monitor Tool</a></dt><dt>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>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>top, <a class="indexterm" href="#s2-sysinfo-system-processes-top">Using the top Command</a></dt></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>user configuration</dt><dd><dl><dt>command line configuration</dt><dd><dl><dt>chage, <a class="indexterm" href="#s2-users-tools-password-aging">Enabling Password Aging</a></dt><dt>passwd, <a class="indexterm" href="#s2-users-too
ls-users-add">Adding a New User</a></dt><dt>useradd, <a class="indexterm" href="#s2-users-tools-users-add">Adding a New User</a></dt></dl></dd><dt>password</dt><dd><dl><dt>forcing expiration of, <a class="indexterm" href="#s2-users-tools-password-aging">Enabling Password Aging</a></dt></dl></dd><dt>viewing list of users, <a class="indexterm" href="#s1-users-configui">Using the 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-tools-groups-directories">Creating Group Directories</a></dt></dl></dd><dt>useradd command</dt><dd><dl><dt>user account creation using, <a class="indexterm" href="#s2-users-tools-users-add">Adding a New User</a></dt></dl></dd><dt>users (see user configuration)</dt><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-users-groups-additional-resources">Additional Resources</a></dt><dd><dl><dt>install
ed documentation, <a class="indexterm" href="#s1-users-groups-additional-resources">Additional Resources</a></dt></dl></dd><dt>introducing, <a class="indexterm" href="#ch-Managing_Users_and_Groups">Managing Users and Groups</a></dt><dt>tools for management of</dt><dd><dl><dt>User Manager, <a class="indexterm" href="#s1-users-tools">Using Command Line Tools</a></dt><dt>useradd, <a class="indexterm" href="#s1-users-tools">Using Command Line 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 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 D
ocumentation</a></dt><dt>useful websites, <a class="indexterm" href="#s3-ftp-useful-websites">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" hre
f="#s2-ftp-vsftpd-start">Starting and Stopping vsftpd </a></dt><dt>starting multiple copies 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></dl></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 plug-ins, <a class="indexterm" href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring, and Disabling Yum Plug-ins</a></dt><dt>configuring Yum and Yum repositories, <a class="indexterm" href="#sec-Configuring_Yum_and_Yum_Repositories">Confi
guring Yum and Yum Repositories</a></dt><dt>disabling plug-ins, <a class="indexterm" href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring, and Disabling Yum Plug-ins</a></dt><dt>displaying packages</dt><dd><dl><dt>yum info, <a class="indexterm" href="#sec-Displaying_Package_Information">Displaying Package Information</a></dt></dl></dd><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 plug-ins, <a class="indexterm" href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring, and Disabling Yum Plug-ins</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="indexte
rm" 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>plug-ins</dt><dd><dl><dt>fs-snapshot, <a class="indexterm" href="#sec-Plugin_Descriptions">Plug-in Descriptions</a></dt><dt>presto, <a class="indexterm" href="#sec-Plugin_Descriptions">Plug-in Descriptions</a></dt><dt>re
fresh-packagekit, <a class="indexterm" href="#sec-Plugin_Descriptions">Plug-in Descriptions</a></dt><dt>rhnplugin, <a class="indexterm" href="#sec-Plugin_Descriptions">Plug-in Descriptions</a></dt><dt>security, <a class="indexterm" href="#sec-Plugin_Descriptions">Plug-in Descriptions</a></dt></dl></dd><dt>repository, <a class="indexterm" href="#sec-Managing_Yum_Repositories">Adding, Enabling, and Disabling a Yum Repository</a>, <a class="indexterm" href="#sec-Creating_a_Yum_Repository">Creating a Yum Repository</a></dt><dt>searching for packages with Yum</dt><dd><dl><dt>yum search, <a class="indexterm" href="#sec-Searching_Packages">Searching Packages</a></dt></dl></dd><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="index
term" 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 plug-ins, <a class="indexterm" href="#sec-Yum_Plugins">Yum Plug-ins</a></dt><dt>Yum repositories</dt><dd><dl><dt>configuring 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 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>
\ No newline at end of file
+ </div></div><div class="index" id="idm261761687520"><div class="titlepage"><div><div><h1 class="title">Index</h1></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 Configura
tion</a></dt><dt>/dev/oprofile/, <a class="indexterm" href="#s1-oprofile-dev-oprofile">Understanding the /dev/oprofile/ directory </a></dt><dt>/dev/shm, <a class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</a></dt><dt>/run, <a class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</a></dt><dt>/sys/fs/cgroup, <a class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</a></dt><dt> /var/spool/anacron , <a class="indexterm" href="#s2-configuring-anacron-jobs">Configuring Anacron Jobs</a></dt><dt> /var/spool/cron , <a class="indexterm" href="#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt></dl></div><div class="indexdiv"><h3></h3><dl><dt> (see OProfile)</dt></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>adding</dt><dd><dl><dt>group, <a class="indexterm" href="#s2-users-tools-groups-add">Adding a New Group</a></dt><dt>user, <a class="indexterm" href="#s2-users-tools-users-add">Adding a New User</a></dt></dl></d
d><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>installable documentation, <a class="indexterm" href="#s2-apache-resources">Additional Resources</a></dt><dt>installed documentation, <a class="indexterm" href="#s2-apache-resources">Additional Resources</a></dt><dt>useful websites, <a class="indexterm" href="#s2-apache-resources">Additional Resources</a></dt></dl></dd><dt>checking configuration, <a class="indexterm" href="#s2-apache-editing">Editing the Configuration Files</a></dt><dt>checking status,
<a class="indexterm" href="#s3-apache-running-status">Verifying 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">Common 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-di
rectives">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-directives">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" href="#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>ProxyR
equests, <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 ht
tpd.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 Directives</a></dt><dt>/var/www/cgi-bin/, <a class="indexterm" href="#s3-apa
che-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 class="indexterm" href="#s2-apache-editing">Editing the Configuration Fil
es</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_rewrite, <a class="indexterm" href="#s3-apache-httpdconf-direc
tives">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">Restarting 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.4</dt><dd><dl><dt>changes, <a class="indexterm" href="#s2-apache-changes">Notable Changes</a></dt><dt>updating from version 2.2, <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 cl
ass="indexterm" href="#s1-autotasks-additional-resources">Additional Resources</a></dt></dl></dd><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-autotasks-additional-resources">Additional Resources</a></dt></dl></dd><dt>blkid, <a class="indexterm" href="#s2-sysinfo-filesystems-blkid">Using the blkid Command</a></dt><dt>boot loader</dt><dd><dl><dt>GRUB 2 boot loader, <a class="indexterm" href="#ch-Working_with_the_GRUB_2_Boot_Loader">Working with the GRUB 2 Boot Loader</a></dt><dt>verifying, <a class="indexterm" href="#s1-kernel-boot-loader">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-tools-password-aging">Enabling Password Aging</a></dt></dl></dd><dt>Configuration File Changes, <a class="indexterm" href="#sec-Preserving_Configuration_File_Changes">Preserving Configuration File Changes</a></dt><dt>CPU usage, <a class="indexterm" href="#s1-sysinfo-cpu">Viewing CPU Usage</a></dt><dt>cron, <a class="indexterm" href="#s1-autotasks-cron-anacron">Cron 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 Cr
on Jobs</a></dt></dl></dd><dt> crontab , <a class="indexterm" href="#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt><dt>CUPS (see Printer Configuration)</dt></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>df, <a class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</a></dt><dt>directory server (see OpenLDAP)</dt><dt>documentation</dt><dd><dl><dt>finding installed, <a class="indexterm" href="#s1-rpm-usage-examples">Common Examples of RPM Usage</a></dt></dl></dd><dt>drivers (see kernel module)</dt><dt>du, <a class="indexterm" href="#s2-sysinfo-filesystems-du">Using the du Command</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>ECDSA keys</dt><dd><dl><dt>generating, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><dt>email</dt><dd><dl><dt>additional resources, <a class="indexterm" href="#s1-email-additional-resources">Additional Resources</a></dt><dd><dl><dt>installed document
ation, <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>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" href="#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 Filters</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>expiration o
f password, forcing, <a class="indexterm" href="#s2-users-tools-password-aging">Enabling Password Aging</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="#idm261712903024">We Need 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 Options</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 systems, <a class="indexterm" href="#s1-sysinfo-filesystems">Viewing Block Devices and File Systems</a></dt><dt>findmnt, <a class="indexterm" href="#s2-sysinfo-filesystems-findmnt">Using the findmnt Command</a></dt><dt>findsmb, <a class="indexterm" href="#s3-samba-connect-share-cmdline">Command Line</a></dt><dt> findsmb program, <a class="indexterm" href="#s2-samba-programs">Samba Distribution Programs</a></dt><dt>free, <a class="inde
xterm" href="#s2-sysinfo-memory-usage-free">Using the free Command</a></dt><dt>FTP, <a class="indexterm" href="#s1-FTP">FTP</a></dt><dd><dl><dt>(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></dl></div><div class="indexdiv"><h3>G</h3><dl><dt>gnome-system-log (see System Log)</dt><dt>gnome-system-monitor, <a class="indexterm" href="#s2-sysinfo-system-processes-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="#s2-sysinfo-memory-usage-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="#s2-sysinfo-cpu-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="#s2-sysinfo-filesystems-system_monitor">Using the System Monitor Tool</a></dt><dt>GnuPG</dt><dd><dl><dt>checking RPM package signatures, <a class="indexterm" href="#s1-check-rpm-sig">Checking Package Signatures</a></dt></dl></dd><dt>group configuration</dt><dd><dl><dt>groupadd, <a class="indexterm" href="#s2-users-tools-groups-add">Adding a New Group</a></dt><dt>viewing list of groups, <a class="indexterm" href="#s1-users-configui">Managing Users in a Graphical Environment</a></dt></dl></dd><dt>groups (see group configura
tion)</dt><dd><dl><dt>additional resources, <a class="indexterm" href="#sect-Users_and_Groups-Resources">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#sect-Users_and_Groups-Resources">Additional Resources</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-tools-groups-directories">Creating Group Directories</a></dt><dt>tools for management of</dt><dd><dl><dt>groupadd, <a class="indexterm" href="#s2-users-groups-private-groups">User Private Groups</a>, <a class="indexterm" href="#s1-users-tools">Using Command Line Tools</a></dt></dl></dd><dt>user private, <a class="indexterm" href="#s2-users-groups-private-groups">User Private Groups</a></dt></dl></dd><dt>GRUB 2</dt><dd><dl><dt>configuring GRUB
2, <a class="indexterm" href="#ch-Working_with_the_GRUB_2_Boot_Loader">Working with the GRUB 2 Boot Loader</a></dt><dt>customizing GRUB 2, <a class="indexterm" href="#ch-Working_with_the_GRUB_2_Boot_Loader">Working with the GRUB 2 Boot Loader</a></dt><dt>reinstalling GRUB 2, <a class="indexterm" href="#ch-Working_with_the_GRUB_2_Boot_Loader">Working with the GRUB 2 Boot Loader</a></dt></dl></dd><dt>GRUB 2 boot loader</dt><dd><dl><dt>configuration file, <a class="indexterm" href="#s3-kernel-boot-loader-grub">Configuring the GRUB 2 Boot Loader</a></dt><dt>configuring, <a class="indexterm" href="#s3-kernel-boot-loader-grub">Configuring the GRUB 2 Boot Loader</a></dt></dl></dd><dt>GUI, <a class="indexterm" href="#ch-Opening_GUI_Applications">Opening Graphical Applications</a></dt></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>hardware</dt><dd><dl><dt>viewing, <a class="indexterm" href="#s1-sysinfo-hardware">Viewing Hardware Information</a></dt></dl></dd><dt>HTTP server (see
Apache HTTP Server)</dt><dt>httpd (see Apache HTTP Server)</dt></dl></div><div class="indexdiv"><h3>I</h3><dl><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 the kernel, <a class="indexterm" href="#ch-Manually_Upgrading_the_Kernel">Manually Upgrad
ing the Kernel</a></dt></dl></div><div class="indexdiv"><h3>K</h3><dl><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_Upgrading_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">Download
ing 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 Upgrading the Kernel</a></dt></dl></dd><dt>kernel module</dt><dd><dl><dt>definition, <a class="indexterm" href="#ch-Working_with_Kernel_Modules">Working with Kernel Modules</a></dt><dt>directories</dt><dd><dl><dt>/etc/modules-load.d/, <a class="indexterm" href="#sec-Persistent_Module_Loading">Persistent Module Loading</a></dt><dt> /lib/modules/kernel_version/kernel/drivers/ , <a class="indexterm" href="#sec-Loading_a_Module">Loading a Module</a></dt></dl></dd><dt>files</dt><dd><dl><dt>/proc/modul
es, <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>supplying, <a class="indexterm" href="#sec-Setting_Module_Parameters">Setting Module Parameters</a></dt></dl></dd><dt>unloading, <a class="indexterm" href="#sec-Unloading_a_Module">Unloading a Module</a></dt><dt>utilities</dt><dd><dl><dt>insmod, <a class="indexterm
" href="#sec-Loading_a_Module">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-headers</dt><dd><dl><dt>C header files f
iles, <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, <a class="indexterm" href="#ch-System_Locale_and_Keyboard_Configuration">System Locale and Keyboard Configuration</a></dt><dd><dl><dt>layout, <a class="indexterm" href="#s1-Changing_the_Keyboard_Layout">Changing the Keyboard Layout</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>L</h3><dl><dt>LDAP (see OpenLDAP)</dt><dt>localectl (see keyboard configuration)</dt><dt>log files, <a class="indexterm" href="#ch-Viewing_and_Manag
ing_Log_Files">Viewing and Managing Log Files</a></dt><dd><dl><dt>(see also System Log)</dt><dt>description, <a class="indexterm" href="#ch-Viewing_and_Managing_Log_Files">Viewing and Managing Log Files</a></dt><dt>locating, <a class="indexterm" href="#s1-logfiles-locating">Locating Log Files</a></dt><dt>monitoring, <a class="indexterm" href="#s2-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="#s2-logfiles-viewing">Viewing Log Files</a></dt></dl></dd><dt>logrotate, <a class="indexterm" href="#s1-logfiles-locating">Locating Log Files</a></dt><dt>lsblk, <a class="indexterm" href="#s2-sysinfo-filesystems-lsblk">Using the lsblk Command</a></dt><dt>lscpu, <a class="indexterm" href="#s2-sysinfo-hardware-lscpu">Using the lscpu Comm
and</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-sysinfo-hardware-lspci">Using the lspci Command</a></dt><dt>lspcmcia, <a class="indexterm" href="#s2-sysinfo-hardware-lspcmcia">Using the lspcmcia Command</a></dt><dt>lsusb, <a class="indexterm" href="#s2-sysinfo-hardware-lsusb">Using the lsusb Command</a></dt></dl></div><div class="indexdiv"><h3>M</h3><dl><dt>Mail 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-u
sage">Viewing 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></dl></div><div class="
indexdiv"><h3>N</h3><dl><dt> net program, <a class="indexterm" href="#s2-samba-programs">Samba Distribution Programs</a></dt><dt> nmblookup program, <a class="indexterm" href="#s2-samba-programs">Samba Distribution Programs</a></dt></dl></div><div class="indexdiv"><h3>O</h3><dl><dt>opannotate (see OProfile)</dt><dt>opcontrol (see OProfile)</dt><dt>OpenLDAP</dt><dd><dl><dt>backends, <a class="indexterm" href="#s3-loading_modules_or_backends">Loading Modules and Backends</a></dt><dt>checking status, <a class="indexterm" href="#s3-ldap-running-status">Verifying 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><dt>TLS, <a class="indexterm" href="#s3-establishing_a_secure_connection">Establishing a Secure Connection</a>, <a class="indexterm" href="#s3-setting_up_replication">Setting Up Replication</a>, <a class="indexterm" href="#s3-loading_modules_or_backends">Loading Modules and Backends</a></dt></dl></dd><dt>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">Chan
ging 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="indexte
rm" href="#s2-ldap-configuration">Configuring an OpenLDAP Server</a>, <a class="indexterm" href="#s3-setting_up_replication">Setting Up Replication</a>, <a class="indexterm" href="#s3-loading_modules_or_backends">Loading Modules and Backends</a></dt><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>, <a class="indexterm" href="#s3-establishing_a_secure_connection">Establishing a Secure Connection</a></dt><dt>/etc/openldap/slapd.d/cn=config.ldif, <a class="indexterm" href="#s3-ldap-configuration-global">Changing the Global Configuration</a>, <a class="indexterm" href="#s3-establishing_a_secure_connection">Establishing a Secure Connection</a></dt><dt>/etc/openldap/slapd
.d/cn=config/olcDatabase={1}bdb.ldif, <a class="indexterm" href="#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>modules, <a class="indexterm" href="#s3-loading_modules_or_backends">Loading Modules and Backends</a></dt><dt>packages, <a class="indexterm" href="#s2-ldap-installation">Installing the OpenLDAP Suite</a></dt><dt>replication, <a class="indexterm" href="#s3-setting_up_replication">Setting Up Replication</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-co
nfiguration-schema">Extending Schema</a></dt><dt>security, <a class="indexterm" href="#s3-establishing_a_secure_connection">Establishing a Secure Connection</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>ECDSA keys</dt><dd><dl><dt>generating, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">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>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 cla
ss="indexterm" href="#s2-ssh-configuration-sshd">Starting an OpenSSH Server</a></dt></dl></dd><dt>ssh-agent, <a class="indexterm" href="#s3-ssh-configuration-keypairs-agent">Configuring ssh-agent</a></dt><dt>ssh-keygen</dt><dd><dl><dt>ECDSA, <a class="indexterm" href="#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt><dt>RSA, <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 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>ophelp, <a class="indexterm" href="#s2-oprofile-events">Setting Events to Monitor</a></dt><dt>opreport (see OProfile)</dt><dt>OProfile, <a class="indexterm" href="#ch-OProfile">OProfile</a
></dt><dd><dl><dt>/dev/oprofile/, <a class="indexterm" href="#s1-oprofile-dev-oprofile">Understanding the /dev/oprofile/ directory </a></dt><dt>additional resources, <a class="indexterm" href="#s1-oprofile_additional_resources">Additional Resources</a></dt><dt>configuring, <a class="indexterm" href="#s1-oprofile-configuring">Configuring OProfile Using Legacy Mode</a></dt><dd><dl><dt>separating profiles, <a class="indexterm" href="#s2-oprofile-starting-separate">Separating Kernel and User-space Profiles</a></dt></dl></dd><dt>events</dt><dd><dl><dt>sampling rate, <a class="indexterm" href="#s3-oprofile-events-sampling">Sampling Rate</a></dt><dt>setting, <a class="indexterm" href="#s2-oprofile-events">Setting Events to Monitor</a></dt></dl></dd><dt>Java, <a class="indexterm" href="#s1-oprofile-java-support">OProfile Support for Java</a></dt><dt>monitoring the kernel, <a class="indexterm" href="#s2-oprofile-kernel">Specifying the Kernel</a></dt><dt> opannotate , <a class="indext
erm" href="#s2-oprofile-reading-opannotate">Using opannotate</a></dt><dt>opcontrol, <a class="indexterm" href="#s1-oprofile-configuring">Configuring OProfile Using Legacy Mode</a></dt><dd><dl><dt> --no-vmlinux , <a class="indexterm" href="#s2-oprofile-kernel">Specifying the Kernel</a></dt><dt> --start , <a class="indexterm" href="#s1-oprofile-starting">Starting and Stopping OProfile Using Legacy Mode</a></dt><dt>--vmlinux=, <a class="indexterm" href="#s2-oprofile-kernel">Specifying the Kernel</a></dt></dl></dd><dt> ophelp , <a class="indexterm" href="#s2-oprofile-events">Setting Events to Monitor</a></dt><dt> opreport , <a class="indexterm" href="#s2-oprofile-reading-opreport">Using opreport</a>, <a class="indexterm" href="#s2-oprofile-module-output">Getting More Detailed Output on the Modules</a></dt><dd><dl><dt>on a single executable, <a class="indexterm" href="#s2-oprofile-reading-opreport-single">Using opreport on a Single Executable</a></dt></dl></dd><dt> oprofiled , <a
class="indexterm" href="#s1-oprofile-starting">Starting and Stopping OProfile Using Legacy Mode</a></dt><dd><dl><dt>log file, <a class="indexterm" href="#s1-oprofile-starting">Starting and Stopping OProfile Using Legacy Mode</a></dt></dl></dd><dt>overview of tools, <a class="indexterm" href="#s1-oprofile-overview-tools">Overview of Tools</a></dt><dt>reading data, <a class="indexterm" href="#s1-oprofile-analyzing-data">Analyzing the Data</a></dt><dt>saving data, <a class="indexterm" href="#s1-oprofile-saving-data">Saving Data in Legacy Mode</a></dt><dt>starting, <a class="indexterm" href="#s1-oprofile-starting">Starting and Stopping OProfile Using Legacy Mode</a></dt><dt>SystemTap, <a class="indexterm" href="#s1-oprofile-and-systemtap">OProfile and SystemTap</a></dt><dt>unit mask, <a class="indexterm" href="#s3-oprofile-events-unit-masks">Unit Masks</a></dt></dl></dd><dt>oprofiled (see OProfile)</dt><dt>oprof_start, <a class="indexterm" href="#s1-oprofile-gui">Graphical Inte
rface</a></dt><dt>OS/400 boot loader</dt><dd><dl><dt>configuration file, <a class="indexterm" href="#s2-kernel-boot-loader-iseries">Configuring the OS/400 Boot Loader</a></dt><dt>configuring, <a class="indexterm" href="#s2-kernel-boot-loader-iseries">Configuring the OS/400 Boot Loader</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>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>packages</dt><dd><dl><dt>dependencies, <a class="indexterm" href="#s3-rpm-unresolved-dependency">Satisfying Unresolved Dependencies</a></dt><dt>determining file ownership with, <a class="indexterm" href="#s1-rpm-usage-examples">Common Examples of RPM Usage</a></dt><dt>displaying packages</dt><dd><dl><dt>yum info, <a class="indexterm" href="#sec-Displaying_Package_Information">Displaying Package Information</a></dt></dl></dd><dt>displaying packages with Yum</dt><dd><dl><dt>yum inf
o, <a class="indexterm" href="#sec-Displaying_Package_Information">Displaying Package Information</a></dt></dl></dd><dt>Fedora installation media, <a class="indexterm" href="#s2-rpm-finding">Finding RPM Packages</a></dt><dt>finding deleted files from, <a class="indexterm" href="#s1-rpm-usage-examples">Common Examples of RPM Usage</a></dt><dt>finding Fedora RPM packages, <a class="indexterm" href="#s2-rpm-finding">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 RPM, <a class="indexterm" href="#sec-Installing_and_Upgrading">Installing and Upgrading Packages</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-ke
rnel-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-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 grouplist, <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-usage-examples">Common Examples of RPM Usage</a></dt><dt>obtaining list of files, <a class="indexterm" href="#s1-rpm-usage-examples">Common Examples of RPM Usage</a></dt><dt>packages and package groups, <a class="indexterm" href="#sec-Packages_and_Package_Groups">Packages and Package Groups</a></dt><dt>perf</dt><dd><dl><dt>firmware files, <a class="indexterm" href="#s1-kernel-packages">Overview of Kernel Packages</a></dt></dl></dd><dt>querying uninstalled, <a class="indexterm" href="#s1-rpm-usage-examples">Common Examples of RPM Usage</a></dt><dt>removing, <a class="indexterm" href="#s2-rpm-uninstalling">Uninstalling Packages</a></dt><dt>removing package groups with Yum
, <a class="indexterm" href="#sec-Removing">Removing Packages</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">Replacing Already-Installed Packages</a></dt><dt>configuration file changes, <a class="indexterm" href="#sec-Configuration_File_Changes">Preserving Changes in Configuration Files</a></dt><dt>conflict, <a class="indexterm" href="#s3-rpm-conflicting-files">Resolving File Conflicts</a></dt><dt>failed dependencies, <a class="indexterm" href="#s3-rpm-unresolved-dependency">Satisfying Unresolved Dependencies</a></dt><dt>freshening, <a class="indexterm" href="#s2-rpm-freshening">Freshening Packages</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 Packages</a></dt><dt>removing, <a class="indexterm" href="#s2-rpm-uninstalling">Uninstalling Packages</a></dt><dt>source and
binary packages, <a class="indexterm" href="#ch-RPM">RPM</a></dt><dt>tips, <a class="indexterm" href="#s1-rpm-usage-examples">Common Examples of RPM Usage</a></dt><dt>uninstalling, <a class="indexterm" href="#s2-rpm-uninstalling">Uninstalling Packages</a></dt><dt>verifying, <a class="indexterm" href="#s2-rpm-verifying">Verifying Packages</a></dt></dl></dd><dt>searching for packages with Yum</dt><dd><dl><dt>yum search, <a class="indexterm" href="#sec-Searching_Packages">Searching Packages</a></dt></dl></dd><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>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>upgrading RPM, <a class="indexterm" href="#sec-Installing_and_Upgrading">Installing and Upgrading Packages
</a></dt><dt>Yum instead of RPM, <a class="indexterm" href="#ch-RPM">RPM</a></dt></dl></dd><dt>partx, <a class="indexterm" href="#s2-sysinfo-filesystems-partx">Using the partx Command</a></dt><dt>password</dt><dd><dl><dt>aging, <a class="indexterm" href="#s2-users-tools-password-aging">Enabling Password Aging</a></dt><dt>expire, <a class="indexterm" href="#s2-users-tools-password-aging">Enabling Password Aging</a></dt></dl></dd><dt>passwords</dt><dd><dl><dt>shadow, <a class="indexterm" href="#s2-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>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) Config
uration</a></dt><dt>Printer Configuration</dt><dd><dl><dt>CUPS, <a class="indexterm" href="#sec-Printer_Configuration">Printer Configuration</a></dt><dt>IPP Printers, <a class="indexterm" href="#s1-printing-ipp-printer">Adding an IPP Printer</a></dt><dt>LDP/LPR Printers, <a class="indexterm" href="#sec-printing-LPDLPR-printer">Adding an LPD/LPR Host or Printer</a></dt><dt>Local Printers, <a class="indexterm" href="#sec-Adding_Other_Printer">Adding a Local Printer</a></dt><dt>New Printer, <a class="indexterm" href="#sec-Setting_Printer">Starting Printer Setup</a></dt><dt>Print Jobs, <a class="indexterm" href="#s1-printing-managing">Managing Print Jobs</a></dt><dt>Samba Printers, <a class="indexterm" href="#s1-printing-smb-printer">Adding a Samba (SMB) printer</a></dt><dt>Settings, <a class="indexterm" href="#idm261758857840">The Settings Page</a></dt><dt>Sharing Printers, <a class="indexterm" href="#sec-Sharing_Printers">Sharing Printers</a></dt></dl></dd><dt>printers (see Pr
inter Configuration)</dt><dt>processes, <a class="indexterm" href="#s1-sysinfo-system-processes">Viewing 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" href="#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="indexterm" href="#s3-email-procmail-recipes-special">Special Conditions and Actions</a></dt></dl></dd></dl></dd><dt>ps, <a class="indexterm" href="#s2-sysinfo-system-processes-ps">Using the ps Command</a></dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>RAM, <a class="indexterm" href="#s1-sysinfo-memory-usage">Viewing Memory Usage</a></dt><dt>rcp, <a class="indexterm" href="#s2-ssh-clients-scp">Using the scp Utility</a></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> rpcclient program, <a class="indexter
m" 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">Replacing Already-Installed Packages</a></dt><dt>basic modes, <a class="indexterm" href="#s1-rpm-using">Using RPM</a></dt><dt>checking package signatures, <a class="indexterm" href="#s1-check-rpm-sig">Checking Package Signatures</a></dt><dt>configuration file changes, <a class="indexterm" href="#sec-Configuration_File_Changes">Preserving Changes in Configuration Files</a></dt><dd><dl><dt>conf.rpmsave, <a class="indexterm" href="#sec-Configuration_File_Changes">Preserving Changes in Configuration Files</a></dt></dl></dd><dt>conflicts, <a class="indexterm" href="#s3-rpm-conflicting-files">Resolving File Conflicts</a></dt><dt>dependencies, <a class="indexterm" href="#s3-rpm-u
nresolved-dependency">Satisfying Unresolved Dependencies</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-usage-examples">Common Examples of RPM Usage</a></dt><dt>documentation with, <a class="indexterm" href="#s1-rpm-usage-examples">Common Examples of RPM Usage</a></dt><dt>failed dependencies, <a class="indexterm" href="#s3-rpm-unresolved-dependency">Satisfying Unresolved Dependencies</a></dt><dt>file conflicts</dt><dd><dl><dt>resolving, <a class="indexterm" href="#s3-rpm-conflicting-files">Resolving File Conflicts</a></dt></dl></dd><dt>file name, <a class="indexterm" href="#
sec-Installing_and_Upgrading">Installing and Upgrading Packages</a></dt><dt>finding and verifying RPM packages, <a class="indexterm" href="#s1-find-verify-rpm">Finding and Verifying RPM Packages</a></dt><dt>finding deleted files with, <a class="indexterm" href="#s1-rpm-usage-examples">Common Examples of RPM Usage</a></dt><dt>finding Fedora RPM packages, <a class="indexterm" href="#s2-rpm-finding">Finding RPM Packages</a></dt><dt>freshening, <a class="indexterm" href="#s2-rpm-freshening">Freshening Packages</a></dt><dt>GnuPG, <a class="indexterm" href="#s1-check-rpm-sig">Checking Package Signatures</a></dt><dt>installing, <a class="indexterm" href="#sec-Installing_and_Upgrading">Installing and Upgrading Packages</a></dt><dt>online documentation, <a class="indexterm" href="#s1-rpm-additional-resources">Additional Resources</a></dt><dt>querying, <a class="indexterm" href="#s2-rpm-querying">Querying Packages</a></dt><dt>querying for file list, <a class="indexterm" href="#s1-rpm-
usage-examples">Common Examples of RPM Usage</a></dt><dt>querying uninstalled packages, <a class="indexterm" href="#s1-rpm-usage-examples">Common Examples of RPM Usage</a></dt><dt>see also, <a class="indexterm" href="#s1-rpm-additional-resources">Additional Resources</a></dt><dt>tips, <a class="indexterm" href="#s1-rpm-usage-examples">Common Examples of RPM Usage</a></dt><dt>uninstalling, <a class="indexterm" href="#s2-rpm-uninstalling">Uninstalling Packages</a></dt><dt>upgrading, <a class="indexterm" href="#sec-Installing_and_Upgrading">Installing and Upgrading Packages</a></dt><dt>verification, <a class="indexterm" href="#s2-rpm-verifying">Verifying Packages</a></dt><dt>verifying, <a class="indexterm" href="#s2-rpm-verifying">Verifying Packages</a></dt><dt>website, <a class="indexterm" href="#s1-rpm-additional-resources">Additional Resources</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-c
onfiguration-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 Information Databases</a></dt><dt>Browsing, <a class="indexterm" href="#s2-samba-network-browsing">Samba Netw
ork 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-services">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>Samba Printers, <a class="indexterm" href="#s1-printing-smb-printer">Adding a Samba (SMB) printer</a></dt><dt>Security Modes, <a class="indexterm" href="#s2-samba-security-modes">Samba 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>Serve
r Security 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-startst
op">Starting 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 Prin
t Server 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-sha
re-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> security plug-in (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="in
dexterm" 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 clas
s="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="#s2-users-groups-shadow-utilities">Shadow Passwords</a></dt></dl></dd><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><dt> smbspool program, <a class="indexterm" href="#s2-samba-programs">Samba Distributi
on 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>connection 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-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>stunnel, <a class="indexterm" href="#s3-email-security-servers">Securing Email Client Communications</a></dt><dt>system analysis</dt><dd><dl><dt>OProfile (see OProfile)</dt></dl></dd><dt>system information</dt><dd><dl><dt>cpu usage, <a class="indexterm" href="#s1-sysinfo-cpu">Viewing CPU Usage</a></dt><dt>file systems, <a class="indexterm" href="#s1-sysinfo-filesystems">Viewing Block Devices and File Systems</a></dt><dd><dl><dt>/dev/shm, <a class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</a></dt><dt>/run, <a class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</a></dt><dt>/sy
s/fs/cgroup, <a class="indexterm" href="#s2-sysinfo-filesystems-df">Using the df Command</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">Viewing Hardware Information</a></dt><dt>memory usage, <a class="indexterm" href="#s1-sysinfo-memory-usage">Viewing Memory Usage</a></dt><dt>processes, <a class="indexterm" href="#s1-sysinfo-system-processes">Viewing System Processes</a></dt><dd><dl><dt>currently running, <a class="indexterm" href="#s2-sysinfo-system-processes-top">Using the top Command</a></dt></dl></dd></dl></dd><dt>System Log</dt><dd><dl><dt>filtering, <a class="indexterm" href="#s2-logfiles-viewing">Viewing Log Files</a></dt><dt>monitoring, <a class="indexterm" href="#s2-logfiles-examining">Monitoring Log Files</a></dt><dt>refresh rate, <a class="indexterm" href="#s2-logfiles-viewing">Viewing Log Files</a></dt><dt>searching, <a class="i
ndexterm" href="#s2-logfiles-viewing">Viewing Log Files</a></dt></dl></dd><dt>System Monitor, <a class="indexterm" href="#s2-sysinfo-system-processes-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="#s2-sysinfo-memory-usage-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="#s2-sysinfo-cpu-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="#s2-sysinfo-filesystems-system_monitor">Using the System Monitor Tool</a></dt><dt> 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>the Users settings tool (see user configuration)</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>top, <a class="indexterm" href="#s2-sysinfo-system-processes-top">Using the to
p Command</a></dt></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>user configuration</dt><dd><dl><dt>command line configuration</dt><dd><dl><dt>chage, <a class="indexterm" href="#s2-users-tools-password-aging">Enabling Password Aging</a></dt><dt>passwd, <a class="indexterm" href="#s2-users-tools-users-add">Adding a New User</a></dt><dt>useradd, <a class="indexterm" href="#s2-users-tools-users-add">Adding a New User</a></dt></dl></dd><dt>password</dt><dd><dl><dt>forcing expiration of, <a class="indexterm" href="#s2-users-tools-password-aging">Enabling Password Aging</a></dt></dl></dd><dt>viewing list of users, <a class="indexterm" href="#s1-users-configui">Managing Users in a Graphical Environment</a></dt></dl></dd><dt>user private groups (see groups)</dt><dd><dl><dt>and shared directories, <a class="indexterm" href="#s2-users-tools-groups-directories">Creating Group Directories</a></dt></dl></dd><dt>useradd command</dt><dd><dl><dt>user account creation using, <a class="in
dexterm" href="#s2-users-tools-users-add">Adding a New User</a></dt></dl></dd><dt>users (see user configuration)</dt><dd><dl><dt>additional resources, <a class="indexterm" href="#sect-Users_and_Groups-Resources">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="#sect-Users_and_Groups-Resources">Additional Resources</a></dt></dl></dd><dt>introducing, <a class="indexterm" href="#ch-Managing_Users_and_Groups">Managing Users and Groups</a></dt><dt>tools for management of</dt><dd><dl><dt>the Users setting tool, <a class="indexterm" href="#s1-users-tools">Using Command Line Tools</a></dt><dt>useradd, <a class="indexterm" href="#s1-users-tools">Using Command Line 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 host (see Apache HTTP Server)</dt><dt> vsftpd , <a class="indexterm" href="#s2-ftp-serv
ers">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-websites">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 copies 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></dl></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
plug-ins, <a class="indexterm" href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring, and Disabling Yum Plug-ins</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 plug-ins, <a class="indexterm" href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring, and Disabling Yum Plug-ins</a></dt><dt>displaying packages</dt><dd><dl><dt>yum info, <a class="indexterm" href="#sec-Displaying_Package_Information">Displaying Package Information</a></dt></dl></dd><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 plug-ins, <a class="indexterm" href="#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring, and Disabling Yum Plug-ins</a></dt><dt>installing a package g
roup 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_Gro
ups">Packages and Package Groups</a></dt><dt>plug-ins</dt><dd><dl><dt>fs-snapshot, <a class="indexterm" href="#sec-Plugin_Descriptions">Plug-in Descriptions</a></dt><dt>presto, <a class="indexterm" href="#sec-Plugin_Descriptions">Plug-in Descriptions</a></dt><dt>refresh-packagekit, <a class="indexterm" href="#sec-Plugin_Descriptions">Plug-in Descriptions</a></dt><dt>rhnplugin, <a class="indexterm" href="#sec-Plugin_Descriptions">Plug-in Descriptions</a></dt><dt>security, <a class="indexterm" href="#sec-Plugin_Descriptions">Plug-in Descriptions</a></dt></dl></dd><dt>repository, <a class="indexterm" href="#sec-Managing_Yum_Repositories">Adding, Enabling, and Disabling a Yum Repository</a>, <a class="indexterm" href="#sec-Creating_a_Yum_Repository">Creating a Yum Repository</a></dt><dt>searching for packages with Yum</dt><dd><dl><dt>yum search, <a class="indexterm" href="#sec-Searching_Packages">Searching Packages</a></dt></dl></dd><dt>searching packages with Yum</dt><dd><dl><d
t>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 plug-ins, <a class="indexterm" href="#sec-Yum_Plugins">Yum Plug-ins</a></dt><dt>Yum repositories</dt><dd><dl><dt>configuring Yum and Yum repositories, <a class="indexterm" href="#sec-Configuring_Yum_and_Yum_Re
positories">Configuring Yum and Yum Repositories</a></dt></dl></dd></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>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/app-Revision_History.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/app-Revision_History.html
index 53cb4ec..2f56867 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/app-Revision_History.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/app-Revision_History.html
@@ -6,8 +6,11 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="s2-rpm-related-books.html" title="A.5.3. Related Books" /><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="s2-rpm-related-books.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ix01.html"><strong>Next</strong></a>
</li></ul><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 summary="Revision History"><tr><th align="left" valign="top" colspan="3"><strong>Revision History</strong></th></tr><tr><td align="left">Revision 1-2</td><td align="left">Tue Dec 9 2014</td><td align="left"><span class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></span></td></tr><tr><td align="left" colspan="3">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="s1-rpm-additional-resources.html" title="A.5. Additional Resources" /><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-rpm-additional-resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ix01.html"><stron
g>Next</strong></a></li></ul><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 summary="Revision History"><tr><th align="left" valign="top" colspan="3"><strong>Revision History</strong></th></tr><tr><td align="left">Revision 1-2.1</td><td align="left">Wed Mar 4 2015</td><td align="left"><span class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></span></td></tr><tr><td align="left" colspan="3">
+ <table border="0" summary="Simple list" class="simplelist"><tr><td>Added "Working with the GRUB 2 Boot Loader" chapter.</td></tr></table>
+
+ </td></tr><tr><td align="left">Revision 1-2</td><td align="left">Tue Dec 9 2014</td><td align="left"><span class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></span></td></tr><tr><td align="left" colspan="3">
<table border="0" summary="Simple list" class="simplelist"><tr><td>Fedora 21 release of the <em class="citetitle">System Administrator's Guide</em>.</td></tr></table>
</td></tr><tr><td align="left">Revision 1-1</td><td align="left">Thu Aug 9 2012</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">
@@ -18,4 +21,4 @@
</td></tr></table></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="ix01.html"><strong>Next</strong>Index</a></li></ul></body></html>
\ No newline at end of file
+ </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="ix01.html"><strong>Next</strong>Index</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Automating_System_Tasks.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Automating_System_Tasks.html
index 529b6b5..9011431 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Automating_System_Tasks.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Automating_System_Tasks.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Monitoring_and_Automation.html" title="Part V. 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 class="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 class="toc"><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#sect-Cron-Installing">18.1.1. Installing Cron and Anacron</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#sect-Cron-Running">18.1.2. Running the Crond Service</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">18.1.3. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">1
8.1.4. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-autotasks-cron-access">18.1.5. 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.6. Black and 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#sect-At_and_Batch_Installation">18.2.1. Installing At and Batch</a></span></dt><dt><span class="section"><a href="sect-Atd-Running.html">18.2.2. Running the At Service</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-configuring.html">18.2.3. Configuring an At Job</a></span></dt><dt><span class="section"><a href="s2-autotasks-batch-configuring.html">18.2.4. Configuring a Batch Job</a></span></dt><dt><span class="section"><a href="s2-autotas
ks-at-batch-viewing.html">18.2.5. Viewing Pending Jobs</a></span></dt><dt><span class="section"><a href="s2-autotasks-commandline-options.html">18.2.6. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-controlling-access.html">18.2.7. Controlling Access to At and Batch</a></span></dt></dl></dd><dt><span class="section"><a href="s1-autotasks-additional-resources.html">18.3. Additional Resources</a></span></dt></dl></div><a id="idm225474866528" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Monitoring_and_Automation.html" title="Part V. Monitoring and Automation" /><link rel="prev" href="s1-log-files-additional-resources.html" title="17.10. Additional Resources" /><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="s1-log-files-additional-resources.html"><strong>Pr
ev</strong></a></li><li class="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 class="toc"><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#sect-Cron-Installing">18.1.1. Installing Cron and Anacron</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#sect-Cron-Running">18.1.2. Running the Crond Service</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">18.1.3. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configurin
g-cron-jobs">18.1.4. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-autotasks-cron-access">18.1.5. 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.6. Black and 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#sect-At_and_Batch_Installation">18.2.1. Installing At and Batch</a></span></dt><dt><span class="section"><a href="sect-Atd-Running.html">18.2.2. Running the At Service</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-configuring.html">18.2.3. Configuring an At Job</a></span></dt><dt><span class="section"><a href="s2-autotasks-batch-configuring.html">18.2.4. Configuring a Batch Job</a></span></dt><dt><span class="section"><a hr
ef="s2-autotasks-at-batch-viewing.html">18.2.5. Viewing Pending Jobs</a></span></dt><dt><span class="section"><a href="s2-autotasks-commandline-options.html">18.2.6. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-controlling-access.html">18.2.7. Controlling Access to At and Batch</a></span></dt></dl></dd><dt><span class="section"><a href="s1-autotasks-additional-resources.html">18.3. Additional Resources</a></span></dt></dl></div><a id="idm261757717888" class="indexterm"></a><div class="para">
Tasks, also known as <em class="firstterm">jobs</em>, can be configured to run automatically within a specified period of time, on a specified date, or when the system load average decreases below 0.8.
</div><div class="para">
Fedora is pre-configured to run important system tasks to keep the system updated. For example, the <span class="database">slocate</span> database used by the <code class="command">locate</code> command is updated daily. A system administrator can use automated tasks to perform periodic backups, monitor the system, run custom scripts, and so on.
@@ -16,7 +16,7 @@
Every utility is intended for scheduling a different job type: while Cron and Anacron schedule recurring jobs, At and Batch schedule one-time jobs (refer to <a class="xref" href="ch-Automating_System_Tasks.html#s1-autotasks-cron-anacron">Section 18.1, “Cron and Anacron”</a> and <a class="xref" href="s1-autotasks-at-batch.html">Section 18.2, “At and Batch”</a> respectively).
</div><div class="para">
Fedora supports the use of <code class="systemitem">systemd.timer</code> for executing a job at a specific time. See man <code class="filename">systemd.timer(5)</code> for more information.
- </div><div class="section" id="s1-autotasks-cron-anacron"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.1. Cron and Anacron</h2></div></div></div><a id="idm225447550944" class="indexterm"></a><a id="idm225474421776" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s1-autotasks-cron-anacron"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">18.1. Cron and Anacron</h2></div></div></div><a id="idm261717226560" class="indexterm"></a><a id="idm261718832880" class="indexterm"></a><div class="para">
Both Cron and Anacron are daemons that can schedule execution of recurring tasks to a certain point in time defined by the exact time, day of the month, month, day of the week, and week.
</div><div class="para">
Cron jobs can run as often as every minute. However, the utility assumes that the system is running continuously and if the system is not on at the time when a job is scheduled, the job is not executed.
@@ -50,7 +50,7 @@
To restart the <code class="systemitem">crond</code> service, type the following at a shell prompt as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">systemctl restart crond.service</code></pre><div class="para">
This command stops the service and starts it again in quick succession.
- </div></div></div><div class="section" id="s2-configuring-anacron-jobs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.3. Configuring Anacron Jobs</h3></div></div></div><a id="idm225476687216" class="indexterm"></a><a id="idm225476685808" class="indexterm"></a><a id="idm225476684368" class="indexterm"></a><a id="idm225476682928" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s2-configuring-anacron-jobs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.3. Configuring Anacron Jobs</h3></div></div></div><a id="idm261746818640" class="indexterm"></a><a id="idm261746817232" class="indexterm"></a><a id="idm261750011056" class="indexterm"></a><a id="idm261750009616" class="indexterm"></a><div class="para">
The main configuration file to schedule jobs is the <code class="filename">/etc/anacrontab</code> file, which can be only accessed by the <code class="systemitem">root</code> user. The file contains the following:
</div><pre class="programlisting">SHELL=/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin
@@ -127,7 +127,7 @@ START_HOURS_RANGE=16-20
The second job executes the <code class="filename">weeklyjob.bash</code> script in the <code class="filename">/etc/</code> directory once a week.
</div><div class="para">
The third job runs a command, which writes the contents of <code class="filename">/proc</code> to the <code class="filename">/tmp/proc</code> file (<code class="command">ls /proc >> /tmp/proc</code>) once a month.
- </div></div></div><div class="section" id="s2-configuring-cron-jobs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.4. Configuring Cron Jobs</h3></div></div></div><a id="idm225453045056" class="indexterm"></a><a id="idm225461766128" class="indexterm"></a><a id="idm225461764688" class="indexterm"></a><a id="idm225461763248" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s2-configuring-cron-jobs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.1.4. Configuring Cron Jobs</h3></div></div></div><a id="idm261745112128" class="indexterm"></a><a id="idm261745110688" class="indexterm"></a><a id="idm261783092704" class="indexterm"></a><a id="idm261783091264" class="indexterm"></a><div class="para">
The configuration file for cron jobs is <code class="filename">/etc/crontab</code>, which can be only modified by the <code class="systemitem">root</code> user. The file contains the following:
</div><pre class="programlisting">SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
@@ -207,4 +207,4 @@ HOME=/
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.5, “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>
\ No newline at end of file
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-log-files-additional-resources.html"><strong>Prev</strong>17.10. 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-autotasks-at-batch.html"><strong>Next</strong>18.2. At and Batch</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Configuring_PTP_Using_ptp4l.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Configuring_PTP_Using_ptp4l.html
index 43fcba1..4fb5adb 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Configuring_PTP_Using_ptp4l.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Configuring_PTP_Using_ptp4l.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Servers.html" title="Part IV. Servers" /><link rel="prev" href="s2-ntpd_useful-websites.html" title="14.20.2. Useful Websites" /><link rel="next" href="sec-Using_PTP.html" title="15.2. Using PTP" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ntpd_useful-websites.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Using
_PTP.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-Configuring_PTP_Using_ptp4l" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 15. Configuring PTP Using ptp4l</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Introduction_to_PTP">15.1. Introduction to PTP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Understanding_PTP">15.1.1. Understanding PTP</a></span></dt><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Advantages_of_PTP">15.1.2. Advantages of PTP</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_PTP.html">15.2. Using PTP</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_PTP.html#sec-Checking_for_Driver_and_Hardware_Support">15.2.1. Checking for Driver and Hardware Support</a></span></dt><dt><span class="section"
><a href="sec-Installing_PTP.html">15.2.2. Installing PTP</a></span></dt><dt><span class="section"><a href="sec-Starting_ptp4l.html">15.2.3. Starting ptp4l</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Specifying_a_Configuration_File.html">15.3. Specifying a Configuration File</a></span></dt><dt><span class="section"><a href="sec-Using_the_PTP_Management_Client.html">15.4. Using the PTP Management Client</a></span></dt><dt><span class="section"><a href="sec-Synchronizing_the_Clocks.html">15.5. Synchronizing the Clocks</a></span></dt><dt><span class="section"><a href="sec-Verifying_Time_Synchronization.html">15.6. Verifying Time Synchronization</a></span></dt><dt><span class="section"><a href="sec-Serving_PTP_Time_with_NTP.html">15.7. Serving PTP Time with NTP</a></span></dt><dt><span class="section"><a href="sec-Serving_NTP_Time_with_PTP.html">15.8. Serving NTP Time with PTP</a></span></dt><dt><span class="section"><a href="sec-Improving_Accuracy.html">15.9
. Improving Accuracy</a></span></dt><dt><span class="section"><a href="sec-PTP_additional_resources.html">15.10. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-PTP_additional_resources.html#sec-PTP-docs-inst">15.10.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-PTP_useful-websites.html">15.10.2. Useful Websites</a></span></dt></dl></dd></dl></div><div class="section" id="sec-Introduction_to_PTP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.1. Introduction to PTP</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Servers.html" title="Part IV. Servers" /><link rel="prev" href="s2-ntpd_useful-websites.html" title="14.20.2. Useful Websites" /><link rel="next" href="sec-Using_PTP.html" title="15.2. Using PTP" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ntpd_useful-websites.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Using
_PTP.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-Configuring_PTP_Using_ptp4l" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 15. Configuring PTP Using ptp4l</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Introduction_to_PTP">15.1. Introduction to PTP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Understanding_PTP">15.1.1. Understanding PTP</a></span></dt><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Advantages_of_PTP">15.1.2. Advantages of PTP</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_PTP.html">15.2. Using PTP</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_PTP.html#sec-Checking_for_Driver_and_Hardware_Support">15.2.1. Checking for Driver and Hardware Support</a></span></dt><dt><span class="section"
><a href="sec-Installing_PTP.html">15.2.2. Installing PTP</a></span></dt><dt><span class="section"><a href="sec-Starting_ptp4l.html">15.2.3. Starting ptp4l</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Specifying_a_Configuration_File.html">15.3. Specifying a Configuration File</a></span></dt><dt><span class="section"><a href="sec-Using_the_PTP_Management_Client.html">15.4. Using the PTP Management Client</a></span></dt><dt><span class="section"><a href="sec-Synchronizing_the_Clocks.html">15.5. Synchronizing the Clocks</a></span></dt><dt><span class="section"><a href="sec-Verifying_Time_Synchronization.html">15.6. Verifying Time Synchronization</a></span></dt><dt><span class="section"><a href="sec-Serving_PTP_Time_with_NTP.html">15.7. Serving PTP Time with NTP</a></span></dt><dt><span class="section"><a href="sec-Serving_NTP_Time_with_PTP.html">15.8. Serving NTP Time with PTP</a></span></dt><dt><span class="section"><a href="sec-Synchronize_to_PTP_or_NTP_Tim
e_Using_timemaster.html">15.9. Synchronize to PTP or NTP Time Using timemaster</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html#sec-Starting_timemaster_as_a_Service">15.9.1. Starting timemaster as a Service</a></span></dt><dt><span class="section"><a href="sec-Understanding_the_timemaster_Configuration_File.html">15.9.2. Understanding the timemaster Configuration File</a></span></dt><dt><span class="section"><a href="sec-Configuring_timemaster_Options.html">15.9.3. Configuring timemaster Options</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Improving_Accuracy.html">15.10. Improving Accuracy</a></span></dt><dt><span class="section"><a href="sec-PTP_additional_resources.html">15.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-PTP_additional_resources.html#sec-PTP-docs-inst">15.11.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="
sec-PTP_useful-websites.html">15.11.2. Useful Websites</a></span></dt></dl></dd></dl></div><div class="section" id="sec-Introduction_to_PTP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.1. Introduction to PTP</h2></div></div></div><div class="para">
The <em class="firstterm">Precision Time Protocol</em> (<acronym class="acronym">PTP</acronym>) is a protocol used to synchronize clocks in a network. When used in conjunction with hardware support, <code class="systemitem">PTP</code> is capable of sub-microsecond accuracy, which is far better than is normally obtainable with <code class="systemitem">NTP</code>. <code class="systemitem">PTP</code> support is divided between the kernel and user space. The kernel in Fedora includes support for <code class="systemitem">PTP</code> clocks, which are provided by network drivers. The actual implementation of the protocol is known as <span class="application"><strong>linuxptp</strong></span>, a <code class="systemitem">PTPv2</code> implementation according to the IEEE standard 1588 for Linux.
</div><div class="para">
The <span class="package">linuxptp</span> package includes the <span class="application"><strong>ptp4l</strong></span> and <span class="application"><strong>phc2sys</strong></span> programs for clock synchronization. The <span class="application"><strong>ptp4l</strong></span> program implements the <code class="systemitem">PTP</code> boundary clock and ordinary clock. With hardware time stamping, it is used to synchronize the <code class="systemitem">PTP</code> hardware clock to the master clock, and with software time stamping it synchronizes the system clock to the master clock. The <span class="application"><strong>phc2sys</strong></span> program is needed only with hardware time stamping, for synchronizing the system clock to the <code class="systemitem">PTP</code> hardware clock on the <em class="firstterm">network interface card</em> (<acronym class="acronym">NIC</acronym>).
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Configuring_the_Date_and_Time.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Configuring_the_Date_and_Time.html
index 0e2c572..1b78bf2 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Configuring_the_Date_and_Time.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Configuring_the_Date_and_Time.html
@@ -59,7 +59,7 @@ NTP synchronized: no
Note that changing the date without specifying the current time results in setting the time to 00:00:00.
</div><div class="example" id="exam-Configuring_the_Date_and_Time-timedatectl-Date"><h6>Example 3.3. Changing the Current Date</h6><div class="example-contents"><div class="para">
To change the current date to 2 June 2013 and keep the current time (11:26 p.m.), run the following command as <code class="systemitem">root</code>:
- </div><pre class="screen">~]# <code class="command">timedatectl set-time 2013-06-02 23:26:00</code></pre></div></div><br class="example-break" /></div><div class="section" id="sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.1.4. Changing the Time Zone</h3></div></div></div><div class="para">
+ </div><pre class="screen">~]# <code class="command">timedatectl set-time "2013-06-02 23:26:00"</code></pre></div></div><br class="example-break" /></div><div class="section" id="sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">3.1.4. Changing the Time Zone</h3></div></div></div><div class="para">
To list all available time zones, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">timedatectl</code> <code class="option">list-timezones</code></pre><div class="para">
To change the currently used time zone, type as <code class="systemitem">root</code>:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Directory_Servers.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Directory_Servers.html
index 5ad8235..6c0968f 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Directory_Servers.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Directory_Servers.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Servers.html" title="Part IV. Servers" /><link rel="prev" href="s2-email-related-books.html" title="10.6.3. Related Books" /><link rel="next" href="ch-File_and_Print_Servers.html" title="Chapter 12. File and Print 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 ac
cesskey="n" href="ch-File_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 11. Directory Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Directory_Servers.html#s1-OpenLDAP">11.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-introduction">11.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-installation">11.1.2. Installing the OpenLDAP Suite</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-configuration">11.1.3. Configuring an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-running">11.1.4. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="ch-Directory_
Servers.html#s2-ldap-pam">11.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">11.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">11.1. OpenLDAP</h2></div></div></div><a id="idm225468441936" class="indexterm"></a><a id="idm225468443632" class="indexterm"></a><a id="idm225468445024" class="indexterm"></a><a id="idm225468446832" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Servers.html" title="Part IV. Servers" /><link rel="prev" href="s2-email-related-books.html" title="10.6.3. Related Books" /><link rel="next" href="ch-File_and_Print_Servers.html" title="Chapter 12. File and Print 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 ac
cesskey="n" href="ch-File_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 11. Directory Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Directory_Servers.html#s1-OpenLDAP">11.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-introduction">11.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-installation">11.1.2. Installing the OpenLDAP Suite</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-configuration">11.1.3. Configuring an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-selinux-openldap">11.1.4. SELinux Policy for Applications Using LDAP</a></span></dt><dt><span class="section"><a
href="ch-Directory_Servers.html#s2-ldap-running">11.1.5. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-pam">11.1.6. Configuring a System to Authenticate Using OpenLDAP</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-resources">11.1.7. Additional Resources</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s3-ldap-related-books">11.1.8. Related Books</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">11.1. OpenLDAP</h2></div></div></div><a id="idm261740468176" class="indexterm"></a><a id="idm261754726480" class="indexterm"></a><a id="idm261754726976" class="indexterm"></a><a id="idm261754730176" 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.
@@ -15,24 +15,24 @@
</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">11.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.
+ Using a client-server architecture, LDAP provides a reliable means to create a central information directory accessible from the network. When a client attempts to modify information within this directory, the server verifies the user has permission to make the change, and then adds or updates the entry as requested. To ensure the communication is secure, the <em class="firstterm">Transport Layer Security</em> (<acronym class="acronym">TLS</acronym>) cryptographic protocol can be used to prevent an attacker from intercepting the transmission.
</div><div class="important"><div class="admonition_header"><h2>Using Mozilla NSS</h2></div><div class="admonition"><div class="para">
- The OpenLDAP suite in Fedora 21 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>.
+ The OpenLDAP suite in Fedora 21 no longer uses OpenSSL. Instead, it uses the Mozilla implementation of <em class="firstterm">Network Security Services</em> (<acronym class="acronym">NSS</acronym>). OpenLDAP continues to work with existing certificates, keys, and other TLS configuration. For more information on how to configure it to use Mozilla certificate and key database, see <a href="http://www.openldap.org/faq/index.cgi?file=1514"><em class="citetitle">How do I use TLS/SSL with Mozilla NSS</em></a>.
</div></div></div><div class="para">
The LDAP server supports several database systems, which gives administrators the flexibility to choose the best suited solution for the type of information they are planning to serve. Because of a well-defined client <em class="firstterm">Application Programming Interface</em> (<acronym class="acronym">API</acronym>), the number of applications able to communicate with an LDAP server is numerous, and increasing in both quantity and quality.
</div><div class="section" id="s3-ldap-terminology"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.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 class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225457241632" class="indexterm"></a>
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261760803952" 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="idm225446916768" class="indexterm"></a>
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261739324768" 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.
+ An attribute can either have a single value, or an unordered space-separated list of values. While certain attributes are optional, others are required. Required attributes are specified using the <code class="option">objectClass</code> definition, and can be found in schema files located in the <code class="filename">/etc/openldap/slapd.d/cn=config/cn=schema/</code> directory.
</div><div class="para">
The assertion of an attribute and its corresponding value is also referred to as a <em class="firstterm">Relative Distinguished Name</em> (<acronym class="acronym">RDN</acronym>). Unlike distinguished names that are unique globally, a relative distinguished name is only unique per entry.
- </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225446924560" class="indexterm"></a>
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261739321360" 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>
@@ -40,7 +40,7 @@
<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">11.1.1.2. OpenLDAP Features</h4></div></div></div><a id="idm225440006608" class="indexterm"></a><div class="para">
+ </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">11.1.1.2. OpenLDAP Features</h4></div></div></div><a id="idm261735352608" 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.
@@ -54,19 +54,19 @@
<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">11.1.1.3. OpenLDAP Server Setup</h4></div></div></div><a id="idm225497634288" class="indexterm"></a><div class="para">
+ </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">11.1.1.3. OpenLDAP Server Setup</h4></div></div></div><a id="idm261735365904" class="indexterm"></a><div class="para">
The typical steps to set up an LDAP server on Fedora are as follows:
</div><div class="procedure"><ol class="1"><li class="step"><div class="para">
Install the OpenLDAP suite. See <a class="xref" href="ch-Directory_Servers.html#s2-ldap-installation">Section 11.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 11.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 11.1.4, “Running an OpenLDAP Server”</a>.
+ Start the <code class="systemitem">slapd</code> service as described in <a class="xref" href="ch-Directory_Servers.html#s2-ldap-running">Section 11.1.5, “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">11.1.2. Installing the OpenLDAP Suite</h3></div></div></div><a id="idm225463503616" class="indexterm"></a><a id="idm225463505072" class="indexterm"></a><div class="para">
+ </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">11.1.2. Installing the OpenLDAP Suite</h3></div></div></div><a id="idm261751759872" class="indexterm"></a><a id="idm261760202688" 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 11.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 class="">
Package
@@ -99,19 +99,19 @@
</td><td class="">
A package containing <code class="systemitem">nslcd</code>, a local LDAP name service that allows a user to perform local LDAP queries.
</td></tr><tr><td class="">
- <span class="package">mod_authz_ldap</span>
+ <span class="package">mod_ldap</span>
</td><td class="">
<div class="para">
- A package containing <code class="systemitem">mod_authz_ldap</code>, the LDAP authorization module for the Apache HTTP Server. This module uses the short form of the distinguished name for a subject and the issuer of the client SSL certificate to determine the distinguished name of the user within an LDAP directory. It is also capable of authorizing users based on attributes of that user's LDAP directory entry, determining access to assets based on the user and group privileges of the asset, and denying access for users with expired passwords. Note that the <code class="systemitem">mod_ssl</code> module is required when using the <code class="systemitem">mod_authz_ldap</code> module.
+ A package containing the <code class="systemitem">mod_authnz_ldap</code> and <code class="systemitem">mod_ldap</code> modules. The <code class="systemitem">mod_authnz_ldap</code> module is the LDAP authorization module for the Apache HTTP Server. This module can authenticate users' credentials against an LDAP directory, and can enforce access control based on the user name, full DN, group membership, an arbitrary attribute, or a complete filter string. The <code class="systemitem">mod_ldap</code> module contained in the same package provides a configurable shared memory cache, to avoid repeated directory access across many HTTP requests, and also support for SSL/TLS.
</div>
</td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
To install these packages, use the <code class="command">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 5.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">11.1.2.1. Overview of OpenLDAP Server Utilities</h4></div></div></div><a id="idm225439986064" class="indexterm"></a><div class="para">
+ </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, see <a class="xref" href="sec-Installing.html">Section 5.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">11.1.2.1. Overview of OpenLDAP Server Utilities</h4></div></div></div><a id="idm261760207136" 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 11.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 class="">
Command
@@ -154,14 +154,14 @@
</td><td class="">
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 11.1.6.1, “Installed Documentation”</a>.
+ For a detailed description of these utilities and their usage, see the corresponding manual pages as referred to in <a class="xref" href="ch-Directory_Servers.html#bh-Installed_Documentation_OpenLDAP">the section called “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">slapadd</code> utility, type the following at a shell prompt:
</div><pre class="screen"><code class="command">chown -R ldap:ldap /var/lib/ldap</code></pre></div></div><div class="warning"><div class="admonition_header"><h2>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 11.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">11.1.2.2. Overview of OpenLDAP Client Utilities</h4></div></div></div><a id="idm225479047264" class="indexterm"></a><div class="para">
+ </div><pre class="screen">~]# <code class="command">systemctl stop slapd.service</code></pre><div class="para">
+ For more information on how to start, stop, restart, and check the current status of the <code class="systemitem">slapd</code> service, see <a class="xref" href="ch-Directory_Servers.html#s2-ldap-running">Section 11.1.5, “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">11.1.2.2. Overview of OpenLDAP Client Utilities</h4></div></div></div><a id="idm261758935184" 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 11.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 class="">
Command
@@ -209,7 +209,7 @@
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">11.1.2.3. Overview of Common LDAP Client Applications</h4></div></div></div><a id="idm225464453792" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-ldap-packages-applications"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.2.3. Overview of Common LDAP Client Applications</h4></div></div></div><a id="idm261753486928" 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">11.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:
@@ -218,24 +218,24 @@
</th><th class="">
Description
</th></tr></thead><tbody><tr><td class="">
- <a id="idm225464467088" class="indexterm"></a>
+ <a id="idm261741223392" class="indexterm"></a>
<code class="filename">/etc/openldap/ldap.conf</code>
</td><td class="">
The configuration file for client applications that use the OpenLDAP libraries. This includes <code class="command">ldapadd</code>, <code class="command">ldapsearch</code>, <span class="application"><strong>Evolution</strong></span>, etc.
</td></tr><tr><td class="">
- <a id="idm225460893360" class="indexterm"></a>
+ <a id="idm261760829840" class="indexterm"></a>
<code class="filename">/etc/openldap/slapd.d/</code>
</td><td class="">
The directory containing the <code class="systemitem">slapd</code> configuration.
</td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
Note that OpenLDAP no longer reads its configuration from the <code class="filename">/etc/openldap/slapd.conf</code> file. Instead, it uses a configuration database located in the <code class="filename">/etc/openldap/slapd.d/</code> directory. If you have an existing <code class="filename">slapd.conf</code> file from a previous installation, you can convert it to the new format by running the following command as <code class="systemitem">root</code>:
- </div><pre class="screen"><code class="command">slaptest -f /etc/openldap/slapd.conf -F /etc/openldap/slapd.d/</code></pre><div class="para">
+ </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 11.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">11.1.3.1. Changing the Global Configuration</h4></div></div></div><a id="idm225459439472" class="indexterm"></a><a id="idm225447168496" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s3-ldap-configuration-global"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.3.1. Changing the Global Configuration</h4></div></div></div><a id="idm261739438784" class="indexterm"></a><a id="idm261739440336" class="indexterm"></a><div class="para">
Global configuration options for the LDAP server are stored in the <code class="filename">/etc/openldap/slapd.d/cn=config.ldif</code> file. The following directives are commonly used:
- </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225447172160" class="indexterm"></a>
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261739445088" 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">
@@ -264,17 +264,17 @@
<code class="option">proxy_authz_anon</code>
</td><td class="">
Enables processing of anonymous proxy authorization control.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-ldap-configuration-olcallows"><h6>Example 11.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="idm225443447248" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-ldap-configuration-olcallows"><h6>Example 11.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="idm261748046960" 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 11.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="idm225458684224" class="indexterm"></a>
+ </div><div class="example" id="example-ldap-configuration-olcconnmaxpending"><h6>Example 11.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="idm261748055664" 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 11.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="idm225435387952" class="indexterm"></a>
+ </div><div class="example" id="example-ldap-configuration-olcconnmaxpendingauth"><h6>Example 11.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="idm261745178496" 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">
@@ -299,78 +299,176 @@
<code class="option">tls_authc</code>
</td><td class="">
Disallows the STARTTLS command when authenticated.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-ldap-configuration-olcdisallows"><h6>Example 11.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="idm225457372512" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-ldap-configuration-olcdisallows"><h6>Example 11.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="idm261753203040" 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 11.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="idm225457381696" class="indexterm"></a>
+ </div><div class="example" id="example-ldap-configuration-olcidletimeout"><h6>Example 11.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="idm261753213792" 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 11.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="idm225454392272" class="indexterm"></a>
+ </div><div class="example" id="example-ldap-configuration-olclogfile"><h6>Example 11.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="idm261757651552" 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 11.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="idm225454402928" class="indexterm"></a>
+ </div><div class="example" id="example-ldap-configuration-olcreferral"><h6>Example 11.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="idm261757660448" 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 11.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">11.1.3.2. Changing the Database-Specific Configuration</h4></div></div></div><a id="idm225438311296" class="indexterm"></a><a id="idm225438315120" class="indexterm"></a><div class="para">
+ </div><div class="example" id="example-ldap-configuration-olcwritetimeout"><h6>Example 11.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">11.1.3.2. Changing the Database-Specific Configuration</h4></div></div></div><a id="idm261763797584" class="indexterm"></a><a id="idm261763799344" class="indexterm"></a><div class="para">
By default, the OpenLDAP server uses Berkeley DB (BDB) as a database back end. The configuration for this database is stored in the <code class="filename">/etc/openldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif</code> file. The following directives are commonly used in a database-specific configuration:
- </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225438317328" class="indexterm"></a>
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261763803552" 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 11.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="idm225480498816" class="indexterm"></a>
+ </div><div class="example" id="example-ldap-configuration-olcreadonly"><h6>Example 11.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="idm261756906320" 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 11.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="idm225475593952" class="indexterm"></a>
+ </div><div class="example" id="example-ldap-configuration-olcrootdn"><h6>Example 11.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="idm261743929984" 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>
+ It accepts either a plain text string, or a hash. To generate a hash, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">slappaswd</code>
New password:
Re-enter new password:
-{SSHA}WczWsyPEnMchFf1GRTweq2q7XJcvmSxD</pre><div class="example" id="example-ldap-configuration-olcrootpw"><h6>Example 11.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="idm225435875616" class="indexterm"></a>
+{SSHA}WczWsyPEnMchFf1GRTweq2q7XJcvmSxD</pre><div class="example" id="example-ldap-configuration-olcrootpw"><h6>Example 11.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="idm261743940160" 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 11.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">11.1.3.3. Extending Schema</h4></div></div></div><a id="idm225435885488" class="indexterm"></a><a id="idm225435883664" class="indexterm"></a><div class="para">
- Since OpenLDAP 2.3, the <code class="filename">/etc/openldap/slapd.d/</code> directory also contains LDAP definitions that were previously located in <code class="filename">/etc/openldap/schema/</code>. It is possible to extend the schema used by OpenLDAP to support additional attribute types and object classes using the default schema files as a guide. However, this task is beyond the scope of this chapter. For more information on this topic, refer to <a href="http://www.openldap.org/doc/admin/schema.html">http://www.openldap.org/doc/admin/schema.html</a>.
- </div></div></div><div class="section" id="s2-ldap-running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.1.4. Running an OpenLDAP Server</h3></div></div></div><a id="idm225501360016" 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 6, <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">11.1.4.1. Starting the Service</h4></div></div></div><a id="idm225501364352" 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">
+ </div><div class="example" id="example-ldap-configuration-olcsuffix"><h6>Example 11.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">11.1.3.3. Extending Schema</h4></div></div></div><a id="idm261746263552" class="indexterm"></a><a id="idm261746265472" class="indexterm"></a><div class="para">
+ Since OpenLDAP 2.3, the <code class="filename">/etc/openldap/slapd.d/</code> directory also contains LDAP definitions that were previously located in <code class="filename">/etc/openldap/schema/</code>. It is possible to extend the schema used by OpenLDAP to support additional attribute types and object classes using the default schema files as a guide. However, this task is beyond the scope of this chapter. For more information on this topic, see <a href="http://www.openldap.org/doc/admin/schema.html">http://www.openldap.org/doc/admin/schema.html</a>.
+ </div></div><div class="section" id="s3-establishing_a_secure_connection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.3.4. Establishing a Secure Connection</h4></div></div></div><a id="idm261751532528" class="indexterm"></a><a id="idm261751532688" class="indexterm"></a><a id="idm261751534592" class="indexterm"></a><a id="idm261751537200" class="indexterm"></a><div class="para">
+ OpenLDAP clients and servers can be secured using the Transport Layer Security (TLS) framework. TLS is a cryptographic protocol designed to provide communication security over the network. As noted above, OpenLDAP suite in Fedora uses Mozilla NSS as the TLS implementation.
+ </div><div class="para">
+ To establish a secure connection using TLS, obtain the required certificates as described in <a href="http://www.openldap.org/faq/index.cgi?file=1514"><em class="citetitle">How do I use TLS/SSL with Mozilla NSS</em></a>. Then, a number of options must be configured on both the client and the server. At a minimum, a server must be configured with the Certificate Authority (CA) certificates and also its own server certificate and private key. The clients must be configured with the name of the file containing all the trusted CA certificates.
+ </div><div class="para">
+ Typically, a server only needs to sign a single CA certificate. A client may want to connect to a variety of secure servers, therefore it is common to specify a list of several trusted CAs in its configuration.
+ </div><h5 id="br-server_configuration">Server Configuration</h5><div class="para">
+ This section lists global configuration directives for <code class="systemitem">slapd</code> that need to be specified in the <code class="filename">/etc/openldap/slapd.d/cn=config.ldif</code> file on an OpenLDAP server in order to establish TLS.
+ </div><div class="para">
+ While the old style configuration uses a single file, normally installed as <code class="filename">/usr/local/etc/openldap/slapd.conf</code>, the new style uses a slapd backend database to store the configuration. The configuration database normally resides in the <code class="filename">/usr/local/etc/openldap/slapd.d/</code> directory.
+ </div><div class="para">
+ The following directives are also valid for establishing SSL. In addition to TLS directives, you need to enable a port dedicated to SSL on the server side – typically it is port 636. To do so, edit the <code class="filename">/etc/sysconfig/slapd</code> file and append the <code class="literal">ldaps:///</code> string to the list of URLs specified with the <code class="option">SLAPD_URLS</code> directive.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">olcTLSCACertificateFile</code> </span></dt><dd><div class="para">
+ The <code class="option">olcTLSCACertificateFile</code> directive specifies the file encoded with Privacy-Enhanced Mail (PEM) schema that contains trusted CA certificates. The directive takes the following form:
+ </div><pre class="synopsis"><code class="option">olcTLSCACertificateFile</code>: <em class="replaceable"><code>path</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> either with a path to the CA certificate file, or, if you use Mozilla NSS, with a certificate name.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">olcTLSCACertificatePath</code> </span></dt><dd><div class="para">
+ The <code class="option">olcTLSCACertificatePath</code> directive specifies the path to a directory containing individual CA certificates in separate files. This directory must be specially managed with the OpenSSL <span class="application"><strong>c_rehash</strong></span> utility that generates symbolic links with the hashed names that point to the actual certificate files. In general, it is simpler to use the <code class="option">olcTLSCACertificateFile</code> directive instead.
+ </div><div class="para">
+ If Mozilla NSS is used, <code class="option">olcTLSCACertificatePath</code> accepts a path to the Mozilla NSS database (as shown in <a class="xref" href="ch-Directory_Servers.html#ex-using_olcTLSCACertificatePath_with_Mozilla_NSS">Example 11.13, “Using olcTLSCACertificatePath with Mozilla NSS”</a>). In such a case, <span class="application"><strong>c_rehash</strong></span> is not needed.
+ </div><div class="para">
+ The directive takes the following form:
+ </div><pre class="synopsis"><code class="option">olcTLSCACertificatePath</code>: <em class="replaceable"><code>path</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a path to the directory containing the CA certificate files, or with a path to a Mozilla NSS database file.
+ </div><div class="example" id="ex-using_olcTLSCACertificatePath_with_Mozilla_NSS"><h6>Example 11.13. Using olcTLSCACertificatePath with Mozilla NSS</h6><div class="example-contents"><div class="para">
+ With Mozilla NSS, the <code class="option">olcTLSCACertificatePath</code> directive specifies the path of the directory containing the NSS certificate and key database files. For example:
+ </div><pre class="synopsis"><code class="option">olcTLSCACertificatePath</code>: <code class="filename">sql:/home/nssdb/sharednssdb</code></pre><div class="para">
+ The <code class="command">certutil</code> command is used to add a CA certificate to these NSS database files:
+ </div><pre class="synopsis"><code class="command">certutil</code> <code class="option">-d</code> <code class="filename">sql:/home/nssdb/sharednssdb</code> <code class="option">-A</code> <code class="option">-n</code> "<em class="replaceable"><code>CA_certificate</code></em>" <code class="option">-t</code> <code class="literal">CT,,</code> <code class="option">-a</code> <code class="option">-i</code> <code class="filename">certificate.pem</code></pre><div class="para">
+ The above command adds a CA certificate stored in a PEM-formatted file named <em class="replaceable"><code>certificate.pem</code></em>. The <code class="option">-d</code> option specifies the database directory containing the certificate and key database files, the <code class="option">-n</code> option sets a name for the certificate, <code class="option">-t</code> <code class="literal">CT,,</code> means that the certificate is trusted to be used in TLS clients and servers. The <code class="option">-A</code> option adds an existing certificate to a certificate database, the <code class="option">-a</code> option allows the use of ASCII format for input or output, and the <code class="option">-i</code> option passes the <code class="filename">certificate.pem</code> input file to the command.
+ </div></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <code class="option">olcTLSCertificateFile</code> </span></dt><dd><div class="para">
+ The <code class="option">olcTLSCertificateFile</code> directive specifies the file that contains the <code class="systemitem">slapd</code> server certificate. The directive takes the following form:
+ </div><pre class="synopsis"><code class="option">olcTLSCertificateFile</code>: <em class="replaceable"><code>path</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a path to the <code class="systemitem">slapd</code> server certificate file, or, if you use Mozilla NSS, with a certificate name.
+ </div><div class="example" id="ex-using_olcTLSCertificateFile_with_Mozilla_NSS"><h6>Example 11.14. Using olcTLSCertificateFile with Mozilla NSS</h6><div class="example-contents"><div class="para">
+ When using Mozilla NSS with certificate and key database files specified with the <code class="option">olcTLSCACertificatePath</code> directive, <code class="option">olcTLSCertificateFile</code> is used to specify the name of the certificate to use. First, execute the following command to view a list of certificates available in your NSS database file:
+ </div><pre class="synopsis"><code class="command">certutil</code> <code class="option">-d</code> <code class="filename">sql:/home/nssdb/sharednssdb</code> <code class="option">-L</code></pre><div class="para">
+ Select a certificate from the list and pass its name to <code class="option">olcTLSCertificateFile</code>. For example:
+ </div><pre class="synopsis"><code class="command">olcTLSCertificateFile</code> <span class="emphasis"><em>slapd_cert</em></span></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <code class="option">olcTLSCertificateKeyFile</code> </span></dt><dd><div class="para">
+ The <code class="option">olcTLSCertificateKeyFile</code> directive specifies the file that contains the private key that matches the certificate stored in the file specified with <code class="option">olcTLSCertificateFile</code>. Note that the current implementation does not support encrypted private keys, and therefore the containing file must be sufficiently protected. The directive takes the following form:
+ </div><pre class="synopsis"><code class="option">olcTLSCertificateKeyFile</code>: <em class="replaceable"><code>path</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a path to the private key file if you use PEM certificates. When using Mozilla NSS, <em class="replaceable"><code>path</code></em> stands for the name of a file that contains the password for the key for the certificate specified with the <code class="option">olcTLSCertificateFile</code> directive (see <a class="xref" href="ch-Directory_Servers.html#ex-using_olcTLSCertificateKeyFile_with_Mozilla_NSS">Example 11.15, “Using olcTLSCertificateKeyFile with Mozilla NSS”</a>).
+ </div><div class="example" id="ex-using_olcTLSCertificateKeyFile_with_Mozilla_NSS"><h6>Example 11.15. Using olcTLSCertificateKeyFile with Mozilla NSS</h6><div class="example-contents"><div class="para">
+ When using Mozilla NSS, this directive specifies the name of a file that contains the password for the key for the certificate specified with <code class="option">olcTLSCertificateFile</code>:
+ </div><pre class="synopsis"><code class="option">olcTLSCertificateKeyFile</code>: <span class="emphasis"><em>slapd_cert_key</em></span></pre><div class="para">
+ The <code class="command">modutil</code> command can be used to turn off password protection or to change the password for NSS database files. For example:
+ </div><pre class="synopsis"><code class="command">modutil</code> <code class="option">-dbdir</code> <code class="filename">sql:/home/nssdb/sharednssdb</code> <code class="option">-changepw</code></pre></div></div><br class="example-break" /></dd></dl></div><h5 id="br-client_configuration">Client Configuration</h5><div class="para">
+ Specify the following directives in the <code class="filename">/etc/openldap/ldap.conf</code> configuration file on the client system. Most of these directives are parallel to the server configuration options. Directives in<code class="filename">/etc/openldap/ldap.conf</code> are configured on a system-wide basis, however, individual users may override them in their <code class="filename">~/.ldaprc</code> files.
+ </div><div class="para">
+ The same directives can be used to establish an SSL connection. The <code class="literal">ldaps://</code> string must be used instead of <code class="literal">ldap://</code> in OpenLDAP commands such as <code class="command">ldapsearch</code>. This forces commands to use the default port for SSL, port 636, configured on the server.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">TLS_CACERT</code> </span></dt><dd><div class="para">
+ The <code class="option">TLS_CACERT</code> directive specifies a file containing certificates for all of the Certificate Authorities the client will recognize. This is equivalent to the <code class="option">olcTLSCACertificateFile</code> directive on a server. <code class="option">TLS_CACERT</code> should always be specified before <code class="option">TLS_CACERTDIR</code> in <code class="filename">/etc/openldap/ldap.conf</code>. The directive takes the following form:
+ </div><pre class="synopsis"><code class="option">TLS_CACERT</code> <em class="replaceable"><code>path</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a path to the CA certificate file.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">TLS_CACERTDIR</code> </span></dt><dd><div class="para">
+ The <code class="option">TLS_CACERTDIR</code> directive specifies the path to a directory that contains Certificate Authority certificates in separate files. As with <code class="option">olcTLSCACertificatePath</code> on a server, the specified directory must be managed with the OpenSSL <span class="application"><strong>c_rehash</strong></span> utility. Path to Mozilla NSS database file is also accepted, <span class="application"><strong>c_rehash</strong></span> is not needed in such case. The directive takes the following form:
+ </div><pre class="synopsis"><code class="option">TLS_CACERTDIR</code> <em class="replaceable"><code>directory</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>directory</code></em> with a path to the directory containing CA certificate files. With Mozilla NSS, <em class="replaceable"><code>directory</code></em> stands for a path to the certificate or key database file.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">TLS_CERT</code> </span></dt><dd><div class="para">
+ The <code class="option">TLS_CERT</code> specifies the file that contains a client certificate. This directive can only be specified in a user's <code class="filename">~/.ldaprc</code> file. With Mozilla NSS, this directive specifies the name of the certificate to be chosen from the database specified with the aforementioned <code class="option">TLS_CACERTDIR</code> directive. The directive takes the following form:
+ </div><pre class="synopsis"><code class="option">TLS_CERT</code> <em class="replaceable"><code>path</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a path to the client certificate file, or with a name of a certificate from the NSS database.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">TLS_KEY</code> </span></dt><dd><div class="para">
+ The <code class="option">TLS_KEY</code> specifies the file that contains the private key that matches the certificate stored in the file specified with the <code class="option">TLS_CERT</code> directive. As with <code class="option">olcTLSCertificateFile</code> on a server, encrypted key files are not supported, so the file itself must be carefully protected. This option is only configurable in a user's <code class="filename">~/.ldaprc</code> file.
+ </div><div class="para">
+ When using Mozilla NSS, <code class="option">TLS_KEY</code> specifies the name of a file that contains the password for the private key that protects the certificate specified with the <code class="option">TLS_CERT</code> directive. Similarly to the <code class="option">olcTLSCertificateKeyFile</code> directive on a server (see <a class="xref" href="ch-Directory_Servers.html#ex-using_olcTLSCertificateKeyFile_with_Mozilla_NSS">Example 11.15, “Using olcTLSCertificateKeyFile with Mozilla NSS”</a>), you can use the <code class="command">modutil</code> command to manage this password.
+ </div><div class="para">
+ The <code class="option">TLS_KEY</code> directive takes the following form:
+ </div><pre class="synopsis"><code class="option">TLS_KEY</code> <em class="replaceable"><code>path</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a path to the client certificate file or with a name of the password file in the NSS database.
+ </div></dd></dl></div></div><div class="section" id="s3-setting_up_replication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.3.5. Setting Up Replication</h4></div></div></div><a id="idm261758771856" class="indexterm"></a><a id="idm261758772016" class="indexterm"></a><a id="idm261747156192" class="indexterm"></a><div class="para">
+ Replication is the process of copying updates from one LDAP server (<span class="emphasis"><em>provider</em></span>) to one or more other servers or clients (<span class="emphasis"><em>consumers</em></span>). A provider replicates directory updates to consumers, the received updates can be further propagated by the consumer to other servers, so a consumer can also act simultaneously as a provider. Also, a consumer does not have to be an LDAP server, it may be just an LDAP client. In OpenLDAP, you can use several replication modes, most notable are <span class="emphasis"><em>mirror</em></span> and <span class="emphasis"><em>sync</em></span>. For more information on OpenLDAP replication modes, see the <span class="emphasis"><em>OpenLDAP Software Administrator's Guide</em></span> installed with <span class="package">openldap-servers</span> package (see <a class="xref" href="ch-Directory_Servers.html#bh-Installed_Documentation_OpenLDAP">the section called “Installed Docume
ntation”</a>).
+ </div><div class="para">
+ To enable a chosen replication mode, use one of the following directives in <code class="filename">/etc/openldap/slapd.d/</code> on both provider and consumers.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">olcMirrorMode</code> </span></dt><dd><div class="para">
+ The <code class="option">olcMirrorMode</code> directive enables the mirror replication mode. It takes the following form:
+ </div><pre class="synopsis"><code class="option">olcMirrorMode</code> <code class="option">on</code></pre><div class="para">
+ This option needs to be specified both on provider and consumers. Also a <code class="option">serverID</code> must be specified along with <code class="option">syncrepl</code> options. Find a detailed example in the <span class="emphasis"><em>18.3.4. MirrorMode</em></span> section of the <span class="emphasis"><em>OpenLDAP Software Administrator's Guide</em></span> (see <a class="xref" href="ch-Directory_Servers.html#bh-Installed_Documentation_OpenLDAP">the section called “Installed Documentation”</a>).
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">olcSyncrepl</code> </span></dt><dd><div class="para">
+ The <code class="option">olcSyncrepl</code> directive enables the sync replication mode. It takes the following form:
+ </div><pre class="synopsis"><code class="option">olcSyncrepl</code> <code class="option">on</code></pre><div class="para">
+ The sync replication mode requires a specific configuration on both the provider and the consumers. This configuration is thoroughly described in the <span class="emphasis"><em>18.3.1. Syncrepl</em></span> section of the <span class="emphasis"><em>OpenLDAP Software Administrator's Guide</em></span> (see <a class="xref" href="ch-Directory_Servers.html#bh-Installed_Documentation_OpenLDAP">the section called “Installed Documentation”</a>).
+ </div></dd></dl></div></div><div class="section" id="s3-loading_modules_or_backends"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.3.6. Loading Modules and Backends</h4></div></div></div><a id="idm261756867024" class="indexterm"></a><a id="idm261756869040" class="indexterm"></a><a id="idm261756871248" class="indexterm"></a><a id="idm261756872688" class="indexterm"></a><div class="para">
+ You can enhance the <code class="systemitem">slapd</code> service with dynamically loaded modules. Support for these modules must be enabled with the <code class="option">--enable-modules</code> option when configuring <code class="systemitem">slapd</code>. Modules are stored in files with the <span class="emphasis"><em>.la</em></span> extension:
+ </div><pre class="synopsis"><em class="replaceable"><code>module_name</code></em>.la</pre><div class="para">
+ <em class="firstterm">Backends</em> store or retrieve data in response to LDAP requests. Backends may be compiled statically into <code class="systemitem">slapd</code>, or when module support is enabled, they may be dynamically loaded. In the latter case, the following naming convention is applied:
+ </div><pre class="synopsis">back_<em class="replaceable"><code>backend_name</code></em>.la</pre><div class="para">
+ To load a module or a backend, use the following directive in <code class="filename">/etc/openldap/slapd.d/</code>:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">olcModuleLoad</code> </span></dt><dd><div class="para">
+ The <code class="option">olcModuleLoad</code> directive specifies a dynamically loadable module to load. It takes the following form:
+ </div><pre class="synopsis"><code class="option">olcModuleLoad</code>: <em class="replaceable"><code>module</code></em></pre><div class="para">
+ Here, <em class="replaceable"><code>module</code></em> stands either for a file containing the module, or a backend, that will be loaded.
+ </div></dd></dl></div></div></div><div class="section" id="s2-selinux-openldap"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.1.4. SELinux Policy for Applications Using LDAP</h3></div></div></div><div class="para">
+ SELinux is an implementation of a mandatory access control mechanism in the Linux kernel. By default, SELinux prevents applications from accessing an OpenLDAP server. To enable authentication through LDAP, which is required by several applications, the <code class="systemitem">allow_ypbind</code> SELinux Boolean needs to be enabled. Certain applications also demand an enabled <code class="systemitem">authlogin_nsswitch_use_ldap</code> Boolean in this scenario. Execute the following commands to enable the aforementioned Booleans:
+ </div><pre class="synopsis">~]# <code class="command">setsebool</code> <code class="option">-P</code> <code class="option">allow_ypbind</code>=<code class="literal">1</code></pre><pre class="synopsis">~]# <code class="command">setsebool</code> <code class="option">-P</code> <code class="option">authlogin_nsswitch_use_ldap</code>=<code class="literal">1</code></pre><div class="para">
+ The <code class="option">-P</code> option makes this setting persistent across system reboots. See the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SELinux_Users_and_Administrators_Guide/">Red Hat Enterprise Linux 7 SELinux User's and Administrator's Guide</a> for more detailed information about SELinux.
+ </div></div><div class="section" id="s2-ldap-running"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.1.5. Running an OpenLDAP Server</h3></div></div></div><a id="idm261779246176" class="indexterm"></a><div class="para">
+ This section describes how to start, stop, restart, and check the current status of the <span class="application"><strong>Standalone LDAP Daemon</strong></span>. For more information on how to manage system services in general, see <a class="xref" href="ch-Services_and_Daemons.html">Chapter 6, <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">11.1.5.1. Starting the Service</h4></div></div></div><a id="idm261749081792" class="indexterm"></a><div class="para">
+ To start the <code class="systemitem">slapd</code> service in the current session, type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">systemctl start slapd.service</code></pre><div class="para">
+ To configure the service to start automatically at the boot time, use the following command as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">systemctl enable slapd.service</code></pre><div class="para">
See <a class="xref" href="ch-Services_and_Daemons.html">Chapter 6, <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">11.1.4.2. Stopping the Service</h4></div></div></div><a id="idm225501373120" 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">
+ </div></div><div class="section" id="s3-ldap-running-stopping"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.5.2. Stopping the Service</h4></div></div></div><a id="idm261749088448" class="indexterm"></a><div class="para">
+ To stop the running <code class="systemitem">slapd</code> service in the current session, type the following at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">systemctl stop slapd.service</code></pre><div class="para">
+ To prevent the service from starting automatically at the boot time, type as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">systemctl disable slapd.service</code>
+rm '/etc/systemd/system/multi-user.target.wants/slapd.service'</pre><div class="para">
See <a class="xref" href="ch-Services_and_Daemons.html">Chapter 6, <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">11.1.4.3. Restarting the Service</h4></div></div></div><a id="idm225474381712" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-ldap-running-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.5.3. Restarting the Service</h4></div></div></div><a id="idm261744768528" 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">11.1.4.4. Checking the Service Status</h4></div></div></div><a id="idm225474386624" 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">11.1.5. Configuring a System to Authenticate Using OpenLDAP</h3></div></div></div><div class="para">
+ </div><pre class="screen">~]# <code class="command">systemctl restart slapd.service</code></pre><div class="para">
+ This stops the service and immediately starts it again. Use this command to reload the configuration.
+ </div></div><div class="section" id="s3-ldap-running-status"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.5.4. Verifying the Service Status</h4></div></div></div><a id="idm261744774736" class="indexterm"></a><div class="para">
+ To verify that the <code class="systemitem">slapd</code> service is running, type the following at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">systemctl is-active slapd.service</code>
+active</pre></div></div><div class="section" id="s2-ldap-pam"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.1.6. 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 11.1.2, “Installing the OpenLDAP Suite”</a> and <a class="xref" href="ch-Directory_Servers.html#s2-ldap-configuration">Section 11.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="section" id="s3-ldap-migrationtools"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.5.1. Migrating Old Authentication Information to LDAP Format</h4></div></div></div><a id="idm225461639504" class="indexterm"></a><div class="para">
+ </div><pre class="screen">~]# <code class="command">yum install openldap openldap-clients nss-pam-ldapd</code></pre><div class="section" id="s3-ldap-migrationtools"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">11.1.6.1. Migrating Old Authentication Information to LDAP Format</h4></div></div></div><a id="idm261725502528" 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">
+ </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";
@@ -378,9 +476,9 @@ $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>
+ </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 11.8, “Commonly used LDAP migration scripts”</a>.
+ To decide which script to run in order to migrate the user database, see <a class="xref" href="ch-Directory_Servers.html#table-ldap-migrationtools">Table 11.8, “Commonly used LDAP migration scripts”</a>.
</div><div class="table" id="table-ldap-migrationtools"><h6>Table 11.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 class="">
Existing Name Service
</th><th class="">
@@ -424,59 +522,59 @@ $DEFAULT_BASE = "dc=example,dc=com";</pre><div class="para">
</td><td class="">
<code class="filename">migrate_all_nis_offline.sh</code>
</td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
- For more information on how to use these scripts, refer to the <code class="filename">README</code> and the <code class="filename">migration-tools.txt</code> files in the <code class="filename">/usr/share/doc/migrationtools/</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">11.1.6. Additional Resources</h3></div></div></div><div class="para">
+ For more information on how to use these scripts, see the <code class="filename">README</code> and the <code class="filename">migration-tools.txt</code> files in the <code class="filename">/usr/share/doc/migrationtools/</code> directory.
+ </div></div></div><div class="section" id="s2-ldap-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">11.1.7. 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">11.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 class="variablelist"><dt class="varlistentry"><span class="term"><code class="filename">/usr/share/doc/openldap-servers/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/README.schema</code></span></dt><dd><div class="para">
- A README file containing the description of installed schema files.
- </div></dd></dl></div><div class="para">
- Additionally, there is also a number of manual pages that are installed with the <span class="package">openldap</span>, <span class="package">openldap-servers</span>, and <span class="package">openldap-clients</span> packages:
- </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">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">11.1.6.2. Useful Websites</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.openldap.org/doc/admin24/">http://www.openldap.org/doc/admin24/</a></span></dt><dd><div class="para">
- 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://www.kingsmountain.com/ldapRoadmap.shtml</a></span></dt><dd><div class="para">
- Jeff Hodges' <em class="citetitle">LDAP Roadmap & FAQ</em> containing links to several useful resources and emerging news concerning the LDAP protocol.
- </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.ldapman.org/articles/">http://www.ldapman.org/articles/</a></span></dt><dd><div class="para">
- A collection of articles that offer a good introduction to LDAP, including methods to design a directory tree and customizing directory structures.
- </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.padl.com/">http://www.padl.com/</a></span></dt><dd><div class="para">
- 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">11.1.6.3. Related Books</h4></div></div></div><div class="variablelist"><dl class="variablelist"><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>10.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 12. File and Print Servers</a></li></ul></body></html>
\ No newline at end of file
+ </div><h3 id="bh-Installed_Documentation_OpenLDAP">Installed Documentation</h3><div class="para">
+ The following documentation is installed with the <span class="package">openldap-servers</span> package:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/openldap-servers/guide.html</code> — A copy of the <em class="citetitle">OpenLDAP Software Administrator's Guide</em>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/openldap-servers/README.schema</code> — A README file containing the description of installed schema files.
+ </div></li></ul></div><div class="para">
+ Additionally, there is also a number of manual pages that are installed with the <span class="package">openldap</span>, <span class="package">openldap-servers</span>, and <span class="package">openldap-clients</span> packages:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Client Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldapadd</span>(1)</span> — The manual page for the <code class="command">ldapadd</code> command describes how to add entries to an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldapdelete</span>(1)</span> — The manual page for the <code class="command">ldapdelete</code> command describes how to delete entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldapmodify</span>(1)</span> — The manual page for the <code class="command">ldapmodify</code> command describes how to modify entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldapsearch</span>(1)</span> — The manual page for the <code class="command">ldapsearch</code> command describes how to search for entries within an LDAP directory.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldappasswd</span>(1)</span> — The manual page for the <code class="command">ldappasswd</code> command describes how to set or change the password of an LDAP user.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldapcompare</span>(1)</span> — Describes how to use the <code class="command">ldapcompare</code> tool.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldapwhoami</span>(1)</span> — Describes how to use the <code class="command">ldapwhoami</code> tool.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldapmodrdn</span>(1)</span> — Describes how to modify the RDNs of entries.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Server Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">slapd</span>(8C)</span> — Describes command line options for the LDAP server.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Administrative Applications</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">slapadd</span>(8C)</span> — Describes command line options used to add entries to a <code class="command">slapd</code> database.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">slapcat</span>(8C)</span> — Describes command line options used to generate an LDIF file from a <code class="command">slapd</code> database.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">slapindex</span>(8C)</span> — Describes command line options used to regenerate an index based upon the contents of a <code class="command">slapd</code> database.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">slappasswd</span>(8C)</span> — Describes command line options used to generate user passwords for LDAP directories.
+ </div></li></ul></div></dd><dt class="varlistentry"><span class="term">Configuration Files</span></dt><dd><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">ldap.conf</span>(5)</span> — The manual page for the <code class="filename">ldap.conf</code> file describes the format and options available within the configuration file for LDAP clients.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">slapd-config</span>(5)</span> — Describes the format and options available within the <code class="filename">/etc/openldap/slapd.d</code> configuration directory.
+ </div></li></ul></div></dd></dl></div><h3 id="bh-Online_Documentation_OpenLDAP">Online Documentation</h3><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://www.openldap.org/doc/admin24/">http://www.openldap.org/doc/admin24/</a></span></dt><dd><div 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://www.kingsmountain.com/ldapRoadmap.shtml</a></span></dt><dd><div class="para">
+ Jeff Hodges' <em class="citetitle">LDAP Roadmap & FAQ</em> containing links to several useful resources and emerging news concerning the LDAP protocol.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.ldapman.org/articles/">http://www.ldapman.org/articles/</a></span></dt><dd><div class="para">
+ A collection of articles that offer a good introduction to LDAP, including methods to design a directory tree and customizing directory structures.
+ </div></dd><dt class="varlistentry"><span class="term"><a href="http://www.padl.com/">http://www.padl.com/</a></span></dt><dd><div class="para">
+ 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"><h3 class="title">11.1.8. Related Books</h3></div></div></div><div class="variablelist"><dl class="variablelist"><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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-related-books.html"><strong>Prev</strong>10.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 12. File and Print Servers</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-File_and_Print_Servers.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-File_and_Print_Servers.html
index f2d6ba9..90ab452 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-File_and_Print_Servers.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-File_and_Print_Servers.html
@@ -6,17 +6,17 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Servers.html" title="Part IV. Servers" /><link rel="prev" href="ch-Directory_Servers.html" title="Chapter 11. Directory Servers" /><link rel="next" href="s1-FTP.html" title="12.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>N
ext</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 12. File and Print Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s1-Samba">12.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="ch-File_and_Print_Servers.html#samba-rgs-overview">12.1.1. Introduction to Samba</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-daemons">12.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">12.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">12.1.4. Configuring a Samba Server</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-
startstop">12.1.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-servers">12.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">12.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">12.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">12.1.9. Samba Network Browsing</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-cups">12.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">12.1.11. Samba Distribution Programs</a></span></dt><dt><span class="section"><a href="ch-File_and_P
rint_Servers.html#s2-samba-resources">12.1.12. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="s1-FTP.html">12.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="s1-FTP.html#s2-ftp-protocol">12.2.1. The File Transfer Protocol</a></span></dt><dt><span class="section"><a href="s2-ftp-servers.html">12.2.2. FTP Servers</a></span></dt><dt><span class="section"><a href="s3-ftp-vsftpd-conf.html">12.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-start.html">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf.html">12.2.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dt><span class="section"><a href="s2-ftp-resources.html">12.2.6. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Printer_Configuration.html">12.3.
Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">12.3.1. Starting the Printer Configuration Tool</a></span></dt><dt><span class="section"><a href="sec-Setting_Printer.html">12.3.2. Starting Printer Setup</a></span></dt><dt><span class="section"><a href="sec-Adding_Other_Printer.html">12.3.3. Adding a Local Printer</a></span></dt><dt><span class="section"><a href="s1-printing-jetdirect-printer.html">12.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="s1-printing-ipp-printer.html">12.3.5. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="sec-printing-LPDLPR-printer.html">12.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="s1-printing-smb-printer.html">12.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="s1-printing-select-model.html">12.3.8. Sele
cting the Printer Model and Finishing</a></span></dt><dt><span class="section"><a href="s1-printing-test-page.html">12.3.9. Printing a Test Page</a></span></dt><dt><span class="section"><a href="s1-printing-edit.html">12.3.10. Modifying Existing Printers</a></span></dt><dt><span class="section"><a href="s1-printing-additional-resources.html">12.3.11. Additional Resources</a></span></dt></dl></dd></dl></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Servers.html" title="Part IV. Servers" /><link rel="prev" href="ch-Directory_Servers.html" title="Chapter 11. Directory Servers" /><link rel="next" href="s1-FTP.html" title="12.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>N
ext</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 12. File and Print Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s1-Samba">12.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="ch-File_and_Print_Servers.html#samba-rgs-overview">12.1.1. Introduction to Samba</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-daemons">12.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">12.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">12.1.4. Configuring a Samba Server</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-
startstop">12.1.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-servers">12.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">12.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">12.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">12.1.9. Samba Network Browsing</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-cups">12.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">12.1.11. Samba Distribution Programs</a></span></dt><dt><span class="section"><a href="ch-File_and_P
rint_Servers.html#s2-samba-resources">12.1.12. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="s1-FTP.html">12.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="s1-FTP.html#s2-ftp-protocol">12.2.1. The File Transfer Protocol</a></span></dt><dt><span class="section"><a href="s2-ftp-servers.html">12.2.2. FTP Servers</a></span></dt><dt><span class="section"><a href="s3-ftp-vsftpd-conf.html">12.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-start.html">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf.html">12.2.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dt><span class="section"><a href="s2-ftp-resources.html">12.2.6. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Printer_Configuration.html">12.3.
Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">12.3.1. Starting the Printers Configuration Tool</a></span></dt><dt><span class="section"><a href="sec-Setting_Printer.html">12.3.2. Starting Printer Setup</a></span></dt><dt><span class="section"><a href="sec-Adding_Other_Printer.html">12.3.3. Adding a Local Printer</a></span></dt><dt><span class="section"><a href="s1-printing-jetdirect-printer.html">12.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="s1-printing-ipp-printer.html">12.3.5. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="sec-printing-LPDLPR-printer.html">12.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="s1-printing-smb-printer.html">12.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="s1-printing-select-model.html">12.3.8. Sel
ecting the Printer Model and Finishing</a></span></dt><dt><span class="section"><a href="s1-printing-test-page.html">12.3.9. Printing a Test Page</a></span></dt><dt><span class="section"><a href="s1-printing-edit.html">12.3.10. Modifying Existing Printers</a></span></dt><dt><span class="section"><a href="s1-printing-additional-resources.html">12.3.11. Additional Resources</a></span></dt></dl></dd></dl></div><div class="para">
This chapter guides you through the installation and configuration of <span class="application"><strong>Samba</strong></span>, an open source implementation of the <em class="firstterm">Server Message Block</em> (<acronym class="acronym">SMB</acronym>) and <em class="firstterm">common Internet file system</em> (<code class="systemitem">CIFS</code>) protocol, and <span class="application"><strong>vsftpd</strong></span>, the primary FTP server shipped with Fedora. Additionally, it explains how to use the <span class="application"><strong>Printer</strong></span> tool to configure printers.
- </div><div xml:lang="en-US" class="section" id="s1-Samba" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.1. Samba</h2></div></div></div><a id="idm225464157680" class="indexterm"></a><a id="idm225464161184" class="indexterm"></a><div class="para">
+ </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">12.1. Samba</h2></div></div></div><a id="idm261718819216" class="indexterm"></a><a id="idm261749435392" class="indexterm"></a><div class="para">
<span class="application"><strong>Samba</strong></span> is an open source implementation of the <em class="firstterm">server message block</em> (<code class="systemitem">SMB</code>) protocol. Modern versions of this protocol are also known as the <em class="firstterm">common Internet file system</em> (<code class="systemitem">CIFS</code>) protocol. It allows the networking of Microsoft <span class="trademark">Windows</span>®, Linux, UNIX, and other operating systems together, enabling access to Windows-based file and printer shares. Samba's use of <code class="systemitem">SMB</code> allows it to appear as a Windows server to Windows clients.
</div><div class="note"><div class="admonition_header"><h2>Installing the samba package</h2></div><div class="admonition"><div class="para">
In order to use <span class="application"><strong>Samba</strong></span>, first ensure the <span class="package">samba</span> package is installed on your system by running, as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">yum install samba</code></pre><div class="para">
For more information on installing packages with Yum, see <a class="xref" href="sec-Installing.html">Section 5.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">12.1.1. Introduction to Samba</h3></div></div></div><a id="idm225443225808" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="samba-rgs-overview"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.1.1. Introduction to Samba</h3></div></div></div><a id="idm261749444864" class="indexterm"></a><div class="para">
Fedora includes Samba version <code class="literal">4.1</code>:
- </div><div class="section" id="s3-samba-abilities"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.1.1. Samba Features</h4></div></div></div><a id="idm225443229184" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-abilities"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.1.1. Samba Features</h4></div></div></div><a id="idm261749448160" class="indexterm"></a><div class="para">
Samba is a powerful and versatile server application.
</div><div class="para">
What Samba can do:
@@ -42,25 +42,25 @@
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">12.1.2. Samba Daemons and Related Services</h3></div></div></div><a id="idm225446992320" class="indexterm"></a><div class="para">
+ </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">12.1.2. Samba Daemons and Related Services</h3></div></div></div><a id="idm261739619520" 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">12.1.2.1. Samba Daemons</h4></div></div></div><a id="idm225442230128" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-services"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.2.1. Samba Daemons</h4></div></div></div><a id="idm261739623168" class="indexterm"></a><div class="para">
Samba is comprised of three daemons (<code class="command">smbd</code>, <code class="command">nmbd</code>, and <code class="command">winbindd</code>). Three services (<code class="command">smb</code>, <code class="command">nmb</code>, and <code class="command">winbind</code>) control how the daemons are started, stopped, and other service-related features. These services act as different init scripts. Each daemon is listed in detail below, as well as which specific service has control over it.
- </div><h5 id="s4-samba-daemon-smbd"> <code class="command">smbd</code> </h5><a id="idm225442236032" class="indexterm"></a><div class="para">
+ </div><h5 id="s4-samba-daemon-smbd"> <code class="command">smbd</code> </h5><a id="idm261739629072" 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 id="s4-samba-daemon-nmbd"> <code class="command">nmbd</code> </h5><a id="idm225442294304" class="indexterm"></a><div class="para">
+ </div><h5 id="s4-samba-daemon-nmbd"> <code class="command">nmbd</code> </h5><a id="idm261722342000" class="indexterm"></a><div class="para">
The <code class="command">nmbd</code> server daemon understands and replies to NetBIOS name service requests such as those produced by SMB/CIFS in Windows-based systems. These systems include Windows 95/98/ME, Windows NT, Windows 2000, Windows XP, and LanManager clients. It also participates in the browsing protocols that make up the Windows <span class="guilabel"><strong>Network Neighborhood</strong></span> view. The default port that the server listens to for <code class="systemitem">NMB</code> traffic is <code class="systemitem">UDP</code> port <code class="systemitem">137</code>.
</div><div class="para">
The <code class="command">nmbd</code> daemon is controlled by the <code class="command">nmb</code> service.
- </div><h5 id="s4-samba-daemon-winbindd"> <code class="command">winbindd</code> </h5><a id="idm225442304080" class="indexterm"></a><div class="para">
+ </div><h5 id="s4-samba-daemon-winbindd"> <code class="command">winbindd</code> </h5><a id="idm261741168544" class="indexterm"></a><div class="para">
The <code class="command">winbind</code> service resolves user and group information received from a server running Windows NT, 2000, 2003, Windows Server 2008, or Windows Server 2012. This makes Windows user and group information understandable by UNIX platforms. This is achieved by using Microsoft RPC calls, <em class="firstterm">Pluggable Authentication Modules</em> (PAM), and the <em class="firstterm">Name Service Switch</em> (NSS). This allows Windows NT domain users to appear and operate as UNIX users on a UNIX machine. Though bundled with the Samba distribution, the <code class="command">winbind</code> service is controlled separately from the <code class="command">smb</code> service.
</div><div class="para">
The <code class="command">winbindd</code> daemon is controlled by the <code class="command">winbind</code> service and does not require the <code class="command">smb</code> service to be started in order to operate. <code class="command">winbindd</code> is also used when Samba is an Active Directory member, and may also be used on a Samba domain controller (to implement nested groups and interdomain trust). Because <code class="command">winbind</code> is a client-side service used to connect to Windows NT-based servers, further discussion of <code class="command">winbind</code> is beyond the scope of this chapter.
</div><div class="note"><div class="admonition_header"><h2>Obtaining a list of utilities that are shipped with Samba</h2></div><div class="admonition"><div class="para">
See <a class="xref" href="ch-File_and_Print_Servers.html#s2-samba-programs">Section 12.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">12.1.3. Connecting to a Samba Share</h3></div></div></div><a id="idm225439447872" class="indexterm"></a><div class="para">
+ </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">12.1.3. Connecting to a Samba Share</h3></div></div></div><a id="idm261741179520" 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
@@ -70,9 +70,9 @@
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">12.1.3.1. Command Line</h4></div></div></div><a id="idm225443298896" class="indexterm"></a><a id="idm225443296288" class="indexterm"></a><a id="idm225443298144" class="indexterm"></a><div class="para">
+ </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">12.1.3.1. Command Line</h4></div></div></div><a id="idm261739650816" class="indexterm"></a><a id="idm261739648048" class="indexterm"></a><a id="idm261739650656" 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="idm225442160976" class="indexterm"></a><a id="idm225442163072" class="indexterm"></a><div class="para">
+ </div><a id="idm261739654304" class="indexterm"></a><a id="idm261739656400" 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.
@@ -80,7 +80,7 @@
If you see the <code class="prompt">smb:\></code> prompt, you have successfully logged in. Once you are logged in, type <strong class="userinput"><code>help</code></strong> for a list of commands. If you want to browse the contents of your home directory, replace <em class="replaceable"><code>sharename</code></em> with your username. If the <code class="command">-U</code> switch is not used, the username of the current user is passed to the Samba server.
</div><div class="para">
To exit <code class="command">smbclient</code>, type <strong class="userinput"><code>exit</code></strong> at the <code class="prompt">smb:\></code> prompt.
- </div></div><div class="section" id="s2-samba-mounting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.3.2. Mounting the Share</h4></div></div></div><a id="idm225439234368" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-samba-mounting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.3.2. Mounting the Share</h4></div></div></div><a id="idm261758275168" 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>:
@@ -99,11 +99,11 @@
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">12.1.4. Configuring a Samba Server</h3></div></div></div><a id="idm225442985920" class="indexterm"></a><a id="idm225442987216" class="indexterm"></a><div class="para">
+ </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">12.1.4. Configuring a Samba Server</h3></div></div></div><a id="idm261743951440" class="indexterm"></a><a id="idm261743943552" class="indexterm"></a><div class="para">
The default configuration file (<code class="filename">/etc/samba/smb.conf</code>) allows users to view their home directories as a Samba share. It also shares all printers configured for the system as Samba shared printers. You can attach a printer to the system and print to it from the Windows machines on your network.
- </div><div class="section" id="s3-samba-configuring-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.4.1. Graphical Configuration</h4></div></div></div><a id="idm225442992032" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-configuring-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.4.1. Graphical Configuration</h4></div></div></div><a id="idm261743949344" class="indexterm"></a><div class="para">
To configure Samba using a graphical interface, use one of the available Samba graphical user interfaces. A list of available GUIs can be found at <a href="http://www.samba.org/samba/GUI/">http://www.samba.org/samba/GUI/</a>.
- </div></div><div class="section" id="s3-samba-configuring-cmdline"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.4.2. Command Line Configuration</h4></div></div></div><a id="idm225443062528" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-samba-configuring-cmdline"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.4.2. Command Line Configuration</h4></div></div></div><a id="idm261719002272" 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>
@@ -125,7 +125,7 @@ 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">12.1.4.3. Encrypted Passwords</h4></div></div></div><div class="para">
Encrypted passwords are enabled by default because it is more secure to use them. To create a user with an encrypted password, use the command <code class="command">smbpasswd -a <em class="replaceable"><code>username</code></em></code>.
- </div><a id="idm225443534320" class="indexterm"></a><a id="idm225443531200" class="indexterm"></a><a id="idm225443533232" class="indexterm"></a><a id="idm225443535104" class="indexterm"></a><a id="idm225443536304" class="indexterm"></a><a id="idm225443538000" class="indexterm"></a><a id="idm225442717456" 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">12.1.5. Starting and Stopping Samba</h3></div></div></div><a id="idm225442718208" class="indexterm"></a><a id="idm225442721200" class="indexterm"></a><a id="idm225442723232" class="indexterm"></a><a id="idm225442725120" class="indexterm"></a><a id="idm225442727152" class="indexterm"></a><div class="para">
+ </div><a id="idm261719010112" class="indexterm"></a><a id="idm261719013056" class="indexterm"></a><a id="idm261719013536" class="indexterm"></a><a id="idm261741739008" class="indexterm"></a><a id="idm261741739168" class="indexterm"></a><a id="idm261741740880" class="indexterm"></a><a id="idm261741742368" 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">12.1.5. Starting and Stopping Samba</h3></div></div></div><a id="idm261741745632" class="indexterm"></a><a id="idm261741749040" class="indexterm"></a><a id="idm261741750032" class="indexterm"></a><a id="idm261757721856" class="indexterm"></a><a id="idm261757728784" 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. Also, it is recommended to run <code class="systemitem">winbind</code> before <code class="systemitem">smbd</code>.
@@ -147,13 +147,13 @@ create mask = 0765</pre><div class="para">
By default, the <code class="command">smb</code> service does <span class="emphasis"><em>not</em></span> start automatically at boot time. To configure Samba to start at boot time, type the following at a shell prompt as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">systemctl enable smb.service</code></pre><div class="para">
See <a class="xref" href="ch-Services_and_Daemons.html">Chapter 6, <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">12.1.6. Samba Server Types and the <code class="filename">smb.conf</code> File</h3></div></div></div><a id="idm225470506496" class="indexterm"></a><a id="idm225470508176" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-samba-servers"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.1.6. Samba Server Types and the <code class="filename">smb.conf</code> File</h3></div></div></div><a id="idm261738872128" class="indexterm"></a><a id="idm261738872624" 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">12.1.6.1. Stand-alone Server</h4></div></div></div><a id="idm225479790128" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-standalone"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.6.1. Stand-alone Server</h4></div></div></div><a id="idm261735263248" 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 12.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">12.1.6.1.1. Anonymous Read-Only</h5></div></div></div><a id="idm225478428672" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s4-samba-standalone-anonreadonly"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.1.6.1.1. Anonymous Read-Only</h5></div></div></div><a id="idm261717207296" 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
@@ -163,7 +163,7 @@ security = share
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">12.1.6.1.2. Anonymous Read/Write</h5></div></div></div><a id="idm225478433056" class="indexterm"></a><div class="para">
+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">12.1.6.1.2. Anonymous Read/Write</h5></div></div></div><a id="idm261717211680" 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.
@@ -177,7 +177,7 @@ 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">12.1.6.1.3. Anonymous Print Server</h5></div></div></div><a id="idm225479789232" class="indexterm"></a><div class="para">
+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">12.1.6.1.3. Anonymous Print Server</h5></div></div></div><a id="idm261735262656" 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
@@ -193,7 +193,7 @@ 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">12.1.6.1.4. Secure Read/Write File and Print Server</h5></div></div></div><a id="idm225479796896" class="indexterm"></a><div class="para">
+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">12.1.6.1.4. Secure Read/Write File and Print Server</h5></div></div></div><a id="idm261735269696" 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
@@ -222,9 +222,9 @@ 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">12.1.6.2. Domain Member Server</h4></div></div></div><a id="idm225443625744" class="indexterm"></a><div class="para">
+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">12.1.6.2. Domain Member Server</h4></div></div></div><a id="idm261754713600" 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">12.1.6.2.1. Active Directory Domain Member Server</h5></div></div></div><a id="idm225443629664" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s4-samba-domain-member-ads"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.1.6.2.1. Active Directory Domain Member Server</h5></div></div></div><a id="idm261754718752" 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
@@ -251,7 +251,7 @@ password server = kerberos.example.com</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">12.1.6.2.2. Windows NT4-based Domain Member Server</h5></div></div></div><a id="idm225479199936" class="indexterm"></a><div class="para">
+ </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">12.1.6.2.2. Windows NT4-based Domain Member Server</h5></div></div></div><a id="idm261714292080" 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
@@ -273,13 +273,13 @@ guest ok = Yes</pre><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">12.1.6.3. Domain Controller</h4></div></div></div><a id="idm225477758496" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s3-samba-domain-controller"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.6.3. Domain Controller</h4></div></div></div><a id="idm261757614304" 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">12.1.6.3.1. Primary Domain Controller (PDC) using <code class="command">tdbsam</code> </h5></div></div></div><a id="idm225477467952" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s4-samba-pdc-tdbsam"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.1.6.3.1. Primary Domain Controller (PDC) using <code class="command">tdbsam</code> </h5></div></div></div><a id="idm261738578112" 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 12.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.
@@ -353,11 +353,11 @@ domain master = Yes
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">12.1.6.3.2. Primary Domain Controller (PDC) with Active Directory</h5></div></div></div><a id="idm225477490960" class="indexterm"></a><div class="para">
+ </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">12.1.6.3.2. Primary Domain Controller (PDC) with Active Directory</h5></div></div></div><a id="idm261723590736" 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">12.1.7. Samba Security Modes</h3></div></div></div><a id="idm225479782256" class="indexterm"></a><div class="para">
+ </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">12.1.7. Samba Security Modes</h3></div></div></div><a id="idm261757722160" 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">12.1.7.1. User-Level Security</h4></div></div></div><a id="idm225437839952" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-user-level"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.7.1. User-Level Security</h4></div></div></div><a id="idm261726542208" 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:
@@ -366,13 +366,13 @@ domain master = Yes
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">12.1.7.1.1. Domain Security Mode (User-Level Security)</h5></div></div></div><a id="idm225442727840" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-domain-security-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.1.7.1.1. Domain Security Mode (User-Level Security)</h5></div></div></div><a id="idm261755804304" 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">12.1.7.1.2. Active Directory Security Mode (User-Level Security)</h5></div></div></div><a id="idm225458652800" class="indexterm"></a><div class="para">
+...</pre></div><div class="section" id="s3-samba-ads-security-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.1.7.1.2. Active Directory Security Mode (User-Level Security)</h5></div></div></div><a id="idm261747168432" 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:
@@ -381,7 +381,7 @@ workgroup = MARKETING
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">12.1.7.1.3. Server Security Mode (User-Level Security)</h5></div></div></div><a id="idm225463808000" class="indexterm"></a><div class="para">
+...</pre></div><div class="section" id="s3-samba-server-security-mode"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.1.7.1.3. Server Security Mode (User-Level Security)</h5></div></div></div><a id="idm261757278848" 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.
@@ -392,18 +392,18 @@ password server = kerberos.example.com
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">12.1.7.2. Share-Level Security</h4></div></div></div><a id="idm225474441376" class="indexterm"></a><div class="para">
+...</pre></div></div><div class="section" id="s3-samba-share-level"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.7.2. Share-Level Security</h4></div></div></div><a id="idm261744753088" 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">12.1.8. Samba Account Information Databases</h3></div></div></div><a id="idm225480957712" class="indexterm"></a><div class="para">
+...</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">12.1.8. Samba Account Information Databases</h3></div></div></div><a id="idm261725711632" 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="idm225481010352" class="indexterm"></a><a id="idm225453172960" class="indexterm"></a><a id="idm225467750480" class="indexterm"></a><a id="idm225462899904" class="indexterm"></a><a id="idm225471430320" class="indexterm"></a><a id="idm225506927024" class="indexterm"></a><a id="idm225443068208" class="indexterm"></a><a id="idm225468795040" class="indexterm"></a><a id="idm225499977600" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Plain Text</span></dt><dd><div class="para">
+ </div><a id="idm261780116368" class="indexterm"></a><a id="idm261783323712" class="indexterm"></a><a id="idm261783116464" class="indexterm"></a><a id="idm261745026096" class="indexterm"></a><a id="idm261752132528" class="indexterm"></a><a id="idm261757893584" class="indexterm"></a><a id="idm261755721024" class="indexterm"></a><a id="idm261784234640" class="indexterm"></a><a id="idm261726705040" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Plain Text</span></dt><dd><div class="para">
Plain text back ends are nothing more than the <code class="command">/etc/passwd</code> type back ends. With a plain text back end, all usernames and passwords are sent unencrypted between the client and the Samba server. This method is very unsecure and is not recommended for use by any means. It is possible that different Windows clients connecting to the Samba server with plain text passwords cannot support such an authentication method.
</div></dd><dt class="varlistentry"><span class="term"> <code class="command">smbpasswd</code> </span></dt><dd><div class="para">
A popular back end used in previous Samba packages, the <code class="command">smbpasswd</code> back end utilizes a plain ASCII text layout that includes the MS Windows LanMan and NT account, and encrypted password information. The <code class="command">smbpasswd</code> back end lacks the storage of the Windows NT/2000/2003 SAM extended controls. The <code class="command">smbpasswd</code> back end is not recommended because it does not scale well or hold any Windows information, such as RIDs for NT-based groups. The <code class="command">tdbsam</code> back end solves these issues for use in a smaller database (250 users), but is still not an enterprise-class solution.
@@ -421,17 +421,17 @@ security = share
As such, if you are using the <code class="command">ldapsam</code> back end for your Samba server, you will need to configure <code class="command">slapd</code> to include one of these schema file. See <a class="xref" href="ch-Directory_Servers.html#s3-ldap-configuration-schema">Section 11.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">12.1.9. Samba Network Browsing</h3></div></div></div><a id="idm225507377984" class="indexterm"></a><a id="idm225467499952" class="indexterm"></a><div class="para">
+ </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">12.1.9. Samba Network Browsing</h3></div></div></div><a id="idm261723130368" class="indexterm"></a><a id="idm261754616224" 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">12.1.9.1. Domain Browsing</h4></div></div></div><a id="idm225445488352" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-domain-browsing"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.9.1. Domain Browsing</h4></div></div></div><a id="idm261745672064" class="indexterm"></a><div class="para">
By default, a Windows server PDC for a domain is also the domain master browser for that domain. A Samba server must <span class="emphasis"><em>not</em></span> be set up as a domain master server in this type of situation.
</div><div class="para">
For subnets that do not include the Windows server PDC, a Samba server can be implemented as a local master browser. Configuring the <code class="filename">/etc/samba/smb.conf</code> file for a local master browser (or no browsing at all) in a domain controller environment is the same as workgroup configuration (see <a class="xref" href="ch-File_and_Print_Servers.html#s2-samba-configuring">Section 12.1.4, “Configuring a Samba Server”</a>).
- </div></div><div class="section" id="s3-samba-wins"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.9.2. WINS (Windows Internet Name Server)</h4></div></div></div><a id="idm225457256000" class="indexterm"></a><a id="idm225442348256" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-samba-wins"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.9.2. WINS (Windows Internet Name Server)</h4></div></div></div><a id="idm261717654128" class="indexterm"></a><a id="idm261737205792" 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.
@@ -440,9 +440,9 @@ security = share
</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">12.1.10. Samba with CUPS Printing Support</h3></div></div></div><a id="idm225471106976" class="indexterm"></a><div class="para">
+ </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">12.1.10. Samba with CUPS Printing Support</h3></div></div></div><a id="idm261758418336" 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">12.1.10.1. Simple <code class="filename">smb.conf</code> Settings</h4></div></div></div><a id="idm225461519504" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-samba-cups-smb.conf"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.10.1. Simple <code class="filename">smb.conf</code> Settings</h4></div></div></div><a id="idm261730254000" 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
@@ -467,7 +467,7 @@ printer admin = ed, john</pre><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">12.1.11. Samba Distribution Programs</h3></div></div></div><a id="idm225501987152" class="indexterm"></a><h4 id="s3-samba-programs-findsmb"> <code class="filename">findsmb</code> </h4><a id="idm225477040016" class="indexterm"></a><a id="idm225453386752" class="indexterm"></a><pre class="screen"><code class="command">findsmb <em class="replaceable"><code>subnet_broadcast_address</code></em></code></pre><div class="para">
+ </div></div></div><div class="section" id="s2-samba-programs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.1.11. Samba Distribution Programs</h3></div></div></div><a id="idm261751811472" class="indexterm"></a><h4 id="s3-samba-programs-findsmb"> <code class="filename">findsmb</code> </h4><a id="idm261760330928" class="indexterm"></a><a id="idm261742454848" 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:
@@ -482,7 +482,7 @@ IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
10.1.57.141 JAWS +[KWIKIMART] [Unix] [Samba 2.2.7a-security-rollup-fix]
10.1.56.159 FRED +[MYGROUP] [Unix] [Samba 3.0.0-14.3E]
10.1.59.192 LEGION *[MYGROUP] [Unix] [Samba 2.2.7-security-rollup-fix]
-10.1.56.205 NANCYN +[MYGROUP] [Unix] [Samba 2.2.7a-security-rollup-fix]</pre><h4 id="s3-samba-programs-net"> <code class="filename">net</code> </h4><a id="idm225476413168" class="indexterm"></a><a id="idm225480280480" 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">
+10.1.56.205 NANCYN +[MYGROUP] [Unix] [Samba 2.2.7a-security-rollup-fix]</pre><h4 id="s3-samba-programs-net"> <code class="filename">net</code> </h4><a id="idm261721122992" class="indexterm"></a><a id="idm261755636192" class="indexterm"></a><pre class="screen"><code class="command">net <em class="replaceable"><code>protocol function misc_options target_options</code></em></code></pre><div class="para">
The <code class="command">net</code> utility is similar to the <code class="command">net</code> utility used for Windows and MS-DOS. The first argument is used to specify the protocol to use when executing a command. The <code class="command"><em class="replaceable"><code>protocol</code></em> </code> option can be <code class="command">ads</code>, <code class="command">rap</code>, or <code class="command">rpc</code> for specifying the type of server connection. Active Directory uses <code class="command">ads</code>, Win9x/NT3 uses <code class="command">rap</code>, and Windows NT4/2000/2003/2008 uses <code class="command">rpc</code>. If the protocol is omitted, <code class="command">net</code> automatically tries to determine it.
</div><div class="para">
The following example displays a list of the available shares for a host named <code class="command">wakko</code>:
@@ -502,14 +502,14 @@ User name Comment
-----------------------------
andriusb Documentation
joe Marketing
-lisa Sales</pre><h4 id="s3-samba-programs-nmblookup"> <code class="filename">nmblookup</code> </h4><a id="idm225480996320" class="indexterm"></a><a id="idm225479258640" class="indexterm"></a><pre class="screen"><code class="command">nmblookup <em class="replaceable"><code>options netbios_name</code></em></code></pre><div class="para">
+lisa Sales</pre><h4 id="s3-samba-programs-nmblookup"> <code class="filename">nmblookup</code> </h4><a id="idm261783695760" class="indexterm"></a><a id="idm261745108832" class="indexterm"></a><pre class="screen"><code class="command">nmblookup <em class="replaceable"><code>options netbios_name</code></em></code></pre><div class="para">
The <code class="command">nmblookup</code> program resolves NetBIOS names into <code class="systemitem">IP</code> addresses. The program broadcasts its query on the local subnet until the target machine replies.
</div><div class="para">
The following example displays the <code class="systemitem">IP</code> address of the NetBIOS name <code class="literal">trek</code>:
</div><pre class="screen">
<strong class="userinput"><code>~]$ nmblookup trek</code></strong>
querying trek on 10.1.59.255
-10.1.56.45 trek<00></pre><h4 id="s3-samba-programs-pdbedit"> <code class="filename">pdbedit</code> </h4><a id="idm225474273056" class="indexterm"></a><a id="idm225444446128" class="indexterm"></a><pre class="screen"><code class="command">pdbedit <em class="replaceable"><code>options</code></em></code></pre><div class="para">
+10.1.56.45 trek<00></pre><h4 id="s3-samba-programs-pdbedit"> <code class="filename">pdbedit</code> </h4><a id="idm261757612704" class="indexterm"></a><a id="idm261754649808" 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:
@@ -563,23 +563,23 @@ lisa:504:
kristin:506:
<strong class="userinput"><code>~]$ pdbedit -x joe</code></strong>
<strong class="userinput"><code>~]$ pdbedit -L</code></strong>
-andriusb:505: lisa:504: kristin:506:</pre><h4 id="s3-samba-programs-rpcclient"> <code class="filename">rpcclient</code> </h4><a id="idm225435698352" class="indexterm"></a><a id="idm225439486752" class="indexterm"></a><pre class="screen"><code class="command">rpcclient <em class="replaceable"><code>server options</code></em></code></pre><div class="para">
+andriusb:505: lisa:504: kristin:506:</pre><h4 id="s3-samba-programs-rpcclient"> <code class="filename">rpcclient</code> </h4><a id="idm261754645008" class="indexterm"></a><a id="idm261748120224" class="indexterm"></a><pre class="screen"><code class="command">rpcclient <em class="replaceable"><code>server options</code></em></code></pre><div class="para">
The <code class="command">rpcclient</code> program issues administrative commands using Microsoft RPCs, which provide access to the Windows administration graphical user interfaces (GUIs) for systems management. This is most often used by advanced users that understand the full complexity of Microsoft RPCs.
- </div><h4 id="s3-samba-programs-smbcacls"> <code class="filename">smbcacls</code> </h4><a id="idm225477278656" class="indexterm"></a><a id="idm225470203216" 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">
+ </div><h4 id="s3-samba-programs-smbcacls"> <code class="filename">smbcacls</code> </h4><a id="idm261714911248" class="indexterm"></a><a id="idm261723061584" class="indexterm"></a><pre class="screen"><code class="command">smbcacls <em class="replaceable"><code>//server/share filename options</code></em></code></pre><div class="para">
The <code class="command">smbcacls</code> program modifies Windows ACLs on files and directories shared by a Samba server or a Windows server.
- </div><h4 id="s3-samba-programs-smbclient"> <code class="filename">smbclient</code> </h4><a id="idm225477278368" class="indexterm"></a><a id="idm225461705040" 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">
+ </div><h4 id="s3-samba-programs-smbclient"> <code class="filename">smbclient</code> </h4><a id="idm261754643344" class="indexterm"></a><a id="idm261744452544" class="indexterm"></a><pre class="screen"><code class="command">smbclient <em class="replaceable"><code>//server/share password options</code></em></code></pre><div class="para">
The <code class="command">smbclient</code> program is a versatile UNIX client which provides functionality similar to <code class="command">ftp</code>.
- </div><h4 id="s3-samba-programs-smbcontrol"> <code class="filename">smbcontrol</code> </h4><a id="idm225459670208" class="indexterm"></a><a id="idm225479634960" 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">
+ </div><h4 id="s3-samba-programs-smbcontrol"> <code class="filename">smbcontrol</code> </h4><a id="idm261783353712" class="indexterm"></a><a id="idm261747443552" class="indexterm"></a><pre class="screen"><code class="command">smbcontrol -i <em class="replaceable"><code>options</code></em></code></pre><pre class="screen"><code class="command">smbcontrol <em class="replaceable"><code>options destination messagetype parameters</code></em></code></pre><div class="para">
The <code class="command">smbcontrol</code> program sends control messages to running <code class="command">smbd</code>, <code class="command">nmbd</code>, or <code class="command">winbindd</code> daemons. Executing <code class="command">smbcontrol -i</code> runs commands interactively until a blank line or a <em class="parameter"><code>'q'</code></em> is entered.
- </div><h4 id="s3-samba-programs-smbpasswd"> <code class="filename">smbpasswd</code> </h4><a id="idm225471899744" class="indexterm"></a><a id="idm225474932032" class="indexterm"></a><pre class="screen"><code class="command">smbpasswd <em class="replaceable"><code>options username password</code></em></code></pre><div class="para">
+ </div><h4 id="s3-samba-programs-smbpasswd"> <code class="filename">smbpasswd</code> </h4><a id="idm261744064144" class="indexterm"></a><a id="idm261745169280" class="indexterm"></a><pre class="screen"><code class="command">smbpasswd <em class="replaceable"><code>options username password</code></em></code></pre><div class="para">
The <code class="command">smbpasswd</code> program manages encrypted passwords. This program can be run by a superuser to change any user's password and also by an ordinary user to change their own Samba password.
- </div><h4 id="s3-samba-programs-smbspool"> <code class="filename">smbspool</code> </h4><a id="idm225467995376" class="indexterm"></a><a id="idm225439856464" 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">
+ </div><h4 id="s3-samba-programs-smbspool"> <code class="filename">smbspool</code> </h4><a id="idm261724819712" class="indexterm"></a><a id="idm261714275200" class="indexterm"></a><pre class="screen"><code class="command">smbspool <em class="replaceable"><code>job user title copies options filename</code></em></code></pre><div class="para">
The <code class="command">smbspool</code> program is a CUPS-compatible printing interface to Samba. Although designed for use with CUPS printers, <code class="command">smbspool</code> can work with non-CUPS printers as well.
- </div><h4 id="s3-samba-programs-smbstatus"> <code class="filename">smbstatus</code> </h4><a id="idm225457344176" class="indexterm"></a><a id="idm225459017760" class="indexterm"></a><pre class="screen"><code class="command">smbstatus <em class="replaceable"><code>options</code></em></code></pre><div class="para">
+ </div><h4 id="s3-samba-programs-smbstatus"> <code class="filename">smbstatus</code> </h4><a id="idm261714728992" class="indexterm"></a><a id="idm261784732272" class="indexterm"></a><pre class="screen"><code class="command">smbstatus <em class="replaceable"><code>options</code></em></code></pre><div class="para">
The <code class="command">smbstatus</code> program displays the status of current connections to a Samba server.
- </div><h4 id="s3-samba-programs-smbtar"> <code class="filename">smbtar</code> </h4><a id="idm225477760304" class="indexterm"></a><a id="idm225438068656" class="indexterm"></a><pre class="screen"><code class="command">smbtar <em class="replaceable"><code>options</code></em></code></pre><div class="para">
+ </div><h4 id="s3-samba-programs-smbtar"> <code class="filename">smbtar</code> </h4><a id="idm261749632864" class="indexterm"></a><a id="idm261745379104" class="indexterm"></a><pre class="screen"><code class="command">smbtar <em class="replaceable"><code>options</code></em></code></pre><div class="para">
The <code class="command">smbtar</code> program performs backup and restores of Windows-based share files and directories to a local tape archive. Though similar to the <code class="command">tar</code> command, the two are not compatible.
- </div><h4 id="s3-samba-programs-testparm"> <code class="filename">testparm</code> </h4><a id="idm225461685920" class="indexterm"></a><a id="idm225447863264" 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">
+ </div><h4 id="s3-samba-programs-testparm"> <code class="filename">testparm</code> </h4><a id="idm261755227504" class="indexterm"></a><a id="idm261714345488" class="indexterm"></a><pre class="screen"><code class="command">testparm <em class="replaceable"><code>options filename hostname IP_address</code></em></code></pre><div class="para">
The <code class="command">testparm</code> program checks the syntax of the <code class="filename">/etc/samba/smb.conf</code> file. If your <code class="filename">smb.conf</code> file is in the default location (<code class="filename">/etc/samba/smb.conf</code>) you do not need to specify the location. Specifying the host name and <code class="systemitem">IP</code> address to the <code class="command">testparm</code> program verifies that the <code class="filename">hosts.allow</code> and <code class="filename">host.deny</code> files are configured correctly. The <code class="command">testparm</code> program also displays a summary of your <code class="filename">smb.conf</code> file and the server's role (stand-alone, domain, etc.) after testing. This is convenient when debugging as it excludes comments and concisely presents information for experienced administrators to read.
</div><div class="para">
For example:
@@ -621,11 +621,11 @@ Press enter to see a dump of your service definitions
force user = andriusb
force group = users
read only = No
- guest only = Yes</pre><h4 id="s3-samba-programs-wbinfo"> <code class="filename">wbinfo</code> </h4><a id="idm225464939056" class="indexterm"></a><a id="idm225461277200" class="indexterm"></a><pre class="screen"><code class="command">wbinfo <em class="replaceable"><code>options</code></em></code></pre><div class="para">
+ guest only = Yes</pre><h4 id="s3-samba-programs-wbinfo"> <code class="filename">wbinfo</code> </h4><a id="idm261750062064" class="indexterm"></a><a id="idm261784813472" 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">12.1.12. Additional Resources</h3></div></div></div><a id="idm225464692016" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-samba-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.1.12. Additional Resources</h3></div></div></div><a id="idm261752329232" 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">12.1.12.1. Installed Documentation</h4></div></div></div><a id="idm225500518224" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><div class="section" id="s3-samba-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.1.12.1. Installed Documentation</h4></div></div></div><a id="idm261785856976" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="filename">/usr/share/doc/samba/</code> — All additional files included with the Samba distribution. This includes all helper scripts, sample configuration files, and documentation.
</div></li></ul></div><div class="para">
See the following manual pages for detailed information about <span class="application"><strong>Samba</strong></span>:
@@ -639,13 +639,13 @@ Press enter to see a dump of your service definitions
<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">12.1.12.2. Related Books</h4></div></div></div><a id="idm225474416464" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </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">12.1.12.2. Related Books</h4></div></div></div><a id="idm261746699696" 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">12.1.12.3. Useful Websites</h4></div></div></div><a id="idm225471114576" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </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">12.1.12.3. Useful Websites</h4></div></div></div><a id="idm261787662416" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://www.samba.org/">http://www.samba.org/</a> — Homepage for the Samba distribution and all official documentation created by the Samba development team. Many resources are available in HTML and PDF formats, while others are only available for purchase. Although many of these links are not Fedora specific, some concepts may apply.
</div></li><li class="listitem"><div class="para">
<a href="http://us1.samba.org/samba/archives.html">http://samba.org/samba/archives.html </a> — Active email lists for the Samba community. Enabling digest mode is recommended due to high levels of list activity.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Mail_Servers.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Mail_Servers.html
index e7983cc..507594e 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Mail_Servers.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Mail_Servers.html
@@ -8,7 +8,7 @@
addID('Fedora.21.System_Administrators_Guide');
</script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Servers.html" title="Part IV. Servers" /><link rel="prev" href="ch-Web_Servers.html" title="Chapter 9. Web Servers" /><link rel="next" href="s1-email-types.html" title="10.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-emai
l-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 10. Mail Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Mail_Servers.html#s1-email-protocols">10.1. Email Protocols</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Mail_Servers.html#s2-email-protocols-send">10.1.1. Mail Transport Protocols</a></span></dt><dt><span class="section"><a href="ch-Mail_Servers.html#s2-email-protocols-client">10.1.2. Mail Access Protocols</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-types.html">10.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-types.html#s2-email-types-mta">10.2.1. Mail Transport Agent</a></span></dt><dt><span class="section"><a href="s2-email-types-mda.html">10.2.2. Mail Delivery Agent</a></span></dt><dt><span
class="section"><a href="s2-email-types-mua.html">10.2.3. Mail User Agent</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mta.html">10.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mta.html#s2-email-mta-postfix">10.3.1. Postfix</a></span></dt><dt><span class="section"><a href="s2-email-mta-sendmail.html">10.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="s2-email-mta-fetchmail.html">10.3.3. Fetchmail</a></span></dt><dt><span class="section"><a href="s2-email-switchmail.html">10.3.4. Mail Transport Agent (MTA) Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mda.html">10.4. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mda.html#s2-email-procmail-configuration">10.4.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="s2-email-procmail-recipes.html">10.4.2. Procmail Recipes</a></span></dt></dl></dd
><dt><span class="section"><a href="s1-email-mua.html">10.5. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mua.html#s2-email-security">10.5.1. Securing Communication</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-additional-resources.html">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-additional-resources.html#s2-email-installed-docs">10.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-email-useful-websites.html">10.6.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-email-related-books.html">10.6.3. Related Books</a></span></dt></dl></dd></dl></div><div class="para">
Fedora offers many advanced applications to serve and access email. This chapter describes modern email protocols in use today, and some of the programs designed to send and receive email.
- </div><div class="section" id="s1-email-protocols"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.1. Email Protocols</h2></div></div></div><a id="idm225462228512" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s1-email-protocols"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">10.1. Email Protocols</h2></div></div></div><a id="idm261754055952" 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.
@@ -16,7 +16,7 @@
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">10.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">10.1.1.1. SMTP</h4></div></div></div><a id="idm225477793392" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-email-protocols-smtp"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.1.1.1. SMTP</h4></div></div></div><a id="idm261752399648" 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.
@@ -26,7 +26,7 @@
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">10.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">10.1.2.1. POP</h4></div></div></div><a id="idm225458126256" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-email-protocols-pop"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.1.2.1. POP</h4></div></div></div><a id="idm261758834240" 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 <span class="package">dovecot</span> package is installed on your system by running, as <code class="systemitem">root</code>:
@@ -50,7 +50,7 @@
<span class="emphasis"><em>RPOP</em></span> — <code class="systemitem">POP3</code> with <code class="systemitem">RPOP</code> authentication. This uses a per-user ID, similar to a password, to authenticate POP requests. However, this ID is not encrypted, so <code class="systemitem">RPOP</code> is no more secure than standard <code class="systemitem">POP</code>.
</div></li></ul></div><div class="para">
For added security, it is possible to use <em class="firstterm">Secure Socket Layer</em> (<em class="firstterm">SSL</em>) encryption for client authentication and data transfer sessions. This can be enabled by using the <code class="command">pop3s</code> service, or by using the <code class="command">stunnel</code> application. For more information on securing email communication, see <a class="xref" href="s1-email-mua.html#s2-email-security">Section 10.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">10.1.2.2. IMAP</h4></div></div></div><a id="idm225468661344" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-protocols-imap"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.1.2.2. IMAP</h4></div></div></div><a id="idm261721238784" class="indexterm"></a><div class="para">
The default <code class="systemitem">IMAP</code> server under Fedora is <span class="application"><strong>Dovecot</strong></span> and is provided by the <span class="package">dovecot</span> package. See <a class="xref" href="ch-Mail_Servers.html#s3-email-protocols-pop">Section 10.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.
@@ -64,11 +64,11 @@
For added security, it is possible to use <code class="systemitem">SSL</code> encryption for client authentication and data transfer sessions. This can be enabled by using the <code class="command">imaps</code> service, or by using the <code class="command">stunnel</code> program. For more information on securing email communication, see <a class="xref" href="s1-email-mua.html#s2-email-security">Section 10.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">10.1.2.3. Dovecot</h4></div></div></div><a id="idm225439391328" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-mail-server-dovecot"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.1.2.3. Dovecot</h4></div></div></div><a id="idm261741601472" class="indexterm"></a><div class="para">
The <code class="command">imap-login</code> and <code class="command">pop3-login</code> processes which implement the <code class="systemitem">IMAP</code> and <code class="systemitem">POP3</code> protocols are spawned by the master <code class="systemitem">dovecot</code> daemon included in the <span class="package">dovecot</span> package. The use of <code class="systemitem">IMAP</code> and <code class="systemitem">POP</code> is configured through the <code class="filename">/etc/dovecot/dovecot.conf</code> configuration file; by default <code class="command">dovecot</code> runs <code class="systemitem">IMAP</code> and <code class="systemitem">POP3</code> together with their secure versions using <code class="systemitem">SSL</code>. To configure <code class="command">dovecot</code> to use <code class="systemitem">POP</code>, complete the following steps:
</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
Edit the <code class="filename">/etc/dovecot/dovecot.conf</code> configuration file to make sure the <code class="literal">protocols</code> variable is uncommented (remove the hash sign (<code class="literal">#</code>) at the beginning of the line) and contains the <code class="literal">pop3</code> argument. For example:
- </div><pre class="programlisting">protocols = imap imaps pop3 pop3s</pre><div class="para">
+ </div><pre class="screen">protocols = imap pop3 lmtp</pre><div class="para">
When the <code class="literal">protocols</code> variable is left commented out, <code class="command">dovecot</code> will use the default values as described above.
</div></li><li class="listitem"><div class="para">
Make the change operational for the current session by running the following command as <code class="systemitem">root</code>:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Managing_Users_and_Groups.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Managing_Users_and_Groups.html
index ca4a303..cacdf4e 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Managing_Users_and_Groups.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Managing_Users_and_Groups.html
@@ -6,21 +6,23 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Basic_System_Configuration.html" title="Part I. Basic System Configuration" /><link rel="prev" href="sect-Date_and_Time-Resources.html" title="3.4. Additional Resources" /><link rel="next" href="s1-users-configui.html" title="4.2. Using the 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-Resources.html"><strong>Pr
ev</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 4. Managing Users and Groups</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s1-users-groups-introduction">4.1. Introduction to Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">4.1.1. User Private Groups</a></span></dt><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">4.1.2. Shadow Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-configui.html">4.2. Using the User Manager Tool</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-configui.html#s2-redhat-co
nfig-users-list">4.2.1. Viewing Users and Groups</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-tools.html">4.3. Using Command Line Tools</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-tools.html#s2-users-tools-users-add">4.3.1. Adding a New User</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-add.html">4.3.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="s2-users-tools-password-aging.html">4.3.3. Enabling Password Aging</a></span></dt><dt><span class="section"><a href="s2-users-tools-users-logout.html">4.3.4. Enabling Automatic Logouts</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-directories.html">4.3.5. Creating Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-groups-additional-resources.html">4.4. Additional Resources</a></span></dt></dl></div><a id="idm225467632528" class="indexterm"></a><a id="idm225437862400" class="i
ndexterm"></a><a id="idm225436174992" class="indexterm"></a><a id="idm225477826752" class="indexterm"></a><div class="para">
- The control of users and groups is a core element of Fedora system administration. This chapter explains how to add, manage, and delete users and groups in the graphical user interface and on the command line, and covers advanced topics, such as enabling password aging or creating group directories.
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Basic_System_Configuration.html" title="Part I. Basic System Configuration" /><link rel="prev" href="sect-Date_and_Time-Resources.html" title="3.4. Additional Resources" /><link rel="next" href="s1-users-configui.html" title="4.2. Managing Users in a Graphical Environment" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Date_and_Time-Resources.ht
ml"><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 4. Managing Users and Groups</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s1-users-groups-introduction">4.1. Introduction to Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">4.1.1. User Private Groups</a></span></dt><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">4.1.2. Shadow Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-configui.html">4.2. Managing Users in a Graphical Environment</a></span></dt><dd><dl><dt><span class="section"><a href="s1-user
s-configui.html#s2-redhat-config-users-list">4.2.1. Using the Users Settings Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-tools.html">4.3. Using Command Line Tools</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-tools.html#s2-users-tools-users-add">4.3.1. Adding a New User</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-add.html">4.3.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="s2-users-tools-password-aging.html">4.3.3. Enabling Password Aging</a></span></dt><dt><span class="section"><a href="s2-users-tools-users-logout.html">4.3.4. Enabling Automatic Logouts</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-directories.html">4.3.5. Creating Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Users_and_Groups-Resources.html">4.4. Additional Resources</a></span></dt></dl></div><a id="idm261749961008" class="indexterm"></a><a i
d="idm261756516512" class="indexterm"></a><a id="idm261718096320" class="indexterm"></a><a id="idm261777124032" class="indexterm"></a><div class="para">
+ The control of users and groups is a core element of Fedora system administration. This chapter explains how to add, manage, and delete users and groups in the graphical user interface and on the command line, and covers advanced topics, such as creating group directories.
</div><div class="section" id="s1-users-groups-introduction"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.1. Introduction to Users and Groups</h2></div></div></div><div class="para">
- While users can be either people (meaning accounts tied to physical users) or accounts which exist for specific applications to use, groups are logical expressions of organization, tying users together for a common purpose. Users within a group can read, write, or execute files owned by that group.
+ While users can be either people (meaning accounts tied to physical users) or accounts which exist for specific applications to use, groups are logical expressions of organization, tying users together for a common purpose. Users within a group share the same permissions to read, write, or execute files owned by that group.
</div><div class="para">
Each user is associated with a unique numerical identification number called a <em class="firstterm">user ID</em> (<acronym class="acronym">UID</acronym>). Likewise, each group is associated with a <em class="firstterm">group ID</em> (<acronym class="acronym">GID</acronym>). 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 <code class="systemitem">root</code>, and access permissions can be changed by both the <code class="systemitem">root</code> user and file owner.
</div><div class="para">
- Additionally, Fedora supports <em class="firstterm">access control lists</em> (<acronym class="acronym">ACLs</acronym>) for files and directories which allow permissions for specific users outside of the owner to be set. For more information about this feature, see the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/ch-acls.html"><em class="citetitle">Access Control Lists</em></a> chapter of the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Storage_Administration_Guide/index.html"><em class="citetitle">Storage Administration Guide</em></a>.
- </div><div class="section" id="s2-users-groups-private-groups"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.1.1. User Private Groups</h3></div></div></div><a id="idm225460611248" class="indexterm"></a><a id="idm225438061536" class="indexterm"></a><a id="idm225438060096" class="indexterm"></a><a id="idm225457156112" class="indexterm"></a><div class="para">
+ Additionally, Fedora supports <em class="firstterm">access control lists</em> (<acronym class="acronym">ACLs</acronym>) for files and directories which allow permissions for specific users outside of the owner to be set. For more information about this feature, see the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Storage_Administration_Guide/ch-acls.html"><em class="citetitle">Access Control Lists</em></a> chapter of the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Storage_Administration_Guide/index.html"><em class="citetitle">Storage Administration Guide</em></a>.
+ </div><div class="section" id="s2-users-groups-private-groups"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.1.1. User Private Groups</h3></div></div></div><a id="idm261715964368" class="indexterm"></a><a id="idm261715962928" class="indexterm"></a><a id="idm261753142160" 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 user private group 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 user private group.
</div><div class="para">
User private groups 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 <span class="quote">“<span class="quote">group protection</span>”</span> is not necessary since every user has their own private group.
- </div></div><div class="section" id="s2-users-groups-shadow-utilities"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.1.2. Shadow Passwords</h3></div></div></div><a id="idm225474242592" class="indexterm"></a><a id="idm225474241152" class="indexterm"></a><div class="para">
+ The setting which determines what permissions are applied to a newly created file or directory is called a <em class="firstterm">umask</em> and is configured in the <code class="filename">/etc/bashrc</code> file. Traditionally on UNIX-based systems, the <code class="command">umask</code> is set to <code class="command">022</code>, which allows only the user who created the file or directory to make modifications. Under this scheme, all other users, <span class="emphasis"><em>including members of the creator's group</em></span>, are not allowed to make any modifications. However, under the UPG scheme, this <span class="quote">“<span class="quote">group protection</span>”</span> is not necessary since every user has their own private group.
+ </div><div class="para">
+ A list of all groups is stored in the <code class="filename">/etc/group</code> configuration file.
+ </div></div><div class="section" id="s2-users-groups-shadow-utilities"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.1.2. Shadow Passwords</h3></div></div></div><a id="idm261727968528" class="indexterm"></a><a id="idm261727967088" class="indexterm"></a><div class="para">
In environments with multiple users, it is very important to use <em class="firstterm">shadow passwords</em> provided by the <span class="package">shadow-utils</span> package to enhance the security of system authentication files. For this reason, the installation program enables shadow passwords by default.
</div><div class="para">
The following is a list of the advantages shadow passwords have over the traditional way of storing passwords on UNIX-based systems:
@@ -31,13 +33,13 @@
</div></li><li class="listitem"><div class="para">
Shadow passwords allow 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 <span class="package">shadow-utils</span> package work properly whether or not shadow passwords are enabled. However, since password aging information is stored exclusively in the <code class="filename">/etc/shadow</code> file, any commands which create or modify password aging information do not work. The following is a list of utilities and commands that do not work without first enabling shadow passwords:
+ Most utilities provided by the <span class="package">shadow-utils</span> package work properly whether or not shadow passwords are enabled. However, since password aging information is stored exclusively in the <code class="filename">/etc/shadow</code> file, some utilities and commands do not work without first enabling shadow passwords:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- The <code class="command">chage</code> utility.
+ The <code class="command">chage</code> utility for setting password-aging parameters. For details, see the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/chap-Hardening_Your_System_with_Tools_and_Services.html#sec-Password_Security">Password Security</a> section in the <em class="citetitle">Fedora 21 Security Guide</em>.
</div></li><li class="listitem"><div class="para">
- The <code class="command">gpasswd</code> utility.
+ The <code class="command">gpasswd</code> utility for administrating the <code class="filename">/etc/group</code> file.
</div></li><li class="listitem"><div class="para">
- The <code class="command">usermod</code> command with the <code class="option">-e</code> or <code class="option">-f</code> option.
+ The <code class="command">usermod</code> command with the <code class="option">-e, --expiredate</code> or <code class="option">-f, --inactive</code> option.
</div></li><li class="listitem"><div class="para">
- The <code class="command">useradd</code> command with the <code class="option">-e</code> or <code class="option">-f</code> option.
- </div></li></ul></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Date_and_Time-Resources.html"><strong>Prev</strong>3.4. 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>4.2. Using the User Manager Tool</a></li></ul></body></html>
\ No newline at end of file
+ The <code class="command">useradd</code> command with the <code class="option">-e, --expiredate</code> or <code class="option">-f, --inactive</code> option.
+ </div></li></ul></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Date_and_Time-Resources.html"><strong>Prev</strong>3.4. 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>4.2. Managing Users in a Graphical Environment</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Manually_Upgrading_the_Kernel.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Manually_Upgrading_the_Kernel.html
index cdd4145..e4ddd31 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Manually_Upgrading_the_Kernel.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Manually_Upgrading_the_Kernel.html
@@ -1,22 +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>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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Kernel_Module_and_Driver_Configuration.html" title="Part VI. Kernel, Module and Driver Configuration" /><link rel="prev" href="part-Kernel_Module_and_Driver_Configuration.html" title="Part VI. 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 acce
sskey="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 class="toc"><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.html#s3-kernel-boot-loader-grub">20.6.1. Configuring the GRUB 2 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="idm225454373104" class="indexterm"></a><a id="idm225438326896" class="indexterm"></a><a id="idm225437933024" class="indexterm"></a><a id="idm225463976464" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Kernel_Module_and_Driver_Configuration.html" title="Part VI. Kernel, Module and Driver Configuration" /><link rel="prev" href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html" title="20.8. Additional Resources" /><link rel="next" href="s1-kernel-preparing.html" title="21.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="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.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 21. Manually Upgrading the Kernel</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">21.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="s1-kernel-preparing.html">21.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="s1-kernel-download.html">21.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="s1-kernel-perform-upgrade.html">21.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="sec-Verifying_the_Initial_RAM_Disk_Ima
ge.html">21.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="s1-kernel-boot-loader.html">21.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">21.6.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-iseries.html">21.6.2. Configuring the OS/400 Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-pseries.html">21.6.3. Configuring the YABOOT Boot Loader</a></span></dt></dl></dd></dl></div><a id="idm261722114448" class="indexterm"></a><a id="idm261750024464" class="indexterm"></a><a id="idm261786305056" class="indexterm"></a><a id="idm261749343248" 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="idm225477501072" class="indexterm"></a><a id="idm225474762272" 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">
+ </div><a id="idm261721080176" class="indexterm"></a><a id="idm261756005472" 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="idm225442908592" class="indexterm"></a><div class="para">
+ </div></div></div><a id="idm261778007488" class="indexterm"></a><div class="para">
For more information on installing kernel packages with <span class="application"><strong>Yum</strong></span>, see <a class="xref" href="ch-yum.html#sec-Updating_Packages">Section 5.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">20.1. Overview of Kernel Packages</h2></div></div></div><a id="idm225463117616" class="indexterm"></a><a id="idm225463116176" class="indexterm"></a><a id="idm225436451600" class="indexterm"></a><a id="idm225436449712" class="indexterm"></a><a id="idm225436447824" class="indexterm"></a><a id="idm225505276592" class="indexterm"></a><a id="idm225505274672" class="indexterm"></a><a id="idm225505272752" class="indexterm"></a><a id="idm225467994432" class="indexterm"></a><a id="idm225467992512" class="indexterm"></a><a id="idm225467990592" class="indexterm"></a><a id="idm225467988672" class="indexterm"></a><a id="idm225451953472" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s1-kernel-packages"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.1. Overview of Kernel Packages</h2></div></div></div><a id="idm261754913904" class="indexterm"></a><a id="idm261754912464" class="indexterm"></a><a id="idm261761781088" class="indexterm"></a><a id="idm261761779200" class="indexterm"></a><a id="idm261740849232" class="indexterm"></a><a id="idm261740846736" class="indexterm"></a><a id="idm261740844816" class="indexterm"></a><a id="idm261740842896" class="indexterm"></a><a id="idm261785574384" class="indexterm"></a><a id="idm261785572464" class="indexterm"></a><a id="idm261785570544" 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.
@@ -27,13 +27,13 @@
</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>/Documentation/</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 VI. 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>
\ No newline at end of file
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-abi-whitelists</span> — Contains information pertaining to the Fedora kernel ABI, including a lists of kernel symbols that are needed by external Linux kernel modules and a <span class="package">yum</span> plug-in to aid enforcement.
+ </div></li><li class="listitem"><div class="para">
+ <span class="package">kernel-tools</span> — Contains tools for manipulating the Linux kernel and supporting documentation.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html"><strong>Prev</strong>20.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="s1-kernel-preparing.html"><strong>Next</strong>21.2. Preparing to Upgrade</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-OProfile.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-OProfile.html
index 7f9ca75..66db63f 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-OProfile.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-OProfile.html
@@ -6,14 +6,14 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Monitoring_and_Automation.html" title="Part V. Monitoring and Automation" /><link rel="prev" href="s1-autotasks-additional-resources.html" title="18.3. Additional Resources" /><link rel="next" href="s1-oprofile-configuring.html" title="19.2. Configuring OProfile" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-autotasks-additional-resources.html"><
strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-oprofile-configuring.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-OProfile" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 19. OProfile</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-OProfile.html#s1-oprofile-overview-tools">19.1. Overview of Tools</a></span></dt><dt><span class="section"><a href="s1-oprofile-configuring.html">19.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-configuring.html#s2-oprofile-kernel">19.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="s2-oprofile-events.html">19.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="s2-oprofile-starting-separate.html">19.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="s1-op
rofile-starting.html">19.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="s1-oprofile-saving-data.html">19.4. Saving Data</a></span></dt><dt><span class="section"><a href="s1-oprofile-analyzing-data.html">19.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">19.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opreport-single.html">19.5.2. Using opreport on a Single Executable</a></span></dt><dt><span class="section"><a href="s2-oprofile-module-output.html">19.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opannotate.html">19.5.4. Using <code class="command">opannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-dev-oprofile.html">19.6. Understanding <code class="filename">/de
v/oprofile/</code> </a></span></dt><dt><span class="section"><a href="s1-oprofile-example-usage.html">19.7. Example Usage</a></span></dt><dt><span class="section"><a href="s1-oprofile-java-support.html">19.8. OProfile Support for Java</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-java-support.html#s1-oprofile-java-profiling">19.8.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-gui.html">19.9. Graphical Interface</a></span></dt><dt><span class="section"><a href="s1-oprofile-and-systemtap.html">19.10. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="s1-oprofile-additional-resources.html">19.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-additional-resources.html#s1-oprofile-installed-docs">19.11.1. Installed Docs</a></span></dt><dt><span class="section"><a href="s2-oprofile-useful-websites.html">19.11.2. Useful Websites</a></span></dt><
/dl></dd></dl></div><a id="idm225468907680" class="indexterm"></a><a id="idm225476781968" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Monitoring_and_Automation.html" title="Part V. Monitoring and Automation" /><link rel="prev" href="s1-autotasks-additional-resources.html" title="18.3. Additional Resources" /><link rel="next" href="s1-using-operf.html" title="19.2. Using operf" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-autotasks-additional-resources.html"><strong>Prev</stron
g></a></li><li class="next"><a accesskey="n" href="s1-using-operf.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-OProfile" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 19. OProfile</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-OProfile.html#s1-oprofile-overview-tools">19.1. Overview of Tools</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OProfile.html#s2-operf_vs_opcontrol">19.1.1. operf vs. opcontrol</a></span></dt></dl></dd><dt><span class="section"><a href="s1-using-operf.html">19.2. Using operf</a></span></dt><dd><dl><dt><span class="section"><a href="s1-using-operf.html#s2-operf-kernel">19.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="s2-operf-events.html">19.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="s2-operf-categorization.html">19.2.3. Categorization of Samples</a></span><
/dt></dl></dd><dt><span class="section"><a href="s1-oprofile-configuring.html">19.3. Configuring OProfile Using Legacy Mode</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-configuring.html#s2-oprofile-kernel">19.3.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="s2-oprofile-events.html">19.3.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="s2-oprofile-starting-separate.html">19.3.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-starting.html">19.4. Starting and Stopping OProfile Using Legacy Mode</a></span></dt><dt><span class="section"><a href="s1-oprofile-saving-data.html">19.5. Saving Data in Legacy Mode</a></span></dt><dt><span class="section"><a href="s1-oprofile-analyzing-data.html">19.6. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">
19.6.1. Using <code class="command">opreport</code></a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opreport-single.html">19.6.2. Using opreport on a Single Executable</a></span></dt><dt><span class="section"><a href="s2-oprofile-module-output.html">19.6.3. Getting More Detailed Output on the Modules</a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opannotate.html">19.6.4. Using <code class="command">opannotate</code></a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-dev-oprofile.html">19.7. Understanding the /dev/oprofile/ directory </a></span></dt><dt><span class="section"><a href="s1-oprofile-example-usage.html">19.8. Example Usage</a></span></dt><dt><span class="section"><a href="s1-oprofile-java-support.html">19.9. OProfile Support for Java</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-java-support.html#s1-oprofile-java-profiling">19.9.1. Profiling Java Code</a></span></dt></dl></dd
><dt><span class="section"><a href="s1-oprofile-gui.html">19.10. Graphical Interface</a></span></dt><dt><span class="section"><a href="s1-oprofile-and-systemtap.html">19.11. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="s1-oprofile_additional_resources.html">19.12. Additional Resources</a></span></dt></dl></div><a id="idm261746650480" class="indexterm"></a><a id="idm261714376416" class="indexterm"></a><div class="para">
OProfile is a low overhead, system-wide performance monitoring tool. It uses the performance monitoring hardware on the processor to retrieve information about the kernel and executables on the system, such as when memory is referenced, the number of L2 cache requests, and the number of hardware interrupts received. On a Fedora system, the <code class="filename">oprofile</code> package must be installed to use this tool.
</div><div class="para">
- Many processors include dedicated performance monitoring hardware. This hardware makes it possible to detect when certain events happen (such as the requested data not being in cache). The hardware normally takes the form of one or more <em class="firstterm">counters</em> that are incremented each time an event takes place. When the counter value, essentially rolls over, an interrupt is generated, making it possible to control the amount of detail (and therefore, overhead) produced by performance monitoring.
+ Many processors include dedicated performance monitoring hardware. This hardware makes it possible to detect when certain events happen (such as the requested data not being in cache). The hardware normally takes the form of one or more <em class="firstterm">counters</em> that are incremented each time an event takes place. When the counter value increments, an interrupt is generated, making it possible to control the amount of detail (and therefore, overhead) produced by performance monitoring.
</div><div class="para">
OProfile uses this hardware (or a timer-based substitute in cases where performance monitoring hardware is not present) to collect <em class="firstterm">samples</em> of performance-related data each time a counter generates an interrupt. These samples are periodically written out to disk; later, the data contained in these samples can then be used to generate reports on system-level and application-level performance.
</div><div class="para">
- OProfile is a useful tool, but be aware of some limitations when using it:
+ Be aware of the following limitations when using OProfile:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<span class="emphasis"><em>Use of shared libraries</em></span> — Samples for code in shared libraries are not attributed to the particular application unless the <code class="option">--separate=library</code> option is used.
</div></li><li class="listitem"><div class="para">
@@ -23,11 +23,11 @@
</div></li><li class="listitem"><div class="para">
<span class="emphasis"><em>OProfile accumulates data from multiple runs</em></span> — OProfile is a system-wide profiler and expects processes to start up and shut down multiple times. Thus, samples from multiple runs accumulate. Use the command <code class="command">opcontrol --reset</code> to clear out the samples from previous runs.
</div></li><li class="listitem"><div class="para">
- <span class="emphasis"><em>Hardware performance counters do not work on guest virtual machines</em></span> — Because the hardware performance counters are not available on virtual systems, you need to use the <code class="computeroutput">timer</code> mode. Run the command <code class="command">opcontrol --deinit</code>, and then execute <code class="command">modprobe oprofile timer=1</code> to enable the <code class="computeroutput">timer</code> mode.
+ <span class="emphasis"><em>Hardware performance counters do not work on guest virtual machines</em></span> — Because the hardware performance counters are not available on virtual systems, you need to use the <code class="computeroutput">timer</code> mode. Enter the command <code class="command">opcontrol --deinit</code>, and then execute <code class="command">modprobe oprofile timer=1</code> to enable the <code class="computeroutput">timer</code> mode.
</div></li><li class="listitem"><div class="para">
<span class="emphasis"><em>Non-CPU-limited performance problems</em></span> — OProfile is oriented to finding problems with CPU-limited processes. OProfile does not identify processes that are asleep because they are waiting on locks or for some other event to occur (for example an I/O device to finish an operation).
- </div></li></ul></div><div class="section" id="s1-oprofile-overview-tools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.1. Overview of Tools</h2></div></div></div><a id="idm225463297808" class="indexterm"></a><div class="para">
- <a class="xref" href="ch-OProfile.html#tb-oprofile-tools">Table 19.1, “OProfile Commands”</a> provides a brief overview of the tools provided with the <code class="filename">oprofile</code> package.
+ </div></li></ul></div><div class="section" id="s1-oprofile-overview-tools"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.1. Overview of Tools</h2></div></div></div><a id="idm261740923408" class="indexterm"></a><div class="para">
+ <a class="xref" href="ch-OProfile.html#tb-oprofile-tools">Table 19.1, “OProfile Commands”</a> provides a brief overview of the most commonly used tools provided with the <code class="filename">oprofile</code> package.
</div><div class="table" id="tb-oprofile-tools"><h6>Table 19.1. OProfile Commands</h6><div class="table-contents"><table summary="OProfile Commands" border="1"><colgroup><col width="29%" class="command" /><col width="71%" class="description" /></colgroup><thead><tr><th class="">
Command
</th><th class="">
@@ -49,19 +49,26 @@
</td></tr><tr><td class="">
<code class="command">opannotate</code>
</td><td class="">
- Creates annotated source for an executable if the application was compiled with debugging symbols. See <a class="xref" href="s2-oprofile-reading-opannotate.html">Section 19.5.4, “Using <code class="command">opannotate</code> ”</a> for details.
+ Creates annotated source for an executable if the application was compiled with debugging symbols. See <a class="xref" href="s2-oprofile-reading-opannotate.html">Section 19.6.4, “Using <code class="command">opannotate</code>”</a> for details.
</td></tr><tr><td class="">
<code class="command">opcontrol</code>
</td><td class="">
<div class="para">
- Configures what data is collected. See <a class="xref" href="s1-oprofile-configuring.html">Section 19.2, “Configuring OProfile”</a> for details.
+ Configures what data is collected. See <a class="xref" href="s1-oprofile-configuring.html">Section 19.3, “Configuring OProfile Using Legacy Mode”</a> for details.
</div>
</td></tr><tr><td class="">
+ <code class="command">operf</code>
+ </td><td class="">
+ <div class="para">
+ Recommended tool to be used in place of <code class="command">opcontrol</code> for profiling. See <a class="xref" href="s1-using-operf.html">Section 19.2, “Using operf”</a> for details.
+ </div>
+ For differences between <code class="command">operf</code> and <code class="command">opcontrol</code> see <a class="xref" href="ch-OProfile.html#s2-operf_vs_opcontrol">Section 19.1.1, “operf vs. opcontrol”</a>.
+ </td></tr><tr><td class="">
<code class="command">opreport</code>
</td><td class="">
<div class="para">
- Retrieves profile data. See <a class="xref" href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">Section 19.5.1, “Using <code class="command">opreport</code> ”</a> for details.
+ Retrieves profile data. See <a class="xref" href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">Section 19.6.1, “Using <code class="command">opreport</code>”</a> for details.
</div>
</td></tr><tr><td class="">
@@ -71,4 +78,14 @@
Runs as a daemon to periodically write sample data to disk.
</div>
- </td></tr></tbody></table></div></div><br class="table-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-autotasks-additional-resources.html"><strong>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="s1-oprofile-configuring.html"><strong>Next</strong>19.2. Configuring OProfile</a></li></ul></body></html>
\ No newline at end of file
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="s2-operf_vs_opcontrol"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.1.1. operf vs. opcontrol</h3></div></div></div><div class="para">
+ There are two mutually exclusive methods for collecting profiling data with OProfile. You can either use the newer and preferred <code class="command">operf</code> or the <code class="command">opcontrol</code> tool.
+ </div><h4 id="idm261718808000">operf</h4><div class="para">
+ This is the recommended mode for profiling. The <code class="command">operf</code> tool uses the Linux Performance Events Subsystem, and therefore does not require the <span class="emphasis"><em>oprofile</em></span> kernel driver. The <code class="command">operf</code> tool allows you to target your profiling more precisely, as a single process or system-wide, and also allows OProfile to co-exist better with other tools using the performance monitoring hardware on your system. Unlike <code class="command">opcontrol</code>, it can be used without the <code class="systemitem">root</code> privileges. However, <code class="command">operf</code> is also capable of system-wide operations with use of the <code class="option">--system-wide</code> option, where root authority is required.
+ </div><div class="para">
+ With <code class="command">operf</code>, there is no initial setup needed. You can invoke <code class="command">operf</code> with command-line options to specify your profiling settings. After that, you can run the OProfile post-processing tools described in <a class="xref" href="s1-oprofile-analyzing-data.html">Section 19.6, “Analyzing the Data”</a>. See <a class="xref" href="s1-using-operf.html">Section 19.2, “Using operf”</a> for further information.
+ </div><h4 id="idm261758356384">opcontrol</h4><div class="para">
+ This mode consists of the <code class="command">opcontrol</code> shell script, the <code class="systemitem">oprofiled</code> daemon, and several post-processing tools. The <code class="command">opcontrol</code> command is used for configuring, starting, and stopping a profiling session. An OProfile kernel driver, usually built as a kernel module, is used for collecting samples, which are then recorded into sample files by <code class="systemitem">oprofiled</code>. You can use legacy mode only if you have <code class="systemitem">root</code> privileges. In certain cases, such as when you need to sample areas with disabled interrupt request (IRQ), this is a better alternative.
+ </div><div class="para">
+ Before OProfile can be run in legacy mode, it must be configured as shown in <a class="xref" href="s1-oprofile-configuring.html">Section 19.3, “Configuring OProfile Using Legacy Mode”</a>. These settings are then applied when starting OProfile (<a class="xref" href="s1-oprofile-starting.html">Section 19.4, “Starting and Stopping OProfile Using Legacy Mode”</a>).
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-autotasks-additional-resources.html"><strong>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="s1-using-operf.html"><strong>Next</strong>19.2. Using operf</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-OpenSSH.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-OpenSSH.html
index 8156136..03ea5b3 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-OpenSSH.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-OpenSSH.html
@@ -6,13 +6,13 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Infrastructure_Services.html" title="Part III. Infrastructure Services" /><link rel="prev" href="s2-services-additional-resources-books.html" title="6.3.2. Related Books" /><link rel="next" href="s1-ssh-configuration.html" title="7.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="s2-services-additional-resources-books.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 7. OpenSSH</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-OpenSSH.html#s1-ssh-protocol">7.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-why">7.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-features">7.1.2. Main Features</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-versions">7.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">7.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-configuration.html">7.2. An OpenSSH Configuration</a></span></dt>
<dd><dl><dt><span class="section"><a href="s1-ssh-configuration.html#s2-ssh-configuration-configs">7.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-sshd.html">7.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-requiring.html">7.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-keypairs.html">7.2.4. Using Key-based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-clients.html">7.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-clients.html#s2-ssh-clients-ssh">7.3.1. Using the ssh Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-scp.html">7.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-sftp.html">7.3.3. Using the <code class="command">sftp</code> Uti
lity</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-beyondshell.html">7.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">7.4.1. X11 Forwarding</a></span></dt><dt><span class="section"><a href="s2-ssh-beyondshell-tcpip.html">7.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="s1-openssh-additional-resources.html">7.5. Additional Resources</a></span></dt></dl></div><a id="idm225475870480" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Infrastructure_Services.html" title="Part III. Infrastructure Services" /><link rel="prev" href="s2-services-additional-resources-books.html" title="6.3.2. Related Books" /><link rel="next" href="s1-ssh-configuration.html" title="7.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="s2-services-additional-resources-books.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 7. OpenSSH</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-OpenSSH.html#s1-ssh-protocol">7.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-why">7.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-features">7.1.2. Main Features</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-versions">7.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">7.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-configuration.html">7.2. An OpenSSH Configuration</a></span></dt>
<dd><dl><dt><span class="section"><a href="s1-ssh-configuration.html#s2-ssh-configuration-configs">7.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-sshd.html">7.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-requiring.html">7.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-keypairs.html">7.2.4. Using Key-based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-clients.html">7.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-clients.html#s2-ssh-clients-ssh">7.3.1. Using the ssh Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-scp.html">7.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-sftp.html">7.3.3. Using the <code class="command">sftp</code> Uti
lity</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-beyondshell.html">7.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">7.4.1. X11 Forwarding</a></span></dt><dt><span class="section"><a href="s2-ssh-beyondshell-tcpip.html">7.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="s1-openssh-additional-resources.html">7.5. Additional Resources</a></span></dt></dl></div><a id="idm261716970960" 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 in to 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 in to 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 in to 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, the OpenSSH packages require the OpenSSL package <span class="package">openssl-libs</span>, which installs several important cryptographic libraries, enabling OpenSSH to provide encrypted communications.
- </div><div class="section" id="s1-ssh-protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.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">7.1.1. Why Use SSH?</h3></div></div></div><a id="idm225438716320" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s1-ssh-protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">7.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">7.1.1. Why Use SSH?</h3></div></div></div><a id="idm261759776880" 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 class="variablelist"><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.
@@ -24,7 +24,7 @@
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">7.1.2. Main Features</h3></div></div></div><a id="idm225435542464" class="indexterm"></a><a id="idm225435541024" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-ssh-features"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.1.2. Main Features</h3></div></div></div><a id="idm261749640816" class="indexterm"></a><a id="idm261749639376" class="indexterm"></a><div class="para">
The SSH protocol provides the following safeguards:
</div><div class="variablelist"><dl class="variablelist"><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.
@@ -42,11 +42,11 @@
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">7.1.3. Protocol Versions</h3></div></div></div><a id="idm225445891568" class="indexterm"></a><a id="idm225445890128" class="indexterm"></a><div class="para">
+ </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">7.1.3. Protocol Versions</h3></div></div></div><a id="idm261739285056" class="indexterm"></a><a id="idm261739283616" 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">7.1.4. Event Sequence of an SSH Connection</h3></div></div></div><a id="idm225464039616" class="indexterm"></a><div class="para">
+ </div></div></div></div><div class="section" id="s2-ssh-conn"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.1.4. Event Sequence of an SSH Connection</h3></div></div></div><a id="idm261738364480" 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.
@@ -56,7 +56,7 @@
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">7.1.4.1. Transport Layer</h4></div></div></div><a id="idm225462205792" class="indexterm"></a><div class="para">
+ </div></li></ol></div><div class="section" id="s2-ssh-protocol-conn-transport"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.1.4.1. Transport Layer</h4></div></div></div><a id="idm261744440528" 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:
@@ -78,18 +78,18 @@
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">7.1.4.2. Authentication</h4></div></div></div><a id="idm225458933328" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-ssh-protocol-authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.1.4.2. Authentication</h4></div></div></div><a id="idm261717181104" 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">7.1.4.3. Channels</h4></div></div></div><a id="idm225458929152" 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><a href="#ftn.idm225437901312" class="footnote"><sup class="footnote" id="idm225437901312">[1]</sup></a>. Each of these channels handles communication for different terminal sessions and for forwarded X11 sessions.
+ </div></div><div class="section" id="s2-ssh-protocol-connection"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.1.4.3. Channels</h4></div></div></div><a id="idm261717176928" 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><a href="#ftn.idm261748951200" class="footnote"><sup class="footnote" id="idm261748951200">[1]</sup></a>. 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 id="ftn.idm225437901312" class="footnote"><div class="para"><a href="#idm225437901312" class="para"><sup class="para">[1] </sup></a>
+ </div></div></div></div><div class="footnotes"><br /><hr /><div id="ftn.idm261748951200" class="footnote"><div class="para"><a href="#idm261748951200" class="para"><sup class="para">[1] </sup></a>
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="s2-services-additional-resources-books.html"><strong>Prev</strong>6.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="s1-ssh-configuration.html"><strong>Next</strong>7.2. An OpenSSH Configuration</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Opening_GUI_Applications.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Opening_GUI_Applications.html
index fc94ac4..e1dee5e 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Opening_GUI_Applications.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Opening_GUI_Applications.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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="gui-alt_f2.html" title="1.2. Launching Applications with Alt+F2" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Basic_System_Configuration
.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="gui-alt_f2.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-Opening_GUI_Applications" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 1. Opening Graphical Applications</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Opening_GUI_Applications.html#gui-from_cli">1.1. Opening graphical applications from the command line</a></span></dt><dt><span class="section"><a href="gui-alt_f2.html">1.2. Launching Applications with <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> </a></span></dt><dt><span class="section"><a href="gui-from_menu.html">1.3. Launching applications from the Desktop Menu</a></span></dt><dd><dl><dt><span class="section"><a href="gui-from_menu.html#gui-from_menu-gnome">1.3.1. Using GNOME menus</a></span></dt><dt><span class="section"><a
href="gui-from_menu-kde.html">1.3.2. Using KDE menus </a></span></dt><dt><span class="section"><a href="ch01s03s03.html">1.3.3. Using menus in LXDE, MATE, and XFCE</a></span></dt></dl></dd></dl></div><a id="idm225477919840" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's 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="gui-alt_f2.html" title="1.2. Launching Applications with Alt+F2" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Basic_System_Configuration
.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="gui-alt_f2.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-Opening_GUI_Applications" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 1. Opening Graphical Applications</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Opening_GUI_Applications.html#gui-from_cli">1.1. Opening graphical applications from the command line</a></span></dt><dt><span class="section"><a href="gui-alt_f2.html">1.2. Launching Applications with <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> </a></span></dt><dt><span class="section"><a href="gui-from_menu.html">1.3. Launching applications from the Desktop Menu</a></span></dt><dd><dl><dt><span class="section"><a href="gui-from_menu.html#gui-from_menu-gnome">1.3.1. Using GNOME menus</a></span></dt><dt><span class="section"><a
href="gui-from_menu-kde.html">1.3.2. Using KDE menus </a></span></dt><dt><span class="section"><a href="ch01s03s03.html">1.3.3. Using menus in LXDE, MATE, and XFCE</a></span></dt></dl></dd></dl></div><a id="idm261751413632" class="indexterm"></a><div class="para">
Fedora provides graphical applications in addition to command line utilities for configuring many features. This chapter describes methods for opening <code class="literal">Graphical User Interface</code>, or <em class="firstterm">GUI</em>, applications in various environments.
</div><div class="section" id="gui-from_cli"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1.1. Opening graphical applications from the command line</h2></div></div></div><div class="para">
Graphical applications can be launched from a terminal window or console session by simply typing the name of the application.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-RPM.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-RPM.html
index aa922b7..c679af4 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-RPM.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-RPM.html
@@ -6,48 +6,34 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="s1-kernel-modules-additional-resources.html" title="21.7. Additional Resources" /><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="s1-kernel-modules-additional-resources.html"><strong>Prev</strong></a></li><li class="next"
><a accesskey="n" href="s1-rpm-using.html"><strong>Next</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="idm225477957248" class="indexterm"></a><a id="idm225452143184" class="indexterm"></a><div class="para">
- The <em class="firstterm">RPM Package Manager</em> (RPM) is an open packaging system
- <a id="idm225496626480" 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>).
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="s1-kernel-modules-additional-resources.html" title="22.8. Additional Resources" /><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="s1-kernel-modules-additional-resources.html"><strong>Prev</strong></a></li><li class="next"
><a accesskey="n" href="s1-rpm-using.html"><strong>Next</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="idm261748192000" class="indexterm"></a><a id="idm261759060656" class="indexterm"></a><a id="idm261724318560" class="indexterm"></a><div class="para">
+ The <em class="firstterm">RPM Package Manager</em> (<span class="application"><strong>RPM</strong></span>) is an open packaging system that runs on Fedora as well as other Linux and UNIX systems. Red Hat and the Fedora Project encourage other vendors to use <span class="application"><strong>RPM</strong></span> for their own products. <span class="application"><strong>RPM</strong></span> is distributed under the terms of the <em class="firstterm">GPL</em> (<em class="firstterm">GNU General Public License</em>).
</div><div class="para">
- The 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 21. 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="idm225477221296" 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. See <a class="xref" href="ch-yum.html">Chapter 5, <em>Yum</em></a>.
+ The <span class="application"><strong>RPM Package Manager</strong></span> only works with packages built in the <span class="emphasis"><em>RPM format</em></span>. <span class="application"><strong>RPM</strong></span> itself is provided as the pre-installed <span class="package">rpm</span> package. For the end user, <span class="application"><strong>RPM</strong></span> makes system updates easy. Installing, uninstalling, and upgrading <span class="application"><strong>RPM</strong></span> packages can be accomplished with short commands. <span class="application"><strong>RPM</strong></span> maintains a database of installed packages and their files, so you can make queries and verify installed files on your system. There are several applications, such as <span class="application"><strong>Yum</strong></span> or <span class="application"><strong>PackageKit</strong></span>, that can make working with packages in the <span class="application"><strong>RPM</strong></span> format e
ven easier.
+ </div><div class="warning" id="warning-Use_Yum_Instead_of_RPM_Whenever_Possible"><div class="admonition_header"><h2>Use Yum Instead of RPM Whenever Possible</h2></div><div class="admonition"><a id="idm261759598496" class="indexterm"></a><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 <span class="application"><strong>RPM</strong></span>. <span class="application"><strong>Yum</strong></span> also performs and tracks complicated system-dependency resolutions. <span class="application"><strong>Yum</strong></span> maintains the system integrity and forces a system integrity check if packages are installed or removed using another application, such as <span class="application"><strong>RPM</strong></span>, instead of <span class="application"><strong>Yum</strong></span>. For these reasons, it is highly recommended that you use <span class="application"><strong>Yum</strong></span> instead of <span class="application"><strong>RPM</strong></span> whenever possible to perform package-management tasks. See <a class="xref" href="ch-yum.html">Chapter 5, <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.
- </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="idm225480992080" 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">A.1. RPM Design Goals</h2></div></div></div><a id="idm225463985680" class="indexterm"></a><div class="para">
- To understand how to use RPM, it can be helpful to understand the design goals of RPM:
- </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">Upgradability
- <a id="idm225463982832" 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="idm225463192688" 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="idm225463188432" 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="idm225477285264" 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.
+ During upgrades, <span class="application"><strong>RPM</strong></span> handles configuration files carefully, so that you never lose your customizations — something that you cannot accomplish with regular <code class="filename">.tar.gz</code> files.
+ </div><a id="idm261728669408" class="indexterm"></a><div class="para">
+ For the developer, <span class="application"><strong>RPM</strong></span> enables software source code to be packaged into source and binary packages for end users. This process is quite simple and is driven from a single file and optional patches that you create. This clear delineation between pristine sources and your patches along with build instructions eases the maintenance of the package as new versions of the software are released.
+ </div><div class="note" id="note-Root_Permissions"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Because <span class="application"><strong>RPM</strong></span> can make changes to the system itself, performing operations like installing, upgrading, downgrading, and uninstalling binary packages system-wide requires <code class="systemitem">root</code> privileges in most cases.
+ </div></div></div><div class="section" id="s1-rpm-design"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.1. RPM Design Goals</h2></div></div></div><a id="idm261740813760" class="indexterm"></a><div class="para">
+ To understand how to use <span class="application"><strong>RPM</strong></span>, it is helpful to understand the design goals of <span class="application"><strong>RPM</strong></span>:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261760390368" class="indexterm"></a>
+ Upgradability </span></dt><dd><div class="para">
+ With <span class="application"><strong>RPM</strong></span>, you can upgrade individual components of your system without a complete reinstallation. When you get a new release of an operating system based on <span class="application"><strong>RPM</strong></span>, such as Fedora, you do not need to reinstall a fresh copy of the operating system on your machine (as you might need to with operating systems based on other packaging systems). <span class="application"><strong>RPM</strong></span> allows for intelligent, fully-automated, in-place upgrades of your system. In addition, configuration files in packages are preserved across upgrades, so you do not lose your customizations. There are no special upgrade files needed to upgrade a package because the same <span class="application"><strong>RPM</strong></span> file is used to both install and upgrade the package on the system.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261760384096" class="indexterm"></a>
+ Powerful Querying </span></dt><dd><div class="para">
+ <span class="application"><strong>RPM</strong></span> is designed to provide powerful querying options. You can perform searches on your copy of the database for packages or even just certain files. You can also easily find out what package a file belongs to and where the package came from. The files an <span class="application"><strong>RPM</strong></span> package contains are in a compressed archive, with a custom binary header containing useful information about the package and its contents, allowing you to query individual packages quickly and easily.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261744409552" class="indexterm"></a>
+ System Verification </span></dt><dd><div class="para">
+ Another powerful <span class="application"><strong>RPM</strong></span> feature is the ability to verify packages. It allows you to verify that the files installed on the system are the same as the ones supplied by a given package. If an inconsistency is detected, <span class="application"><strong>RPM</strong></span> notifies you, and you can reinstall the package if necessary. Any configuration files that you modified are preserved during reinstallation.
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261725495952" class="indexterm"></a>
+ Pristine Sources </span></dt><dd><div class="para">
+ A crucial design goal was to allow the use of <span class="emphasis"><em>pristine</em></span> software sources, as distributed by the original authors of the software. With <span class="application"><strong>RPM</strong></span>, you have the pristine sources along with any patches that were used, plus complete build instructions. This is an important advantage for several reasons. For instance, if a new version of a program is released, you do not necessarily have to start from scratch to get it to compile. You can look at the patch to see what you <span class="emphasis"><em>might</em></span> need to do. All the compiled-in defaults, and all of the changes that were made to get the software to build properly, are easily visible using this technique.
</div><div class="para">
- The goal of keeping sources pristine may seem important only for developers, but it results in higher quality software for end users, too.
- </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-modules-additional-resources.html"><strong>Prev</strong>21.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="s1-rpm-using.html"><strong>Next</strong>A.2. Using RPM</a></li></ul></body></html>
\ No newline at end of file
+ The goal of keeping sources pristine may seem important only for developers, but it results in higher quality software for end users.
+ </div></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-modules-additional-resources.html"><strong>Prev</strong>22.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="s1-rpm-using.html"><strong>Next</strong>A.2. Using RPM</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Services_and_Daemons.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Services_and_Daemons.html
index 0b4574e..4540d49 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Services_and_Daemons.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Services_and_Daemons.html
@@ -6,13 +6,13 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Infrastructure_Services.html" title="Part III. Infrastructure Services" /><link rel="prev" href="part-Infrastructure_Services.html" title="Part III. Infrastructure Services" /><link rel="next" href="s1-services-running.html" title="6.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></li><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 6. Services and Daemons</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Services_and_Daemons.html#s1-services-configuring">6.1. Configuring Services</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">6.1.1. Enabling the Service</a></span></dt><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-disabling">6.1.2. Disabling the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-running.html">6.2. Running Services</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-running.html#s3-services-running-checking">6.2.1. Checking the
Service Status</a></span></dt><dt><span class="section"><a href="s3-services-running-running.html">6.2.2. Running the Service</a></span></dt><dt><span class="section"><a href="s3-services-running-stopping.html">6.2.3. Stopping the Service</a></span></dt><dt><span class="section"><a href="s3-services-running-restarting.html">6.2.4. Restarting the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-additional-resources.html">6.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-additional-resources.html#s2-services-additional-resources-installed">6.3.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-services-additional-resources-books.html">6.3.2. Related Books</a></span></dt></dl></dd></dl></div><a id="idm225503238432" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Infrastructure_Services.html" title="Part III. Infrastructure Services" /><link rel="prev" href="part-Infrastructure_Services.html" title="Part III. Infrastructure Services" /><link rel="next" href="s1-services-running.html" title="6.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></li><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 6. Services and Daemons</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Services_and_Daemons.html#s1-services-configuring">6.1. Configuring Services</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">6.1.1. Enabling the Service</a></span></dt><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-disabling">6.1.2. Disabling the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-running.html">6.2. Running Services</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-running.html#s3-services-running-checking">6.2.1. Checking the
Service Status</a></span></dt><dt><span class="section"><a href="s3-services-running-running.html">6.2.2. Running the Service</a></span></dt><dt><span class="section"><a href="s3-services-running-stopping.html">6.2.3. Stopping the Service</a></span></dt><dt><span class="section"><a href="s3-services-running-restarting.html">6.2.4. Restarting the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-additional-resources.html">6.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-additional-resources.html#s2-services-additional-resources-installed">6.3.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-services-additional-resources-books.html">6.3.2. Related Books</a></span></dt></dl></dd></dl></div><a id="idm261748935904" 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. For more information, refer to the Fedora 21 <em class="citetitle">Security Guide</em>.
- </div></div></div><div class="section" id="s1-services-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. Configuring Services</h2></div></div></div><a id="idm225460544448" class="indexterm"></a><a id="idm225476652336" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s1-services-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">6.1. Configuring Services</h2></div></div></div><a id="idm261724790032" class="indexterm"></a><a id="idm261748493568" 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.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-System_Locale_and_Keyboard_Configuration.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-System_Locale_and_Keyboard_Configuration.html
index 6886cbe..bef6b62 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-System_Locale_and_Keyboard_Configuration.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-System_Locale_and_Keyboard_Configuration.html
@@ -6,10 +6,10 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Basic_System_Configuration.html" title="Part I. Basic System Configuration" /><link rel="prev" href="ch01s03s03.html" title="1.3.3. Using menus in LXDE, MATE, and XFCE" /><link rel="next" href="s1-Changing_the_Keyboard_Layout.html" title="2.2. Changing the Keyboard Layout" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s03s03.html"><strong>Prev</
strong></a></li><li class="next"><a accesskey="n" href="s1-Changing_the_Keyboard_Layout.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-System_Locale_and_Keyboard_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. System Locale and Keyboard Configuration</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s1-Setting_the_System_Locale">2.1. Setting the System Locale</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Displaying_the_Current_Status">2.1.1. Displaying the Current Status</a></span></dt><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Listing_Available_Locales">2.1.2. Listing Available Locales</a></span></dt><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Setting_the_L
ocale">2.1.3. Setting the Locale</a></span></dt></dl></dd><dt><span class="section"><a href="s1-Changing_the_Keyboard_Layout.html">2.2. Changing the Keyboard Layout</a></span></dt><dd><dl><dt><span class="section"><a href="s1-Changing_the_Keyboard_Layout.html#s2-Displaying_the_Current_Settings">2.2.1. Displaying the Current Settings</a></span></dt><dt><span class="section"><a href="s2-Listing_Available_Keymaps.html">2.2.2. Listing Available Keymaps</a></span></dt><dt><span class="section"><a href="s2-Setting_the_Keymap.html">2.2.3. Setting the Keymap</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Keyboard_Configuration-Resources.html">2.3. Additional Resources</a></span></dt></dl></div><a id="idm225475123248" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Basic_System_Configuration.html" title="Part I. Basic System Configuration" /><link rel="prev" href="ch01s03s03.html" title="1.3.3. Using menus in LXDE, MATE, and XFCE" /><link rel="next" href="s1-Changing_the_Keyboard_Layout.html" title="2.2. Changing the Keyboard Layout" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch01s03s03.html"><strong>Prev</
strong></a></li><li class="next"><a accesskey="n" href="s1-Changing_the_Keyboard_Layout.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-System_Locale_and_Keyboard_Configuration" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 2. System Locale and Keyboard Configuration</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s1-Setting_the_System_Locale">2.1. Setting the System Locale</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Displaying_the_Current_Status">2.1.1. Displaying the Current Status</a></span></dt><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Listing_Available_Locales">2.1.2. Listing Available Locales</a></span></dt><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Setting_the_L
ocale">2.1.3. Setting the Locale</a></span></dt></dl></dd><dt><span class="section"><a href="s1-Changing_the_Keyboard_Layout.html">2.2. Changing the Keyboard Layout</a></span></dt><dd><dl><dt><span class="section"><a href="s1-Changing_the_Keyboard_Layout.html#s2-Displaying_the_Current_Settings">2.2.1. Displaying the Current Settings</a></span></dt><dt><span class="section"><a href="s2-Listing_Available_Keymaps.html">2.2.2. Listing Available Keymaps</a></span></dt><dt><span class="section"><a href="s2-Setting_the_Keymap.html">2.2.3. Setting the Keymap</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Keyboard_Configuration-Resources.html">2.3. Additional Resources</a></span></dt></dl></div><a id="idm261725861840" class="indexterm"></a><div class="para">
The <span class="emphasis"><em>system locale</em></span> specifies the language settings of system services and user interfaces. The <span class="emphasis"><em>keyboard layout</em></span> settings control the layout used on the text console and graphical user interfaces.
</div><div class="para">
- These settings can be made by modifying the <code class="filename">/etc/locale.conf</code> configuration file or by using the <span class="application"><strong>localectl</strong></span> utility. Also, you can use the graphical user interface to perform the task; for a description of this method, see <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/">Red Hat Enterprise Linux 7 Installation Guide</a>.
+ These settings can be made by modifying the <code class="filename">/etc/locale.conf</code> configuration file or by using the <span class="application"><strong>localectl</strong></span> utility. Also, you can use the graphical user interface to perform the task; for a description of this method, see <a href="http://docs.fedoraproject.org/install-guide">Fedora Installation Guide</a>.
</div><div class="section" id="s1-Setting_the_System_Locale"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.1. Setting the System Locale</h2></div></div></div><div class="para">
System-wide locale settings are stored in the <code class="filename">/etc/locale.conf</code> file, which is read at early boot by the <code class="systemitem">systemd</code> daemon. The locale settings configured in <code class="filename">/etc/locale.conf</code> are inherited by every service or user, unless individual programs or individual users override them.
</div><div class="para">
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-System_Monitoring_Tools.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-System_Monitoring_Tools.html
index 32798ff..606d680 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-System_Monitoring_Tools.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-System_Monitoring_Tools.html
@@ -6,9 +6,9 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Monitoring_and_Automation.html" title="Part V. Monitoring and Automation" /><link rel="prev" href="part-Monitoring_and_Automation.html" title="Part V. Monitoring and Automation" /><link rel="next" href="s1-sysinfo-memory-usage.html" title="16.2. Viewing Memory Usage" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Monitoring_and_Automation.html"
><strong>Prev</strong></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 class="toc"><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">16.1. Viewing System Processes</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-ps">16.1.1. Using the ps Command</a></span></dt><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-top">16.1.2. Using the top Command</a></span></dt><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-system_monitor">16.1.3. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span clas
s="section"><a href="s1-sysinfo-memory-usage.html">16.2. Viewing Memory Usage</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-memory-usage.html#s2-sysinfo-memory-usage-free">16.2.1. Using the free Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-memory-usage-system_monitor.html">16.2.2. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-cpu.html">16.3. Viewing CPU Usage</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-cpu.html#s2-sysinfo-cpu-system_monitor">16.3.1. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-filesystems.html">16.4. Viewing Block Devices and File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-filesystems.html#s2-sysinfo-filesystems-lsblk">16.4.1. Using the lsblk Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-blkid.html">16.4.2. Usi
ng the blkid Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-partx.html">16.4.3. Using the partx Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-findmnt.html">16.4.4. Using the findmnt Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-df.html">16.4.5. Using the df Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-du.html">16.4.6. Using the du Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-system_monitor.html">16.4.7. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-hardware.html">16.5. Viewing Hardware Information</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-hardware.html#s2-sysinfo-hardware-lspci">16.5.1. Using the lspci Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-hardware-lsusb.html">16.5.2. Using the lsusb Command
</a></span></dt><dt><span class="section"><a href="s2-sysinfo-hardware-lspcmcia.html">16.5.3. Using the lspcmcia Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-hardware-lscpu.html">16.5.4. Using the lscpu Command</a></span></dt></dl></dd><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP.html">16.6. Monitoring Performance with Net-SNMP</a></span></dt><dd><dl><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP.html#sect-System_Monitoring_Tools-Net-SNMP-Installing">16.6.1. Installing Net-SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Running.html">16.6.2. Running the Net-SNMP Daemon</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html">16.6.3. Configuring Net-SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html">16.6.4. Retrieving Performance Data over SNMP</a><
/span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Extending.html">16.6.5. Extending Net-SNMP</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-additional-resources.html">16.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">16.7.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="idm225442116912" class="indexterm"></a><a id="idm225475014560" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Monitoring_and_Automation.html" title="Part V. Monitoring and Automation" /><link rel="prev" href="part-Monitoring_and_Automation.html" title="Part V. Monitoring and Automation" /><link rel="next" href="s1-sysinfo-memory-usage.html" title="16.2. Viewing Memory Usage" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Monitoring_and_Automation.html"
><strong>Prev</strong></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 class="toc"><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">16.1. Viewing System Processes</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-ps">16.1.1. Using the ps Command</a></span></dt><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-top">16.1.2. Using the top Command</a></span></dt><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-system_monitor">16.1.3. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span clas
s="section"><a href="s1-sysinfo-memory-usage.html">16.2. Viewing Memory Usage</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-memory-usage.html#s2-sysinfo-memory-usage-free">16.2.1. Using the free Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-memory-usage-system_monitor.html">16.2.2. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-cpu.html">16.3. Viewing CPU Usage</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-cpu.html#s2-sysinfo-cpu-system_monitor">16.3.1. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-filesystems.html">16.4. Viewing Block Devices and File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-filesystems.html#s2-sysinfo-filesystems-lsblk">16.4.1. Using the lsblk Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-blkid.html">16.4.2. Usi
ng the blkid Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-partx.html">16.4.3. Using the partx Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-findmnt.html">16.4.4. Using the findmnt Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-df.html">16.4.5. Using the df Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-du.html">16.4.6. Using the du Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-system_monitor.html">16.4.7. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-hardware.html">16.5. Viewing Hardware Information</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-hardware.html#s2-sysinfo-hardware-lspci">16.5.1. Using the lspci Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-hardware-lsusb.html">16.5.2. Using the lsusb Command
</a></span></dt><dt><span class="section"><a href="s2-sysinfo-hardware-lspcmcia.html">16.5.3. Using the lspcmcia Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-hardware-lscpu.html">16.5.4. Using the lscpu Command</a></span></dt></dl></dd><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP.html">16.6. Monitoring Performance with Net-SNMP</a></span></dt><dd><dl><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP.html#sect-System_Monitoring_Tools-Net-SNMP-Installing">16.6.1. Installing Net-SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Running.html">16.6.2. Running the Net-SNMP Daemon</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html">16.6.3. Configuring Net-SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html">16.6.4. Retrieving Performance Data over SNMP</a><
/span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Extending.html">16.6.5. Extending Net-SNMP</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-additional-resources.html">16.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">16.7.1. Installed Documentation</a></span></dt></dl></dd></dl></div><a id="idm261755661712" class="indexterm"></a><a id="idm261778699744" class="indexterm"></a><div class="para">
In order to configure the system, system administrators often need to determine the amount of free memory, how much free disk space is available, how the hard drive is partitioned, or what processes are running.
- </div><div class="section" id="s1-sysinfo-system-processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.1. Viewing System Processes</h2></div></div></div><a id="idm225458192224" class="indexterm"></a><a id="idm225471545312" class="indexterm"></a><div class="section" id="s2-sysinfo-system-processes-ps"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.1.1. Using the ps Command</h3></div></div></div><a id="idm225480143856" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s1-sysinfo-system-processes"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.1. Viewing System Processes</h2></div></div></div><a id="idm261760711776" class="indexterm"></a><a id="idm261718699792" class="indexterm"></a><div class="section" id="s2-sysinfo-system-processes-ps"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.1.1. Using the ps Command</h3></div></div></div><a id="idm261782995376" class="indexterm"></a><div class="para">
The <code class="command">ps</code> command allows you to display information about running processes. It produces a static list, that is, a snapshot of what is running when you execute the command. If you want a constantly updated list of running processes, use the <code class="command">top</code> command or the <span class="application"><strong>System Monitor</strong></span> application instead.
</div><div class="para">
To list all processes that are currently running on the system including processes owned by other users, type the following at a shell prompt:
@@ -37,7 +37,7 @@ root 6 0.0 0.0 0 0 ? S 13:28 0:00 [migration/0]
</div><pre class="screen">~]$ <code class="command">ps ax | grep emacs</code>
2625 ? Sl 0:00 emacs</pre><div class="para">
For a complete list of available command line options, refer to the <span class="bold bold"><strong>ps</strong></span>(1) manual page.
- </div></div><div class="section" id="s2-sysinfo-system-processes-top"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.1.2. Using the top Command</h3></div></div></div><a id="idm225466498752" class="indexterm"></a><a id="idm225466496832" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-sysinfo-system-processes-top"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.1.2. Using the top Command</h3></div></div></div><a id="idm261787419584" class="indexterm"></a><a id="idm261725247712" class="indexterm"></a><div class="para">
The <code class="command">top</code> command displays a real-time list of processes that are running on the system. It also displays additional information about the system uptime, current CPU and memory usage, or total number of running processes, and allows you to perform actions such as sorting the list or killing a process.
</div><div class="para">
To run the <code class="command">top</code> command, type the following at a shell prompt:
@@ -105,7 +105,7 @@ Swap: 1540092k total, 55780k used, 1484312k free, 256408k cached
<span class="keycap"><strong>q</strong></span>
</td><td class="">
Terminates the utility and returns to the shell prompt.
- </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="s2-sysinfo-system-processes-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.1.3. Using the System Monitor Tool</h3></div></div></div><a id="idm225499602912" class="indexterm"></a><a id="idm225499601792" class="indexterm"></a><div class="para">
+ </td></tr></tbody></table></div></div><br class="table-break" /></div><div class="section" id="s2-sysinfo-system-processes-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.1.3. Using the System Monitor Tool</h3></div></div></div><a id="idm261726047760" class="indexterm"></a><a id="idm261726046640" class="indexterm"></a><div class="para">
The <span class="guilabel"><strong>Processes</strong></span> tab of the <span class="application"><strong>System Monitor</strong></span> tool allows you to view, search for, change the priority of, and kill processes from the graphical user interface.
</div><div class="para">
To start the <span class="application"><strong>System Monitor</strong></span> tool, either select <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Monitor</strong></span> from the <span class="guimenu"><strong>Activities</strong></span> menu, or type <code class="command">gnome-system-monitor</code> at a shell prompt. Then click the <span class="guilabel"><strong>Processes</strong></span> tab to view the list of running processes.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-TigerVNC.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-TigerVNC.html
index 0584e7a..492fa2d 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-TigerVNC.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-TigerVNC.html
@@ -6,23 +6,25 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Infrastructure_Services.html" title="Part III. Infrastructure Services" /><link rel="prev" href="s1-openssh-additional-resources.html" title="7.5. Additional Resources" /><link rel="next" href="s5-vnc-viewer.html" title="8.2. VNC Viewer" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-openssh-additional-resources.html"><strong>Prev</strong></a></li
><li class="next"><a accesskey="n" href="s5-vnc-viewer.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-TigerVNC" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 8. TigerVNC</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-TigerVNC.html#s1-vnc-server">8.1. VNC Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-TigerVNC.html#s2-vnc-installation">8.1.1. Installing VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#s3-configuring-vnc-server">8.1.2. Configuring VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#s4-starting-vncserver">8.1.3. Starting VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#terminating-vnc-session">8.1.4. Terminating a VNC session</a></span></dt></dl></dd><dt><span class="section"><a href="s5-vnc-viewer.html">8.2. VNC Viewer</a></span></dt><dd><dl><dt>
<span class="section"><a href="s5-vnc-viewer.html#installing-vncviewer">8.2.1. Installing VNC Viewer</a></span></dt><dt><span class="section"><a href="s6-connecting-vnc-viewer.html">8.2.2. Connecting to VNC Server</a></span></dt><dt><span class="section"><a href="s1-using_ssh.html">8.2.3. Connecting to VNC Server using SSH</a></span></dt></dl></dd><dt><span class="section"><a href="s9-additional-sources.html">8.3. Additional Resources</a></span></dt></dl></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Infrastructure_Services.html" title="Part III. Infrastructure Services" /><link rel="prev" href="s1-openssh-additional-resources.html" title="7.5. Additional Resources" /><link rel="next" href="s5-vnc-viewer.html" title="8.2. VNC Viewer" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-openssh-additional-resources.html"><strong>Prev</strong></a></li
><li class="next"><a accesskey="n" href="s5-vnc-viewer.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-TigerVNC" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 8. TigerVNC</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-TigerVNC.html#s1-vnc-server">8.1. VNC Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-TigerVNC.html#s2-vnc-installation">8.1.1. Installing VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#s3-configuring-vnc-server">8.1.2. Configuring VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#s4-starting-vncserver">8.1.3. Starting VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#terminating-vnc-session">8.1.4. Terminating a VNC Session</a></span></dt></dl></dd><dt><span class="section"><a href="s5-vnc-viewer.html">8.2. VNC Viewer</a></span></dt><dd><dl><dt>
<span class="section"><a href="s5-vnc-viewer.html#installing-vncviewer">8.2.1. Installing VNC Viewer</a></span></dt><dt><span class="section"><a href="s6-connecting-vnc-viewer.html">8.2.2. Connecting to VNC Server</a></span></dt><dt><span class="section"><a href="s1-using_ssh.html">8.2.3. Connecting to VNC Server Using SSH</a></span></dt></dl></dd><dt><span class="section"><a href="s9-additional-sources.html">8.3. Additional Resources</a></span></dt></dl></div><div class="para">
<code class="systemitem">TigerVNC</code> (Tiger Virtual Network Computing) is a system for graphical desktop sharing which allows you to remotely control other computers.
</div><div class="para">
<code class="systemitem">TigerVNC</code> works on the client-server network: a <span class="bold bold"><strong>server</strong></span> shares its output (<code class="systemitem">vncserver</code>) and a <span class="bold bold"><strong>client</strong></span> (<code class="systemitem">vncviewer</code>) connects to the server.
</div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
Unlike in previous Red Hat Enterprise Linux distributions, <code class="systemitem">TigerVNC</code> in Red Hat Enterprise Linux 7 uses the <code class="systemitem">systemd</code> system management daemon for its configuration. The <code class="filename">/etc/sysconfig/vncserver</code> configuration file has been replaced by <code class="filename">/etc/systemd/system/vncserver at .service</code>.
</div></div></div><div class="section" id="s1-vnc-server"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.1. VNC Server</h2></div></div></div><div class="para">
- <code class="systemitem">vncserver</code> is a utility which starts a VNC (Virtual Network Computing) desktop. It runs Xvnc with appropriate options and starts a window manager on the VNC desktop. <code class="systemitem">vncserver</code> allows users to run separate sessions in parallel on a machine which can then be accessed by any number of clients from anywhere.
+ <code class="systemitem">vncserver</code> is a utility which starts a VNC (Virtual Network Computing) desktop. It runs <span class="application"><strong>Xvnc</strong></span> with appropriate options and starts a window manager on the VNC desktop. <code class="systemitem">vncserver</code> allows users to run separate sessions in parallel on a machine which can then be accessed by any number of clients from anywhere.
</div><div class="section" id="s2-vnc-installation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.1. Installing VNC Server</h3></div></div></div><div class="para">
- To install the TigerVNC server, issue the following command as <code class="systemitem">root</code>:
+ To install the <span class="application"><strong>TigerVNC</strong></span> server, issue the following command as <code class="systemitem">root</code>:
<pre class="screen"><code class="command"><code class="computeroutput">~]# </code><strong class="userinput"><code>yum install tigervnc-server</code></strong></code></pre>
</div></div><div class="section" id="s3-configuring-vnc-server"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.2. Configuring VNC Server</h3></div></div></div><div class="procedure" id="configuring-vncserver"><h6>Procedure 8.1. Configuring the first VNC connection</h6><ol class="1"><li class="step"><div class="para">
A configuration file named <code class="filename">/etc/systemd/system/vncserver at .service</code> is required. To create this file, copy the <code class="filename">/lib/systemd/system/vncserver at .service</code> file as <code class="systemitem">root</code>:
</div><pre class="screen">
<code class="computeroutput">~]# </code><strong class="userinput"><code>cp /lib/systemd/system/vncserver at .service /etc/systemd/system/vncserver at .service</code></strong>
-</pre></li><li class="step"><div class="para">
+</pre><div class="para">
+ There is no need to include the display number in the file name because <code class="systemitem">systemd</code> automatically creates the appropriately named instance in memory on demand, replacing <code class="literal">'%i'</code> in the service file by the display number. For a single user it is not necessary to rename the file. For multiple users, a uniquely named service file for each user is required, for example, by adding the user name to the file name in some way. See <a class="xref" href="ch-TigerVNC.html#configuring-vncserver-2users">Section 8.1.2.1, “Configuring VNC Server for Two Users”</a> for details.
+ </div></li><li class="step"><div class="para">
Edit <code class="filename">/etc/systemd/system/vncserver at .service</code>, replacing <em class="replaceable"><code>USER</code></em> with the actual user name. Leave the remaining lines of the file unmodified. The <code class="option">-geometry</code> argument specifies the size of the VNC desktop to be created; by default, it is set to <code class="literal">1024x768</code>.
</div><pre class="screen">
ExecStart=/sbin/runuser -l <em class="replaceable"><code>USER</code></em> -c "/usr/bin/vncserver %i -geometry 1280x1024"
@@ -41,7 +43,9 @@ Password:
Verify:
</pre><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
The stored password is not encrypted; anyone who has access to the password file can find the plain-text password.
- </div></div></div></li></ol></div><div class="section" id="configuring-vncserver-2users"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">8.1.2.1. Configuring VNC Server for Two Users</h4></div></div></div><div class="para">
+ </div></div></div></li></ol></div><div class="para">
+ Proceed to <a class="xref" href="ch-TigerVNC.html#s4-starting-vncserver">Section 8.1.3, “Starting VNC Server”</a>.
+ </div><div class="section" id="configuring-vncserver-2users"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">8.1.2.1. Configuring VNC Server for Two Users</h4></div></div></div><div class="para">
If you want to configure more than one user on the same machine, create different template-type service files, one for each user.
</div><div class="procedure"><ol class="1"><li class="step"><div class="para">
Create two service files, for example <code class="filename">vncserver-<em class="replaceable"><code>USER_1</code></em>@.service</code> and <code class="filename">vncserver-<em class="replaceable"><code>USER_2</code></em>@.service</code>. In both these files substitute <em class="replaceable"><code>USER</code></em> with the correct user name.
@@ -57,18 +61,18 @@ Verify:
Password:
Verify:
</pre></li></ol></div></div></div><div class="section" id="s4-starting-vncserver"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.3. Starting VNC Server</h3></div></div></div><div class="para">
- To start or enable the service, specify the display number directly in the command. The file configured above works as a template, in which <code class="literal">%i</code> is substituted with the display number by <code class="systemitem">systemd</code>. With a valid number, execute the following command:
+ To start or enable the service, specify the display number directly in the command. The file configured above in <a class="xref" href="ch-TigerVNC.html#configuring-vncserver">Procedure 8.1, “Configuring the first VNC connection”</a> works as a template, in which <code class="literal">%i</code> is substituted with the display number by <code class="systemitem">systemd</code>. With a valid display number, execute the following command:
</div><pre class="screen">
<code class="command"><code class="computeroutput">~]# </code>systemctl start vncserver@:<em class="replaceable"><code>display_number</code></em>.service</code></pre><div class="para">
You can also enable the service to start automatically at system start. Then, when you log in, <code class="systemitem">vncserver</code> is automatically started. As <code class="systemitem">root</code>, issue a command as follows:
</div><pre class="screen">
<code class="command"><code class="computeroutput">~]# </code>systemctl enable vncserver@:<em class="replaceable"><code>display_number</code></em>.service</code></pre><div class="para">
- At this point, other users are able to use the <code class="systemitem">vncviewer</code> program to connect to the VNC server using the display number and password defined.
- </div><div class="section" id="starting-vncserver-2displays"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">8.1.3.1. Configuring VNC Server for two users and two different displays</h4></div></div></div><div class="para">
+ At this point, other users are able to use a VNC viewer program to connect to the VNC server using the display number and password defined. Provided a graphical desktop is installed, an instance of that desktop will be displayed. It will not be the same instance as that currently displayed on the target machine.
+ </div><div class="section" id="starting-vncserver-2displays"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">8.1.3.1. Configuring VNC Server for Two Users and Two Different Displays</h4></div></div></div><div class="para">
For the two configured VNC servers, vncserver-USER_1 at .service and vncserver-USER_2 at .service, you can enable different display numbers. For example, the following commands will cause a VNC server for USER_1 to start on display 3, and a VNC server for USER_2 to start on display 5:
</div><pre class="screen">
<code class="command"><code class="computeroutput">~]# </code>systemctl start vncserver-USER_1@:3.service</code>
-<code class="command"><code class="computeroutput">~]# </code>systemctl start vncserver-USER_2@:5.service</code></pre></div></div><div class="section" id="terminating-vnc-session"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.4. Terminating a VNC session</h3></div></div></div><div class="para">
+<code class="command"><code class="computeroutput">~]# </code>systemctl start vncserver-USER_2@:5.service</code></pre></div></div><div class="section" id="terminating-vnc-session"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.1.4. Terminating a VNC Session</h3></div></div></div><div class="para">
Similarly to enabling the <code class="systemitem">vncserver</code> service, you can disable the automatic start of the service at system start:
</div><pre class="screen">
<code class="command"><code class="computeroutput">~]# </code><strong class="userinput"><code>systemctl disable vncserver@:<em class="replaceable"><code>display_number</code></em>.service</code></strong></code></pre><div class="para">
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Viewing_and_Managing_Log_Files.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Viewing_and_Managing_Log_Files.html
index d498f26..93ad590 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Viewing_and_Managing_Log_Files.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Viewing_and_Managing_Log_Files.html
@@ -6,305 +6,16 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Monitoring_and_Automation.html" title="Part V. Monitoring and Automation" /><link rel="prev" href="s1-sysinfo-additional-resources.html" title="16.7. 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>Pr
ev</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 class="toc"><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-we
bsites.html">17.6.2. Useful Websites</a></span></dt></dl></dd></dl></div><a id="idm225473947872" class="indexterm"></a><a id="idm225438132912" 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.
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Monitoring_and_Automation.html" title="Part V. Monitoring and Automation" /><link rel="prev" href="s1-sysinfo-additional-resources.html" title="16.7. Additional Resources" /><link rel="next" href="s1-basic_configuration_of_rsyslog.html" title="17.2. Basic Configuration of Rsyslog" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-additional-r
esources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-basic_configuration_of_rsyslog.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 class="toc"><dt><span class="section"><a href="ch-Viewing_and_Managing_Log_Files.html#s1-logfiles-locating">17.1. Locating Log Files</a></span></dt><dt><span class="section"><a href="s1-basic_configuration_of_rsyslog.html">17.2. Basic Configuration of Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="s1-basic_configuration_of_rsyslog.html#s2-Filters">17.2.1. Filters</a></span></dt><dt><span class="section"><a href="s2-Actions.html">17.2.2. Actions</a></span></dt><dt><span class="section"><a href="s2-Templates.html">17.2.3. Templates</a></span></dt><dt><span class="section"><a h
ref="s2-global_directives.html">17.2.4. Global Directives</a></span></dt><dt><span class="section"><a href="s2-log_rotation.html">17.2.5. Log Rotation</a></span></dt><dt><span class="section"><a href="s2-using_the_new_configuration_format.html">17.2.6. Using the New Configuration Format</a></span></dt><dt><span class="section"><a href="s2-Rulesets.html">17.2.7. Rulesets</a></span></dt><dt><span class="section"><a href="s2-compatibility_with_syslogd.html">17.2.8. Compatibility with syslogd</a></span></dt></dl></dd><dt><span class="section"><a href="s1-working_with_queues_in_rsyslog.html">17.3. Working with Queues in Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="s1-working_with_queues_in_rsyslog.html#s2-defining_queues">17.3.1. Defining Queues</a></span></dt><dt><span class="section"><a href="s2-managing_queues.html">17.3.2. Managing Queues</a></span></dt></dl></dd><dt><span class="section"><a href="s1-using_rsyslog_modules.html">17.4. Using Rsyslog Modules
</a></span></dt><dd><dl><dt><span class="section"><a href="s1-using_rsyslog_modules.html#s2-importing_text_files">17.4.1. Importing Text Files</a></span></dt><dt><span class="section"><a href="s2-exporting_messages_to_a_database.html">17.4.2. Exporting Messages to a Database</a></span></dt><dt><span class="section"><a href="s2-enabling_encrypted_transport.html">17.4.3. Enabling Encrypted Transport</a></span></dt><dt><span class="section"><a href="s2-using_RELP.html">17.4.4. Using RELP</a></span></dt></dl></dd><dt><span class="section"><a href="s1-interaction_of_rsyslog_and_journal.html">17.5. Interaction of Rsyslog and Journal</a></span></dt><dt><span class="section"><a href="s1-structured_logging_with_rsyslog.html">17.6. Structured Logging with Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="s1-structured_logging_with_rsyslog.html#s2-importing_data_from_journal">17.6.1. Importing Data from Journal</a></span></dt><dt><span class="section"><a href="s2-filter
ing_structured_messages.html">17.6.2. Filtering Structured Messages</a></span></dt><dt><span class="section"><a href="s2-parsing_JSON.html">17.6.3. Parsing JSON</a></span></dt><dt><span class="section"><a href="s2-storing_messages_in_the_mongodb.html">17.6.4. Storing Messages in the MongoDB</a></span></dt></dl></dd><dt><span class="section"><a href="s1-debugging_rsyslog.html">17.7. Debugging Rsyslog</a></span></dt><dt><span class="section"><a href="s1-Using_the_Journal.html">17.8. Using the Journal</a></span></dt><dd><dl><dt><span class="section"><a href="s1-Using_the_Journal.html#s2-Viewing_Log_Files">17.8.1. Viewing Log Files</a></span></dt><dt><span class="section"><a href="s2-Access_Control.html">17.8.2. Access Control</a></span></dt><dt><span class="section"><a href="s2-Using_The_Live_View.html">17.8.3. Using The Live View</a></span></dt><dt><span class="section"><a href="s2-Filtering_Messages.html">17.8.4. Filtering Messages</a></span></dt><dt><span class="section"><a
href="s2-Enabling_Persistent_Storage.html">17.8.5. Enabling Persistent Storage</a></span></dt></dl></dd><dt><span class="section"><a href="s1-managing_log_files_in_a_graphical_environment.html">17.9. Managing Log Files in a Graphical Environment</a></span></dt><dd><dl><dt><span class="section"><a href="s1-managing_log_files_in_a_graphical_environment.html#s2-logfiles-viewing">17.9.1. Viewing Log Files</a></span></dt><dt><span class="section"><a href="s2-logfiles-adding.html">17.9.2. Adding a Log File</a></span></dt><dt><span class="section"><a href="s2-logfiles-examining.html">17.9.3. Monitoring Log Files</a></span></dt></dl></dd><dt><span class="section"><a href="s1-log-files-additional-resources.html">17.10. Additional Resources</a></span></dt></dl></div><a id="idm261726831856" class="indexterm"></a><a id="idm261723065872" class="indexterm"></a><div class="para">
+ <em class="firstterm">Log files</em> are files that contain messages about the system, including the kernel, services, and applications running on it. There are several types of log files for storing various information. For example, there is a default system log file, a log file just for security messages, and a log file for cron tasks. Log files can be very useful in many situations, for instance to troubleshoot a problem with the system, when trying to load a kernel driver, or when looking for unauthorized login attempts to the system.
+ </div><a id="idm261746747232" class="indexterm"></a><a id="idm261730937840" class="indexterm"></a><div class="para">
+ Some log files are controlled by a daemon called <code class="systemitem">rsyslogd</code>. The <code class="systemitem">rsyslogd</code> daemon is an enhanced replacement for <span class="application"><strong>syslogd</strong></span>, and provides extended filtering, various configuration options, input and output modules, support for transportation via the <code class="systemitem">TCP</code> or <code class="systemitem">UDP</code> protocols. A list of log files maintained by <code class="systemitem">rsyslogd</code> can be found in the <code class="filename">/etc/rsyslog.conf</code> configuration file. Most log files are located in the <code class="filename">/var/log/</code> directory.
</div><div class="para">
- Log files can 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="idm225445897792" class="indexterm"></a><a id="idm225437919776" 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.
+ Log files can also be managed by the <code class="systemitem">journald</code> daemon – a component of <code class="systemitem">systemd</code>. The <code class="systemitem">journald</code> daemon captures Syslog messages, kernel log messages, initial RAM disk and early boot messages as well as messages written to standard output and standard error output of all services, indexes them and makes this available to the user. The native journal file format, which is a structured and indexed binary file, improves searching and provides faster operation, and it also stores meta data information like time stamps or user IDs. Log files produced by <code class="systemitem">journald</code> are by default not persistent, log files are stored only in memory or a small ring-buffer in the <code class="filename">/run/log/journal/</code> directory. The amount of logged data depends on free memory, when you reach the capacity limit, the oldest entries are deleted. However, this setting can
be altered – see <a class="xref" href="s2-Enabling_Persistent_Storage.html">Section 17.8.5, “Enabling Persistent Storage”</a>. For more information on Journal see <a class="xref" href="s1-Using_the_Journal.html">Section 17.8, “Using the Journal”</a>.
</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">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">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/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">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/">http://www.rsyslog.com/doc/rsyslog_conf_modules.html</a>
- </div><div class="warning"><div class="admonition_header"><h2>Make sure you use trustworthy modules only</h2></div><div class="admonition"><div class="para">
- Note that when <span class="application"><strong>rsyslog</strong></span> loads any modules, it provides them with access to some of its functions and data. This poses a possible security threat. To minimize security risks, use trustworthy modules only.
- </div></div></div></div><div class="section" id="s2-rules"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">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">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 class="variablelist"><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 class="">
- Compare-operation
- </th><th class="">
- Description
- </th></tr></thead><tbody><tr><td class="">
- <em class="parameter"><code>contains</code></em>
- </td><td class="">
- Checks whether the provided string matches any part of the text provided by the property.
- </td></tr><tr><td class="">
- <em class="parameter"><code>isequal</code></em>
- </td><td class="">
- Compares the provided string against all of the text provided by the property.
- </td></tr><tr><td class="">
- <em class="parameter"><code>startswith</code></em>
- </td><td class="">
- Checks whether the provided string matches a prefix of the text provided by the property.
- </td></tr><tr><td class="">
- <em class="parameter"><code>regex</code></em>
- </td><td class="">
- Compares the provided POSIX BRE (Basic Regular Expression) regular expression against the text provided by the property.
- </td></tr><tr><td class="">
- <em class="parameter"><code>ereregex</code></em>
- </td><td class="">
- 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/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">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 class="variablelist"><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/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">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">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">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/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/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">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 class="variablelist"><dt class="varlistentry"><span class="term"><em class="parameter"><code>RSYSLOG_DebugFormat</code></em></span></dt><dd><pre class="screen">"Debug line with all properties:\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-co
lumn="always"><h3 class="title">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.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="s1-logfiles-locating.html"><strong>Next</strong>17.2. Locating Log Files</a></li></ul></body></html>
\ No newline at end of file
+ By default, these two logging tools coexist on your system. The <code class="systemitem">journald</code> daemon is the primary tool for troubleshooting. It also provides additional data necessary for creating structured log messages. Data acquired by <code class="systemitem">journald</code> is forwarded into the <code class="systemitem">/run/systemd/journal/syslog</code> socket that may be used by <code class="systemitem">rsyslogd</code> to process the data further. However, <span class="application"><strong>rsyslog</strong></span> does the actual integration by default via the <code class="systemitem">imjournal</code> input module, thus avoiding the aforementioned socket. You can also transfer data in the opposite direction, from <code class="systemitem">rsyslogd</code> to <code class="systemitem">journald</code> with use of <code class="systemitem">omjournal</code> module. See <a class="xref" href="s1-interaction_of_rsyslog_and_journal.html">Section 17.5, “Interaction
of Rsyslog and Journal”</a> for further information. The integration enables maintaining text-based logs in a consistent format to ensure compatibility with possible applications or configurations dependent on <code class="systemitem">rsyslogd</code>. Also, you can maintain rsyslog messages in a structured format (see <a class="xref" href="s1-structured_logging_with_rsyslog.html">Section 17.6, “Structured Logging with Rsyslog”</a>).
+ </div><div class="section" id="s1-logfiles-locating"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.1. Locating Log Files</h2></div></div></div><a id="idm261751351088" 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="idm261754146256" class="indexterm"></a><a id="idm261754144816" class="indexterm"></a><div class="para">
+ You may notice multiple files in the <code class="filename">/var/log/</code> directory with numbers after them (for example, <code class="filename">cron-20100906</code>). These numbers represent a time stamp that has been added to a rotated log file. Log files are rotated so their file sizes do not become too large. The <code class="filename">logrotate</code> package contains a cron task that automatically rotates log files according to the <code class="filename">/etc/logrotate.conf</code> configuration file and the configuration files in the <code class="filename">/etc/logrotate.d/</code> directory.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-additional-resources.html"><strong>Prev</strong>16.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="s1-basic_configuration_of_rsyslog.html"><strong>Next</strong>17.2. Basic Configuration of Rsyslog</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Web_Servers.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Web_Servers.html
index f6f8096..3509e31 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Web_Servers.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Web_Servers.html
@@ -6,13 +6,13 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Servers.html" title="Part IV. Servers" /><link rel="prev" href="part-Servers.html" title="Part IV. Servers" /><link rel="next" href="ch-Mail_Servers.html" title="Chapter 10. 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="part-Servers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Mail_Servers.html"><str
ong>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 9. Web Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Web_Servers.html#s1-The_Apache_HTTP_Server">9.1. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-changes">9.1.1. Notable Changes</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-version2-migrating">9.1.2. Updating the Configuration</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-running">9.1.3. Running the httpd Service</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-editing">9.1.4. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-dso">9.1.5. Working with Modules</a></span></dt><dt><span clas
s="section"><a href="ch-Web_Servers.html#s2-apache-virtualhosts">9.1.6. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-mod_ssl">9.1.7. Setting Up an SSL Server</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-resources">9.1.8. Additional Resources</a></span></dt></dl></dd></dl></div><a id="idm225458067200" class="indexterm"></a><a id="idm225458063808" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Servers.html" title="Part IV. Servers" /><link rel="prev" href="part-Servers.html" title="Part IV. Servers" /><link rel="next" href="ch-Mail_Servers.html" title="Chapter 10. 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="part-Servers.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Mail_Servers.html"><str
ong>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 9. Web Servers</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Web_Servers.html#s1-The_Apache_HTTP_Server">9.1. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-changes">9.1.1. Notable Changes</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-version2-migrating">9.1.2. Updating the Configuration</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-running">9.1.3. Running the httpd Service</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-editing">9.1.4. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-dso">9.1.5. Working with Modules</a></span></dt><dt><span clas
s="section"><a href="ch-Web_Servers.html#s2-apache-virtualhosts">9.1.6. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-mod_ssl">9.1.7. Setting Up an SSL Server</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-resources">9.1.8. Additional Resources</a></span></dt></dl></dd></dl></div><a id="idm261714758208" class="indexterm"></a><a id="idm261761262720" class="indexterm"></a><div class="para">
A <em class="firstterm">web server</em> is a network service that serves content to a client over the web. This typically means web pages, but any other documents can be served as well. Web servers are also known as HTTP servers, as they use the <em class="firstterm">hypertext transport protocol</em> (<acronym class="acronym">HTTP</acronym>).
- </div><div xml:lang="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">9.1. The Apache HTTP Server</h2></div></div></div><a id="idm225458068640" class="indexterm"></a><div class="para">
+ </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">9.1. The Apache HTTP Server</h2></div></div></div><a id="idm261714759648" class="indexterm"></a><div class="para">
The web server available in Fedora is the Apache HTTP server daemon, <code class="systemitem">httpd</code>, an open source web server developed by the <a href="http://www.apache.org/">Apache Software Foundation</a>. In Fedora 19 the Apache server was updated to <span class="application"><strong>Apache HTTP Server 2.4</strong></span>. This section describes the basic configuration of the <code class="systemitem">httpd</code> service, and covers some advanced topics such as adding server modules, setting up virtual hosts, or configuring the secure HTTP server.
</div><div class="para">
There are important differences between the Apache HTTP Server 2.4 and version 2.2, and if you are upgrading from a release prior to Fedora 19, you will need to update the <code class="systemitem">httpd</code> service configuration accordingly. This section reviews some of the newly added features, outlines important changes, and guides you through the update of older configuration files.
- </div><div class="section" id="s2-apache-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.1. Notable Changes</h3></div></div></div><a id="idm225452122064" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-apache-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.1. Notable Changes</h3></div></div></div><a id="idm261714767616" class="indexterm"></a><div class="para">
The Apache HTTP Server version 2.4 has the following changes compared to version 2.2:
</div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">httpd Service Control</span></dt><dd><div class="para">
With the migration away from SysV init scripts, server administrators should switch to using the <code class="command">apachectl</code> and <code class="command">systemctl</code> commands to control the service, in place of the <code class="command">service</code> command. The following examples are specific to the <code class="systemitem">httpd</code> service.
@@ -75,14 +75,14 @@
</div></dd><dt class="varlistentry"><span class="term">mod_authz_ldap</span></dt><dd><div class="para">
<span class="application"><strong>httpd 2.4</strong></span> provides LDAP support in sub-package <span class="package">mod_ldap</span> using <span class="application"><strong>mod_authnz_ldap</strong></span>.
</div></dd></dl></div>
- </div></dd></dl></div></div><div class="section" id="s2-apache-version2-migrating"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.2. Updating the Configuration</h3></div></div></div><a id="idm225476400064" class="indexterm"></a><div class="para">
+ </div></dd></dl></div></div><div class="section" id="s2-apache-version2-migrating"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.2. Updating the Configuration</h3></div></div></div><a id="idm261749336640" class="indexterm"></a><div class="para">
To update the configuration files from the Apache HTTP Server version 2.2, take the following steps:
</div><div class="procedure"><ol class="1"><li class="step"><div class="para">
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="idm225476406464" class="indexterm"></a>
+ <a id="idm261745450992" 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.
@@ -96,19 +96,19 @@ Syntax OK</pre><div class="para">
</div><pre class="screen">~]# <code class="command">yum install httpd</code></pre><div class="para">
For more information on the concept of targets and how to manage system services in Fedora in general, see
<a class="xref" href="ch-Services_and_Daemons.html">Chapter 6, <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">9.1.3.1. Starting the Service</h4></div></div></div><a id="idm225466024912" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-apache-running-starting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.3.1. Starting the Service</h4></div></div></div><a id="idm261729378864" 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 boot time, use the following command:
</div><pre class="screen">~]# <code class="command">systemctl enable httpd.service</code>
ln -s '/usr/lib/systemd/system/httpd.service' '/etc/systemd/system/multi-user.target.wants/httpd.service'</pre><div class="note"><div class="admonition_header"><h2>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">9.1.3.2. Stopping the Service</h4></div></div></div><a id="idm225475937376" class="indexterm"></a><div class="para">
+ </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">9.1.3.2. Stopping the Service</h4></div></div></div><a id="idm261729387536" 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 boot time, type:
</div><pre class="screen">~]# <code class="command">systemctl disable httpd.service</code>
-rm '/etc/systemd/system/multi-user.target.wants/httpd.service'</pre></div><div class="section" id="s3-apache-running-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.3.3. Restarting the Service</h4></div></div></div><a id="idm225475944944" class="indexterm"></a><div class="para">
+rm '/etc/systemd/system/multi-user.target.wants/httpd.service'</pre></div><div class="section" id="s3-apache-running-restarting"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.3.3. Restarting the Service</h4></div></div></div><a id="idm261722103280" class="indexterm"></a><div class="para">
There are three different ways to restart a running <code class="systemitem">httpd</code> service:
</div><div class="orderedlist"><ol><li class="listitem"><div class="para">
To restart the service completely, enter the following command as <code class="systemitem">root</code>:
@@ -124,7 +124,7 @@ rm '/etc/systemd/system/multi-user.target.wants/httpd.service'</pre></div><div c
This causes the running <code class="systemitem">httpd</code> service to reload its configuration file. Any requests currently being processed will continue to use the old configuration.
</div></li></ol></div><div class="para">
- </div></div><div class="section" id="s3-apache-running-status"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.3.4. Verifying the Service Status</h4></div></div></div><a id="idm225463151008" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-apache-running-status"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.3.4. Verifying the Service Status</h4></div></div></div><a id="idm261714941040" class="indexterm"></a><div class="para">
To verify that the <code class="systemitem">httpd</code> service is running, type the following at a shell prompt:
</div><pre class="screen">~]# <code class="command">systemctl is-active httpd.service</code>
active</pre></div></div><div class="section" id="s2-apache-editing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.4. Editing the Configuration Files</h3></div></div></div><div class="para">
@@ -134,25 +134,25 @@ active</pre></div></div><div class="section" id="s2-apache-editing"><div class="
</th><th class="">
Description
</th></tr></thead><tbody><tr><td class="">
- <a id="idm225458914352" class="indexterm"></a>
+ <a id="idm261752836800" class="indexterm"></a>
<code class="filename">/etc/httpd/conf/httpd.conf</code>
</td><td class="">
The main configuration file.
</td></tr><tr><td class="">
- <a id="idm225458918192" class="indexterm"></a>
+ <a id="idm261734156320" class="indexterm"></a>
<code class="filename">/etc/httpd/conf.d/</code>
</td><td class="">
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. See <a class="xref" href="ch-Web_Servers.html#s3-apache-running-restarting">Section 9.1.3.3, “Restarting the Service”</a> for more information on how to restart the <code class="systemitem">httpd</code> service.
- </div><a id="idm225459644064" class="indexterm"></a><div class="para">
+ </div><a id="idm261734163200" 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">apachectl configtest</code>
Syntax OK</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">9.1.4.1. Common httpd.conf Directives</h4></div></div></div><a id="idm225462617648" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-apache-httpdconf-directives"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.4.1. Common httpd.conf Directives</h4></div></div></div><a id="idm261743958416" 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 class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225462622400" class="indexterm"></a>
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261743963168" 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>>
@@ -167,7 +167,7 @@ Syntax OK</pre><div class="para">
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="idm225459648448" class="indexterm"></a>
+</Directory></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261747982704" 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>>
@@ -177,7 +177,7 @@ Syntax OK</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 9.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="idm225444161312" class="indexterm"></a>
+</IfDefine></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261763939232" 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>>
@@ -188,7 +188,7 @@ Syntax OK</pre><div class="para">
</div><div class="example" id="example-apache-httpdconf-ifmodule"><h6>Example 9.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="idm225464567040" class="indexterm"></a>
+</IfModule></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261735480176" 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>>
@@ -201,7 +201,7 @@ Syntax OK</pre><div class="para">
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="idm225479585840" class="indexterm"></a>
+</Location></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261735490992" 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>>
@@ -213,7 +213,7 @@ Syntax OK</pre><div class="para">
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="idm225479587088" class="indexterm"></a>
+</Proxy></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261741619616" 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>]…>
@@ -239,12 +239,12 @@ Syntax OK</pre><div class="para">
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="idm225478818480" class="indexterm"></a>
+</VirtualHost></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261748773072" 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="idm225478823184" class="indexterm"></a><a id="idm225442128560" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">AccessFileName <em class="replaceable"><code>filename</code></em>…</pre><a id="idm261748778256" class="indexterm"></a><a id="idm261748782048" 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="idm225442132000" class="indexterm"></a><a id="idm225442133280" class="indexterm"></a><div class="para">
+ </div><a id="idm261754248864" class="indexterm"></a><a id="idm261754251200" 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 9.7. Using the AccessFileName directive</h6><div class="example-contents"><pre class="programlisting">AccessFileName .htaccess
@@ -252,31 +252,31 @@ Syntax OK</pre><div class="para">
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="idm225442140272" class="indexterm"></a>
+</Files></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261754258240" 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 9.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="idm225505715248" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-action"><h6>Example 9.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="idm261730576928" 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 9.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="idm225505723008" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-adddescription"><h6>Example 9.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="idm261761240976" 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 9.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="idm225471875936" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-addencoding"><h6>Example 9.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="idm261754352432" 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 9.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="idm225459826608" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-addhandler"><h6>Example 9.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="idm261761736768" 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">
@@ -293,34 +293,34 @@ Syntax OK</pre><div class="para">
<code class="option">^^BLANKICON^^</code>
</td><td class="">
Represents a blank line.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-addicon"><h6>Example 9.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="idm225471293360" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-addicon"><h6>Example 9.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="idm261721777984" 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 9.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="idm225477007888" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-addiconbyencoding"><h6>Example 9.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="idm261745798592" 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 9.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="idm225467688608" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-addiconbytype"><h6>Example 9.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="idm261759732032" 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 9.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="idm225467585072" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-addlanguage"><h6>Example 9.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="idm261787439776" 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 9.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="idm225460756048" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-addtype"><h6>Example 9.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="idm261745952512" 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="idm225467645600" class="indexterm"></a><div class="para">
+ </div><a id="idm261752256704" 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 9.17. Using the Alias directive</h6><div class="example-contents"><pre class="programlisting">Alias /icons/ /var/www/icons/
@@ -329,13 +329,13 @@ Syntax OK</pre><div class="para">
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="idm225467653536" class="indexterm"></a>
+<Directory></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261752264080" 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 9.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="idm225506543824" class="indexterm"></a>
- <code class="option">AllowOverride</code> </span></dt><dd><a id="idm225506546960" class="indexterm"></a><a id="idm225506549360" class="indexterm"></a><div class="para">
+ </div><div class="example" id="example-apache-httpdconf-allow"><h6>Example 9.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="idm261778862128" class="indexterm"></a>
+ <code class="option">AllowOverride</code> </span></dt><dd><a id="idm261778865264" class="indexterm"></a><a id="idm261760937856" 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 9.4, “Available AllowOverride options”</a>.
@@ -371,24 +371,24 @@ Syntax OK</pre><div class="para">
<code class="option">Options</code>[<span class="optional">=<em class="replaceable"><code>option</code></em>,…</span>]
</td><td class="">
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 9.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="idm225461154880" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-allowoverride"><h6>Example 9.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="idm261734214688" 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 9.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="idm225448539392" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-browsermatch"><h6>Example 9.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="idm261751596032" 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 9.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="idm225481239776" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-cachedefaultexpire"><h6>Example 9.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="idm261777468656" 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 9.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="idm225481251296" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-cachedisable"><h6>Example 9.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="idm261724400432" 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">
@@ -409,17 +409,17 @@ Syntax OK</pre><div class="para">
<code class="option">fd</code>
</td><td class="">
The file descriptor cache.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-cacheenable"><h6>Example 9.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="idm225506287856" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-cacheenable"><h6>Example 9.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="idm261750385648" 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 9.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="idm225444470528" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-cachelastmodifiedfactor"><h6>Example 9.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="idm261750394528" 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 9.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="idm225439468304" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-cachemaxexpire"><h6>Example 9.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="idm261733610576" 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">
@@ -436,53 +436,53 @@ Syntax OK</pre><div class="para">
<code class="option">Off</code>
</td><td class="">
Disables caching the content-negotiated documents.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-cachenegotiateddocs"><h6>Example 9.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="idm225475002304" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-cachenegotiateddocs"><h6>Example 9.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="idm261753188624" 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="idm225475007776" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">CacheRoot <em class="replaceable"><code>directory</code></em></pre><a id="idm261726525568" 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 9.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="idm225436035072" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-cacheroot"><h6>Example 9.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="idm261726532224" 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="idm225436041136" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">CustomLog <em class="replaceable"><code>path</code></em> <em class="replaceable"><code>format</code></em></pre><a id="idm261752687264" 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 9.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="idm225462301168" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-customlog"><h6>Example 9.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="idm261730370544" 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 9.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="idm225463342976" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-defaulticon"><h6>Example 9.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="idm261730379456" 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 9.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="idm225463352304" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-defaulttype"><h6>Example 9.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="idm261739465888" 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 9.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="idm225461472544" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-deny"><h6>Example 9.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="idm261740797264" 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 9.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="idm225463169632" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-directoryindex"><h6>Example 9.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="idm261745977920" 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="idm225463174688" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">DocumentRoot <em class="replaceable"><code>directory</code></em></pre><a id="idm261745982576" 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 9.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="idm225497867840" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-documentroot"><h6>Example 9.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="idm261745988736" 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 9.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="idm225454288272" class="indexterm"></a>
+ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261754506144" 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="idm225454294656" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">ErrorLog <em class="replaceable"><code>path</code></em></pre><a id="idm261726271632" 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 9.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="idm225504117776" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-errorlog"><h6>Example 9.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="idm261726277424" 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">
@@ -499,19 +499,19 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">Off</code>
</td><td class="">
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 9.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="idm225438869408" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-extendedstatus"><h6>Example 9.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="idm261746452752" 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 9.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="idm225436168640" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-group"><h6>Example 9.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="idm261760820096" 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 9.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="idm225481024480" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-headername"><h6>Example 9.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="idm261749763968" 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">
@@ -534,17 +534,17 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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 9.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="idm225463529712" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-hostnamelookups"><h6>Example 9.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="idm261735254256" 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="idm225463534624" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">Include <em class="replaceable"><code>filename</code></em></pre><a id="idm261753751712" 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 9.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="idm225477589936" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-include"><h6>Example 9.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="idm261753762096" 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 9.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="idm225477598080" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-indexignore"><h6>Example 9.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="idm261718620704" 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">
@@ -649,7 +649,7 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">XHTML</code>
</td><td class="">
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 9.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="idm225444135136" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-indexoptions"><h6>Example 9.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="idm261730955936" 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">
@@ -668,33 +668,33 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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 9.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="idm225458225120" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-keepalive"><h6>Example 9.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="idm261773679472" 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 9.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="idm225445929344" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-keepalivetimeout"><h6>Example 9.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="idm261718395056" 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 9.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="idm225477370928" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-languagepriority"><h6>Example 9.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="idm261744338544" 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 9.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="idm225466393872" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-listen"><h6>Example 9.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="idm261745059056" 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="idm225464122608" class="indexterm"></a><a id="idm225464125072" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">LoadModule <em class="replaceable"><code>name</code></em> <em class="replaceable"><code>path</code></em></pre><a id="idm261740443024" class="indexterm"></a><a id="idm261740445488" class="indexterm"></a><div class="para">
The <em class="replaceable"><code>name</code></em> has to be a valid identifier of the required module. The <em class="replaceable"><code>path</code></em> refers to an existing module file, and must be relative to the directory in which the libraries are placed (that is, <code class="filename">/usr/lib/httpd/</code> on 32-bit and <code class="filename">/usr/lib64/httpd/</code> on 64-bit systems by default).
</div><div class="para">
See <a class="xref" href="ch-Web_Servers.html#s2-apache-dso">Section 9.1.5, “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 9.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="idm225464133536" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-loadmodule"><h6>Example 9.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="idm261718869904" 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">
@@ -735,7 +735,7 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">%{<em class="replaceable"><code>field</code></em>}</code>
</td><td class="">
Represents the content of the HTTP header <em class="replaceable"><code>field</code></em>. The common options include <code class="option">%{Referer}</code> (the URL of the web page that referred the client to the server) and <code class="option">%{User-Agent}</code> (the type of the web browser making the request).
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-logformat"><h6>Example 9.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="idm225467767120" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-logformat"><h6>Example 9.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="idm261786002368" 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">
@@ -776,12 +776,12 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">debug</code>
</td><td class="">
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 9.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="idm225472359536" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-loglevel"><h6>Example 9.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="idm261735284160" 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 9.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="idm225474955152" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-maxkeepaliverequests"><h6>Example 9.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="idm261758057552" 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">
@@ -790,7 +790,7 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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 9.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="idm225439755744" class="indexterm"></a>
+ </div></div></div><div class="example" id="example-apache-httpdconf-namevirtualhost"><h6>Example 9.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="idm261760102544" 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">
@@ -835,7 +835,7 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">None</code>
</td><td class="">
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 9.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="idm225470987440" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-options"><h6>Example 9.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="idm261752876992" 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">
@@ -852,12 +852,12 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">deny,allow</code>
</td><td class="">
<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 9.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="idm225458199136" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-order"><h6>Example 9.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="idm261758114400" 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="idm225480055680" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">PidFile <em class="replaceable"><code>path</code></em></pre><a id="idm261749727824" 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 9.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="idm225480055040" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-pidfile"><h6>Example 9.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="idm261749735440" 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">
@@ -874,12 +874,12 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">Off</code>
</td><td class="">
Disables forward proxy requests.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-proxyrequests"><h6>Example 9.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="idm225469111200" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-proxyrequests"><h6>Example 9.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="idm261725228000" 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 9.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="idm225471390832" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-readmename"><h6>Example 9.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="idm261732129408" 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">
@@ -904,14 +904,14 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">gone</code>
</td><td class="">
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="idm225449712208" class="indexterm"></a><div class="para">
+ </td></tr></tbody></table></div></div><br class="table-break" /><a id="idm261751826272" 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 9.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="idm225458979536" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-redirect"><h6>Example 9.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="idm261717469888" 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="idm225458976752" class="indexterm"></a><div class="para">
+ </div><a id="idm261717469264" 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.
@@ -922,26 +922,26 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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="idm225477783440" class="indexterm"></a>
+</Directory></pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261730312496" 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 at localhost</code>.
</div><div class="para">
This directive is commonly set to <code class="literal">webmaster@<em class="replaceable"><code>hostname</code></em></code>, where <em class="replaceable"><code>hostname</code></em> is the address of the server. Once set, alias <code class="literal">webmaster</code> to the person responsible for the web server in <code class="filename">/etc/aliases</code>, and as superuser, run the <code class="command">newaliases</code> command.
- </div><div class="example" id="example-apache-httpdconf-serveradmin"><h6>Example 9.59. Using the ServerAdmin directive</h6><div class="example-contents"><pre class="programlisting">ServerAdmin webmaster at penguin.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225435918112" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-serveradmin"><h6>Example 9.59. Using the ServerAdmin directive</h6><div class="example-contents"><pre class="programlisting">ServerAdmin webmaster at penguin.example.com</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261730324000" 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 9.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="idm225459749984" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-servername"><h6>Example 9.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="idm261731156192" 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="idm225459754976" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">ServerRoot <em class="replaceable"><code>directory</code></em></pre><a id="idm261755458096" 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 9.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="idm225450566224" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpd-serverroot"><h6>Example 9.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="idm261755467312" 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">
@@ -962,7 +962,7 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">EMail</code>
</td><td class="">
Enables appending the server name, version, and the email address of the system administrator as specified by the <code class="option">ServerAdmin</code> directive to server-generated pages.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-serversignature"><h6>Example 9.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="idm225483186880" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-serversignature"><h6>Example 9.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="idm261724624880" 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">
@@ -997,26 +997,26 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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 9.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="idm225458694256" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-servertokens"><h6>Example 9.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="idm261723240656" 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 9.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="idm225455331440" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-suexecusergroup"><h6>Example 9.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="idm261778970432" 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 9.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="idm225481908176" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-timeout"><h6>Example 9.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="idm261778981520" 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="idm225481912992" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">TypesConfig <em class="replaceable"><code>path</code></em></pre><a id="idm261748102912" 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 9.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="idm225476374848" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-typesconfig"><h6>Example 9.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="idm261773665872" 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">
@@ -1037,17 +1037,17 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
<code class="option">DNS</code>
</td><td class="">
Disables the use of the name that is specified by the <code class="option">ServerName</code> directive. The hostname determined by a reverse DNS lookup is used instead.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-usecanonicalname"><h6>Example 9.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="idm225476386192" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="example-apache-httpdconf-usecanonicalname"><h6>Example 9.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="idm261756692576" 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 9.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="idm225454620800" class="indexterm"></a>
+ </div><div class="example" id="example-apache-httpdconf-user"><h6>Example 9.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="idm261754814064" 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="idm225454626048" class="indexterm"></a><div class="para">
+ </div><pre class="programlisting">UserDir <em class="replaceable"><code>option</code></em></pre><a id="idm261754817552" 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 9.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 9.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 class="">
Option
@@ -1068,9 +1068,9 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
All files in this directory must be set accordingly.
</div></div></div><div class="example" id="example-apache-httpdconf-userdir"><h6>Example 9.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">9.1.4.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="idm225475819264" class="indexterm"></a><div class="para">
+ </div><a id="idm261718797632" 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 class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225475823744" class="indexterm"></a>
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261718802096" 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">
@@ -1111,57 +1111,57 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
Note that for the <code class="filename">/etc/httpd/conf.d/ssl.conf</code> file to be present, the <span class="package">mod_ssl</span> needs to be installed. See <a class="xref" href="ch-Web_Servers.html#s2-apache-mod_ssl">Section 9.1.7, “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">9.1.4.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="idm225438932288" class="indexterm"></a><div class="para">
+ </div><a id="idm261735393216" 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 class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225472555088" class="indexterm"></a>
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261757325120" 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 9.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="idm225461998176" class="indexterm"></a>
+ </div><div class="example" id="example-apache-mpm-maxclients"><h6>Example 9.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="idm261758687600" 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 9.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="idm225462008688" class="indexterm"></a>
+ </div><div class="example" id="example-apache-mpm-maxrequestsperchild"><h6>Example 9.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="idm261758697936" 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 9.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="idm225477686064" class="indexterm"></a>
+ </div><div class="example" id="example-apache-mpm-maxspareservers"><h6>Example 9.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="idm261785641072" 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 9.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="idm225463615456" class="indexterm"></a>
+ </div><div class="example" id="example-apache-mpm-maxsparethreads"><h6>Example 9.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="idm261734709840" 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 9.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="idm225462456656" class="indexterm"></a>
+ </div><div class="example" id="example-apache-mpm-minspareservers"><h6>Example 9.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="idm261777586688" 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 9.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="idm225462466064" class="indexterm"></a>
+ </div><div class="example" id="example-apache-mpm-minsparethreads"><h6>Example 9.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="idm261753602368" 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 9.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="idm225480235792" class="indexterm"></a>
+ </div><div class="example" id="example-apache-mpm-startservers"><h6>Example 9.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="idm261753609168" 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 9.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">9.1.5. Working with Modules</h3></div></div></div><a id="idm225462831728" class="indexterm"></a><a id="idm225462827056" class="indexterm"></a><div class="para">
+ </div><div class="example" id="example-apache-mpm-threadsperchild"><h6>Example 9.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">9.1.5. Working with Modules</h3></div></div></div><a id="idm261754638432" class="indexterm"></a><a id="idm261754639744" 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">9.1.5.1. Loading a Module</h4></div></div></div><a id="idm225455436752" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-apache-dso-loading"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.5.1. Loading a Module</h4></div></div></div><a id="idm261715226976" 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 9.1.4.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 9.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. See <a class="xref" href="ch-Web_Servers.html#s3-apache-running-restarting">Section 9.1.3.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">9.1.5.2. Writing a Module</h4></div></div></div><a id="idm225455445888" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-apache-dso-writing"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.5.2. Writing a Module</h4></div></div></div><a id="idm261728451792" class="indexterm"></a><div class="para">
If you intend to create a new DSO module, make sure you have the <span class="package">httpd-devel</span> package installed. To do so, enter the following command as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">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.
@@ -1169,7 +1169,7 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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">9.1.6. Setting Up Virtual Hosts</h3></div></div></div><a id="idm225448684464" class="indexterm"></a><a id="idm225448685936" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s2-apache-virtualhosts"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.6. Setting Up Virtual Hosts</h3></div></div></div><a id="idm261728461376" class="indexterm"></a><a id="idm261728463168" class="indexterm"></a><div class="para">
The Apache HTTP Server's built in virtual hosting allows the server to provide different information based on which IP address, host name, or port is being requested.
</div><div class="para">
To create a name-based virtual host, copy the example configuration file <code class="filename">/usr/share/doc/httpd-<em class="replaceable"><code>VERSION</code></em>/httpd-vhosts.conf</code> into the <code class="filename">/etc/httpd/conf.d/</code> directory, and replace the <code class="literal">@@Port@@</code> and <code class="literal">@@ServerRoot@@</code> placeholder values. Customize the options according to your requirements as shown in <a class="xref" href="ch-Web_Servers.html#example-apache-virtualhosts-config">Example 9.80, “Example virtual host configuration”</a>.
@@ -1187,13 +1187,13 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
If you configure a virtual host to listen on a non-default port, make sure you update the <code class="option">Listen</code> directive in the global settings section of the <code class="filename">/etc/httpd/conf/httpd.conf</code> file accordingly.
</div></div></div><div class="para">
To activate a newly created virtual host, the web server has to be restarted first. See <a class="xref" href="ch-Web_Servers.html#s3-apache-running-restarting">Section 9.1.3.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">9.1.7. Setting Up an SSL Server</h3></div></div></div><a id="idm225447797008" class="indexterm"></a><a id="idm225447789664" class="indexterm"></a><a id="idm225447791408" class="indexterm"></a><a id="idm225447796368" class="indexterm"></a><a id="idm225447795088" class="indexterm"></a><a id="idm225447797488" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s2-apache-mod_ssl"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">9.1.7. Setting Up an SSL Server</h3></div></div></div><a id="idm261787985856" class="indexterm"></a><a id="idm261787987280" class="indexterm"></a><a id="idm261787989712" class="indexterm"></a><a id="idm261787991296" class="indexterm"></a><a id="idm261787992912" class="indexterm"></a><a id="idm261749494960" 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">9.1.7.1. An Overview of Certificates and Security</h4></div></div></div><a id="idm225507259760" class="indexterm"></a><a id="idm225507260880" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-apache-mod_ssl-certificates"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.7.1. An Overview of Certificates and Security</h4></div></div></div><a id="idm261749505152" class="indexterm"></a><a id="idm261740299216" 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="idm225443705920" class="indexterm"></a><a id="idm225443704128" class="indexterm"></a><div class="para">
+ </div><a id="idm261740304928" class="indexterm"></a><a id="idm261740306224" class="indexterm"></a><div class="para">
To provide secure communications using SSL, an SSL server must use a digital certificate signed by a <em class="firstterm">Certificate Authority</em> (<acronym class="acronym">CA</acronym>). The certificate lists various attributes of the server (that is, the server host name, the name of the company, its location, etc.), and the signature produced using the CA's private key. This signature ensures that a particular certificate authority has signed the certificate, and that the certificate has not been modified in any way.
</div><div class="para">
When a web browser establishes a new SSL connection, it checks the certificate provided by the web server. If the certificate does not have a signature from a trusted CA, or if the host name listed in the certificate does not match the host name used to establish the connection, it refuses to communicate with the server and usually presents a user with an appropriate error message.
@@ -1223,9 +1223,9 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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">9.1.7.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, enter the following command as <code class="systemitem">root</code>:
- </div><pre class="screen">~]# <code class="command">yum install mod_ssl openssl</code></pre><a id="idm225447265200" class="indexterm"></a><div class="para">
+ </div><pre class="screen">~]# <code class="command">yum install mod_ssl openssl</code></pre><a id="idm261750141312" 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 9.1.3.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">9.1.7.3. Using an Existing Key and Certificate</h4></div></div></div><a id="idm225467233296" class="indexterm"></a><a id="idm225467235248" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-apache-mod_ssl-keypair"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">9.1.7.3. Using an Existing Key and Certificate</h4></div></div></div><a id="idm261750146896" class="indexterm"></a><a id="idm261750148768" 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>
@@ -1246,7 +1246,7 @@ ErrorDocument 404 /404-not_found.html</pre></div></div><br class="example-break"
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 9.1.3.3, “Restarting the Service”</a>.
</div><div class="example" id="example-apache-mod_ssl-keypair"><h6>Example 9.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">9.1.7.4. Generating a New Key and Certificate</h4></div></div></div><a id="idm225471068848" class="indexterm"></a><a id="idm225471070768" class="indexterm"></a><div class="para">
+~]# <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">9.1.7.4. Generating a New Key and Certificate</h4></div></div></div><a id="idm261740769376" class="indexterm"></a><a id="idm261740771136" class="indexterm"></a><div class="para">
In order to generate a new key and certificate pair, the <span class="package">crypto-utils</span> package must be installed on the system. To install it, enter the following command as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">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.
@@ -1309,18 +1309,18 @@ SSLCertificateKeyFile /etc/pki/tls/private/<em class="replaceable"><code>hostnam
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 9.1.3.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">9.1.8. Additional Resources</h3></div></div></div><div class="para">
To learn more about the Apache HTTP Server, see the following resources.
- </div><h4 id="bh-The_Apache_HTTP_Server-Installed_Documentation">Installed Documentation</h4><a id="idm225446308304" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><h4 id="bh-The_Apache_HTTP_Server-Installed_Documentation">Installed Documentation</h4><a id="idm261750096256" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="filename">httpd(8)</code> — The manual page for the <code class="systemitem">httpd</code> service containing the complete list of its command-line options.
</div></li><li class="listitem"><div class="para">
<code class="filename">genkey(1)</code> — The manual page for <code class="command">genkey</code> utility, provided by the <span class="package">crypto-utils</span> package.
</div></li><li class="listitem"><div class="para">
<code class="filename">apachectl(8)</code> — The manual page for the Apache HTTP Server Control Interface.
- </div></li></ul></div><h4 id="bh-The_Apache_HTTP_Server-Installable_Documentation">Installable Documentation</h4><a id="idm225442341920" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div></li></ul></div><h4 id="bh-The_Apache_HTTP_Server-Installable_Documentation">Installable Documentation</h4><a id="idm261715167040" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://localhost/manual/">http://localhost/manual/</a> — The official documentation for the Apache HTTP Server with the full description of its directives and available modules. Note that in order to access this documentation, you must have the <span class="package">httpd-manual</span> package installed, and the web server must be running.
</div><div class="para">
Before accessing the documentation, issue the following commands as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">yum install httpd-manual</code>
-~]# <code class="command">apachectl graceful</code></pre></li></ul></div><h4 id="bh-The_Apache_HTTP_Server-Online_Documentation">Online Documentation</h4><a id="idm225467524672" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+~]# <code class="command">apachectl graceful</code></pre></li></ul></div><h4 id="bh-The_Apache_HTTP_Server-Online_Documentation">Online Documentation</h4><a id="idm261741052672" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://httpd.apache.org/">http://httpd.apache.org/</a> — The official website for the Apache HTTP Server with documentation on all the directives and default modules.
</div></li><li class="listitem"><div class="para">
ulink url="http://www.modssl.org/" /> — The official website for the <span class="application"><strong>mod_ssl</strong></span> module.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Working_with_Kernel_Modules.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Working_with_Kernel_Modules.html
index 6255c43..08a8f3d 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Working_with_Kernel_Modules.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Working_with_Kernel_Modules.html
@@ -1,12 +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>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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Working with Kernel Modules</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Kernel_Module_and_Driver_Configuration.html" title="Part VI. 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 class="toc"><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="secti
on"><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="s1-kernel-modules-additional-resources.html">21.7. Additional Resources</a></span></dt></dl></div><a id="idm225451431312" class="indexterm"></a><a id="idm225464892224" class="indexterm"></a><a id="idm225480407920" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Kernel_Module_and_Driver_Configuration.html" title="Part VI. Kernel, Module and Driver Configuration" /><link rel="prev" href="s2-kernel-boot-loader-pseries.html" title="21.6.3. Configuring the YABOOT Boot Loader" /><link rel="next" href="sec-Displaying_Information_About_a_Module.html" title="22.2. Displaying Information About a Module" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class=
"previous"><a accesskey="p" href="s2-kernel-boot-loader-pseries.html"><strong>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 22. Working with Kernel Modules</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="sec-Displaying_Information_About_a_Module.html">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="sec-Loading_a_Module.html">22.3. Loading a Module</a></span></dt><dt><span class="section"><a href="sec-Unloading_a_Module.html">22.4. Unloading a Module</a></span></dt><dt><span class="secti
on"><a href="sec-Setting_Module_Parameters.html">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="sec-Persistent_Module_Loading.html">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="sect-signing-kernel-modules-for-secure-boot.html">22.7. Signing Kernel Modules for Secure Boot</a></span></dt><dd><dl><dt><span class="section"><a href="sect-signing-kernel-modules-for-secure-boot.html#sect-prerequisites">22.7.1. Prerequisites</a></span></dt><dt><span class="section"><a href="sect-kernel-module-authentication.html">22.7.2. Kernel Module Authentication</a></span></dt><dt><span class="section"><a href="sect-generating-a-public-private-x509-key-pair.html">22.7.3. Generating a Public and Private X.509 Key Pair</a></span></dt><dt><span class="section"><a href="sect-enrolling-public-key-on-target-system.html">22.7.4. Enrolling Public Key on Target System</a></span></dt><dt><span class="section"><a href="sect-signing-ker
nel-module-with-the-private-key.html">22.7.5. Signing Kernel Module with the Private Key</a></span></dt><dt><span class="section"><a href="sect-loading-signed-kernel-module.html">22.7.6. Loading Signed Kernel Module</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kernel-modules-additional-resources.html">22.8. Additional Resources</a></span></dt></dl></div><a id="idm261726827440" class="indexterm"></a><a id="idm261747761696" class="indexterm"></a><a id="idm261739541216" 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,
@@ -29,7 +29,7 @@
</div><pre class="screen">~]# <code class="command">yum install kmod</code>
</pre><div class="para">
For more information on installing packages with Yum, see <a class="xref" href="sec-Installing.html">Section 5.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">21.1. Listing Currently-Loaded Modules</h2></div></div></div><a id="idm225447644352" class="indexterm"></a><a id="idm225468747312" class="indexterm"></a><a id="idm225468745232" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="sec-Listing_Currently-Loaded_Modules"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">22.1. Listing Currently-Loaded Modules</h2></div></div></div><a id="idm261788239744" class="indexterm"></a><a id="idm261760381072" class="indexterm"></a><a id="idm261760378992" 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>
@@ -71,7 +71,7 @@ nf_nat 21798 4 nf_nat_ipv4,nf_nat_ipv6,ip6table_nat,iptable_nat
</div></li><li class="listitem"><div class="para">
the amount of memory it uses; and,
</div></li><li class="listitem"><div class="para">
- the sum total of processes that are using the module and other modules which depend on it, followed by a list of the names of those modules, if there are any. Using this list, you can first unload all the modules depending the module you want to unload. For more information, see <a class="xref" href="sec-Unloading_a_Module.html">Section 21.4, “Unloading a Module”</a>.
- </div></li></ul></div><a id="idm225446724832" class="indexterm"></a><div class="para">
+ the sum total of processes that are using the module and other modules which depend on it, followed by a list of the names of those modules, if there are any. Using this list, you can first unload all the modules depending the module you want to unload. For more information, see <a class="xref" href="sec-Unloading_a_Module.html">Section 22.4, “Unloading a Module”</a>.
+ </div></li></ul></div><a id="idm261745726800" 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>
\ No newline at end of file
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kernel-boot-loader-pseries.html"><strong>Prev</strong>21.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>22.2. Displaying Information About a Module</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Working_with_the_GRUB_2_Boot_Loader.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Working_with_the_GRUB_2_Boot_Loader.html
new file mode 100644
index 0000000..30c8347
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-Working_with_the_GRUB_2_Boot_Loader.html
@@ -0,0 +1,47 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>Chapter 20. Working with the GRUB 2 Boot Loader</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="part-Kernel_Module_and_Driver_Configuration.html" title="Part VI. Kernel, Module and Driver Configuration" /><link rel="prev" href="part-Kernel_Module_and_Driver_Configuration.html" title="Part VI. Kernel, Module and Driver Configuration" /><link rel="next" href="sec-Customizing_GRUB_2_Menu.html" title="20.2. Customizing GRUB 2 Menu" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previo
us"><a accesskey="p" href="part-Kernel_Module_and_Driver_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Customizing_GRUB_2_Menu.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="chapter" id="ch-Working_with_the_GRUB_2_Boot_Loader" lang="en-US"><div class="titlepage"><div><div><h2 class="title">Chapter 20. Working with the GRUB 2 Boot Loader</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-Working_with_the_GRUB_2_Boot_Loader.html#sec-Configuring_the_GRUB_2_Boot_Loader">20.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="sec-Customizing_GRUB_2_Menu.html">20.2. Customizing GRUB 2 Menu</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Customizing_GRUB_2_Menu.html#sec-Changing_the_Default_Boot_Entry">20.2.1. Changing the Default Boot Entry</a></span></dt><dt><span class="section"><a href="sec-Editing_an_Entry.html">20.
2.2. Editing an Entry</a></span></dt><dt><span class="section"><a href="sec-Adding_a_new_Entry.html">20.2.3. Adding a new Entry</a></span></dt><dt><span class="section"><a href="sec-Using_only_a_Custom_Menu.html">20.2.4. Creating a Custom Menu</a></span></dt></dl></dd><dt><span class="section"><a href="sec-GRUB_2_Password_Protection.html">20.3. GRUB 2 Password Protection</a></span></dt><dd><dl><dt><span class="section"><a href="sec-GRUB_2_Password_Protection.html#sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries">20.3.1. Setting Up Users and Password Protection, Specifying Menu Entries</a></span></dt><dt><span class="section"><a href="sec-Password_Encryption.html">20.3.2. Password Encryption</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Reinstalling_GRUB_2.html">20.4. Reinstalling GRUB 2</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Reinstalling_GRUB_2.html#sec-Using_the_grub2-install_Command">20.4.1. Using the grub2-insta
ll Command</a></span></dt><dt><span class="section"><a href="sec-Resetting_and_Reinstalling_GRUB_2.html">20.4.2. Resetting and Reinstalling GRUB 2</a></span></dt></dl></dd><dt><span class="section"><a href="sec-GRUB_2_over_Serial_Console.html">20.5. GRUB 2 over Serial Console</a></span></dt><dd><dl><dt><span class="section"><a href="sec-GRUB_2_over_Serial_Console.html#sec-Configuring_GRUB_2">20.5.1. Configuring GRUB 2</a></span></dt><dt><span class="section"><a href="sec-Using_screen_to_Connect_to_the_Serial_Console.html">20.5.2. Using screen to Connect to the Serial Console</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Terminal_Menu_Editing_During_Boot.html">20.6. Terminal Menu Editing During Boot</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Terminal_Menu_Editing_During_Boot.html#sec-Booting_to_Rescue_Mode">20.6.1. Booting to Rescue Mode</a></span></dt><dt><span class="section"><a href="sec-Booting_to_Emergency_Mode.html">20.6.2. Booting t
o Emergency Mode</a></span></dt><dt><span class="section"><a href="sec-Changing_and_Resetting_the_Root_Password.html">20.6.3. Changing and Resetting the Root Password</a></span></dt></dl></dd><dt><span class="section"><a href="sec-UEFI_Secure_Boot.html">20.7. UEFI Secure Boot</a></span></dt><dd><dl><dt><span class="section"><a href="sec-UEFI_Secure_Boot.html#sec-UEFI_Secure_Boot_Support_in_Fedora">20.7.1. UEFI Secure Boot Support in Fedora</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html">20.8. Additional Resources</a></span></dt></dl></div><a id="idm261722678736" class="indexterm"></a><a id="idm261724797264" class="indexterm"></a><a id="idm261738235904" class="indexterm"></a><a id="idm261715437568" class="indexterm"></a><div class="para">
+ Fedora 21 is distributed with the GNU GRand Unified Boot loader (GRUB) version 2 boot loader, which allows the user to select an operating system or kernel to be loaded at system boot time. GRUB 2 also allows the user to pass arguments to the kernel.
+ </div><div class="section" id="sec-Configuring_the_GRUB_2_Boot_Loader"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.1. Configuring the GRUB 2 Boot Loader</h2></div></div></div><div class="para">
+ GRUB 2 reads its configuration from the <code class="filename">/boot/grub2/grub.cfg</code> file on traditional BIOS-based machines and from the <code class="filename">/boot/efi/EFI/redhat/grub.cfg</code> file on UEFI machines. This file contains menu information, however, it is not supposed to be edited as it is generated by the <span class="application"><strong>/usr/sbin/grub2-mkconfig</strong></span> utility based on Linux kernels located in the <code class="filename">/boot/</code> directory, template files located in <code class="filename">/etc/grub.d/</code>, and custom settings in the <code class="filename">/etc/default/grub</code> file. Any manual edits could therefore cause the changes to be lost during updates. The GRUB 2 configuration file, <code class="filename">grub.cfg</code>, is automatically updated each time a new kernel is installed. Note that any changes to <code class="filename">/etc/default/grub</code> require rebuilding the <code class="filename">grub.
cfg</code> file. To update the GRUB 2 configuration file manually, use the <code class="command">grub2-mkconfig <code class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div class="para">
+ On UEFI-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div><div class="para">
+ Among various code snippets and directives, the <code class="filename">grub.cfg</code> configuration file contains one or more <code class="literal">menuentry</code> blocks, each representing a single GRUB 2 boot menu entry. These blocks always start with the <code class="literal">menuentry</code> keyword followed by a title, list of options, and an opening curly bracket, and end with a closing curly bracket. Anything between the opening and closing bracket should be indented. For example, the following is a sample <code class="literal">menuentry</code> block for Fedora 21 with Linux kernel 3.17.4-301.fc21.x86_64:
+ </div><pre class="programlisting">
+menuentry 'Fedora, with Linux 3.17.4-301.fc21.x86_64' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.17.4-301.fc21.x86_64-advanced-effee860-8d55-4e4a-995e-b4c88f9ac9f0' {
+ load_video
+ set gfxpayload=keep
+ insmod gzio
+ insmod part_msdos
+ insmod ext2
+ set root='hd0,msdos1'
+ if [ x$feature_platform_search_hint = xy ]; then
+ search --no-floppy --fs-uuid --set=root --hint='hd0,msdos1' f19c92f4-9ead-4207-b46a-723b7a2c51c8
+ else
+ search --no-floppy --fs-uuid --set=root f19c92f4-9ead-4207-b46a-723b7a2c51c8
+ fi
+ linux16 /vmlinuz-3.17.4-301.fc21.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
+ initrd16 /initramfs-3.17.4-301.fc21.x86_64.img
+}
+</pre><div class="para">
+ Each <code class="literal">menuentry</code> block that represents an installed Linux kernel contains <code class="literal">linux</code> on 64-bit IBM POWER Series, <code class="literal">linux16</code> on x86_64 BIOS-based systems, and <code class="literal">linuxefi</code> on UEFI-based systems. Then the <code class="literal">initrd</code> directives followed by the path to the kernel and the <code class="systemitem">initramfs</code> image respectively. If a separate <code class="filename">/boot</code> partition was created, the paths to the kernel and the <code class="systemitem">initramfs</code> image are relative to <code class="filename">/boot</code>. In the example above, the <code class="literal">initrd /initramfs-3.8.0-0.40.el7.x86_64.img</code> line means that the <code class="systemitem">initramfs</code> image is actually located at <code class="filename">/boot/initramfs-3.8.0-0.40.el7.x86_64.img</code> when the <code class="systemitem">root</code> file system is
mounted, and likewise for the kernel path.
+ </div><div class="para">
+ The kernel version number as given on the <code class="literal">linux16 /vmlinuz-kernel_version</code> line must match the version number of the <code class="systemitem">initramfs</code> image given on the <code class="literal">initrd /initramfs-kernel_version.img</code> line of each <code class="literal">menuentry</code> block. For more information on how to verify the initial RAM disk image, see <a class="xref" href="sec-Verifying_the_Initial_RAM_Disk_Image.html">Section 21.5, “Verifying the Initial RAM Disk Image”</a>.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ In <code class="literal">menuentry</code> blocks, the <code class="computeroutput">initrd</code> directive must point to the location (relative to the <code class="filename">/boot/</code> directory if it is on a separate partition) of the <code class="filename">initramfs</code> file corresponding to the same kernel version. This directive is called <code class="literal">initrd</code> because the previous tool which created initial RAM disk images, <code class="command">mkinitrd</code>, created what were known as <code class="systemitem">initrd</code> files. The <code class="filename">grub.cfg</code> directive remains <code class="systemitem">initrd</code> to maintain compatibility with other tools. The file-naming convention of systems using the <code class="command">dracut</code> utility to create the initial RAM disk image is <code class="filename">initramfs-<em class="replaceable"><code>kernel_version</code></em>.img</code>.
+ </div><div class="para">
+ For information on using <span class="application"><strong>Dracut</strong></span>, see <a class="xref" href="sec-Verifying_the_Initial_RAM_Disk_Image.html">Section 21.5, “Verifying the Initial RAM Disk Image”</a>.
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Kernel_Module_and_Driver_Configuration.html"><strong>Prev</strong>Part VI. 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="sec-Customizing_GRUB_2_Menu.html"><strong>Next</strong>20.2. Customizing GRUB 2 Menu</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-yum.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-yum.html
index 481aaad..a151937 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-yum.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch-yum.html
@@ -9,14 +9,14 @@
</script><link rel="home" href="index.html" title="System Administrator's 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="5.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</stro
ng></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 5. Yum</h2></div></div></div><div class="toc"><dl class="toc"><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_and_Updating_Packages">5.1. Checking For and Updating Packages</a></span></dt><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_Updates">5.1.1. Checking For Updates</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Updating_Packages">5.1.2. Updating Packages</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Preserving_Configuration_File_Changes">5.1.3. Preserving Configuration File Changes</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html">5.2. Packages and Package Groups</a></span></dt><dd><dl><dt><span cla
ss="section"><a href="sec-Packages_and_Package_Groups.html#sec-Searching_Packages">5.2.1. Searching Packages</a></span></dt><dt><span class="section"><a href="sec-Listing_Packages.html">5.2.2. Listing Packages</a></span></dt><dt><span class="section"><a href="sec-Displaying_Package_Information.html">5.2.3. Displaying Package Information</a></span></dt><dt><span class="section"><a href="sec-Installing.html">5.2.4. Installing Packages</a></span></dt><dt><span class="section"><a href="sec-Removing.html">5.2.5. Removing Packages</a></span></dt><dt><span class="section"><a href="sec-Yum-Transaction_History.html">5.2.6. Working with Transaction History</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html">5.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">5.3.1. Setting [main] Options</a></span></dt><dt><span
class="section"><a href="sec-Setting_repository_Options.html">5.3.2. Setting [repository] Options</a></span></dt><dt><span class="section"><a href="sec-Using_Yum_Variables.html">5.3.3. Using Yum Variables</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Current_Configuration.html">5.3.4. Viewing the Current Configuration</a></span></dt><dt><span class="section"><a href="sec-Managing_Yum_Repositories.html">5.3.5. Adding, Enabling, and Disabling a Yum Repository</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Yum_Repository.html">5.3.6. Creating a Yum Repository</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Yum_Plugins.html">5.4. Yum Plug-ins</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">5.4.1. Enabling, Configuring, and Disabling Yum Plug-ins</a></span></dt><dt><span class="section"><a href="sec-Installing_More_Yum_Plugins.html">5.4.2. Insta
lling Additional Yum Plug-ins</a></span></dt><dt><span class="section"><a href="sec-Plugin_Descriptions.html">5.4.3. Plug-in Descriptions</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Additional_Resources.html">5.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. Yum 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. Yum can be configured with new, additional repositories, or <em class="firstterm">package sources</em>, and also provides many plug-ins which enhance and extend its capabilities. Yum is able to perform many of the same tasks that <span class="application"><strong>RPM</strong></span> can; additionally, many of the command line options are similar. Yum 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">
- Yum 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, Yum will refuse to install any packages not GPG-signed with the correct key for that repository. This means that you can trust that the <span class="application"><strong>RPM</strong></span> packages you download and install on your system are from a trusted source, such as The Fedora Project, and were not modified during transfer. See <a class="xref" href="sec-Configuring_Yum_and_Yum_Repositories.html">Section 5.3, “Configuring Yum and Yum Repositories”</a> for details on enabling signature-checking with Yum, 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="applicatio
n"><strong>RPM</strong></span> packages in general.
+ Yum 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, Yum will refuse to install any packages not GPG-signed with the correct key for that repository. This means that you can trust that the <span class="application"><strong>RPM</strong></span> packages you download and install on your system are from a trusted source, such as The Fedora Project, and were not modified during transfer. See <a class="xref" href="sec-Configuring_Yum_and_Yum_Repositories.html">Section 5.3, “Configuring Yum and Yum Repositories”</a> for details on enabling signature-checking with Yum, or <a class="xref" href="s1-check-rpm-sig.html">Section A.3.2, “Checking Package Signatures”</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">
Yum 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 Yum is a worthwhile investment because it is often the fastest way to perform system administration tasks, and it provides capabilities beyond those provided by the <span class="application"><strong>PackageKit</strong></span> graphical package management tools.
</div><div class="note" id="note-Note_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">5.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">5.1.1. Checking For Updates</h3></div></div></div><a id="idm225444686400" class="indexterm"></a><div class="para">
+ </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">5.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">5.1.1. Checking For Updates</h3></div></div></div><a id="idm261745838096" class="indexterm"></a><div class="para">
To see which installed packages on your system have updates available, use the following command:
</div><pre class="synopsis"><code class="command">yum</code> <code class="option">check-update</code></pre><div class="para">
For example:
@@ -49,9 +49,9 @@ yum.noarch 3.2.29-5.fc15 fedora</pre><
<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 kernel package), Yum 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">kernel-firmware</span>, <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">5.1.2. Updating Packages</h3></div></div></div><a id="idm225462846976" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="sec-Updating_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.1.2. Updating Packages</h3></div></div></div><a id="idm261721657328" class="indexterm"></a><div class="para">
You can choose to update a single package, multiple packages, or all packages at once. If any dependencies of the package (or packages) you update have updates available themselves, then they are updated too.
- </div><h4 id="bh-Updating_a_Single_Package"> Updating a Single Package </h4><a id="idm225462844240" class="indexterm"></a><div class="para">
+ </div><h4 id="bh-Updating_a_Single_Package"> Updating a Single Package </h4><a id="idm261721654592" class="indexterm"></a><div class="para">
To update a single package, run the following command as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">yum</code> <code class="option">update</code> <em class="replaceable"><code>package_name</code></em></pre><div class="para">
For example, to update the <span class="package">udev</span> package, type:
@@ -92,11 +92,11 @@ Is this ok [y/N]:</pre><div class="para">
</div></li></ol></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). See <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 id="bh-Updating_All_Packages_and_Their_Dependencies"> Updating All Packages and Their Dependencies </h4><a id="idm225481068016" class="indexterm"></a><div class="para">
+ When using <span class="application"><strong>RPM</strong></span>, on the other hand, it is important to use the <code class="command">rpm -i kernel</code> command (which installs a new kernel) instead of <code class="command">rpm -u kernel</code> (which <span class="emphasis"><em>replaces</em></span> the current kernel). See <a class="xref" href="s1-rpm-using.html#sec-Installing_and_Upgrading">Section A.2.1, “Installing and Upgrading Packages”</a> for more information on installing/updating kernels with <span class="application"><strong>RPM</strong></span>.
+ </div></div></div><h4 id="bh-Updating_All_Packages_and_Their_Dependencies"> Updating All Packages and Their Dependencies </h4><a id="idm261746937328" class="indexterm"></a><div class="para">
To update all packages and their dependencies, simply enter <code class="command">yum update</code> (without any arguments):
- </div><pre class="screen"><code class="command">yum update</code></pre><h4 id="bh-Updating_Security-Related_Packages"> Updating Security-Related Packages </h4><a id="idm225460972112" class="indexterm"></a><a id="idm225460970704" class="indexterm"></a><a id="idm225460969328" class="indexterm"></a><div class="para">
+ </div><pre class="screen"><code class="command">yum update</code></pre><h4 id="bh-Updating_Security-Related_Packages"> Updating Security-Related Packages </h4><a id="idm261758103200" class="indexterm"></a><a id="idm261758101792" class="indexterm"></a><a id="idm261758100416" class="indexterm"></a><div class="para">
Discovering which packages have security updates available and then updating those packages quickly and easily is important. Yum provides the plug-in for this purpose. The <span class="application"><strong>security</strong></span> plug-in extends the <code class="command">yum</code> command with a set of highly-useful security-centric commands, subcommands and options. See <a class="xref" href="sec-Plugin_Descriptions.html">Section 5.4.3, “Plug-in 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">5.1.3. Preserving Configuration File Changes</h3></div></div></div><a id="idm225467857888" 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 Yum uses to perform changes to the system, provides a mechanism for ensuring their integrity. See <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 class="section" id="sec-Preserving_Configuration_File_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.1.3. Preserving Configuration File Changes</h3></div></div></div><a id="idm261741659120" 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 Yum uses to perform changes to the system, provides a mechanism for ensuring their integrity. See <a class="xref" href="s1-rpm-using.html#sec-Installing_and_Upgrading">Section A.2.1, “Installing and Upgrading Packages”</a> for details on how to manage changes to configuration files across package upgrades.
</div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="part-Package_Management.html"><strong>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>5.2. Packages and Package Groups</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch01s03s03.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch01s03s03.html
index 44d2ac7..822e3de 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch01s03s03.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ch01s03s03.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="gui-from_menu.html" title="1.3. Launching applications from the Desktop Menu" /><link rel="prev" href="gui-from_menu-kde.html" title="1.3.2. Using KDE menus" /><link rel="next" href="ch-System_Locale_and_Keyboard_Configuration.html" title="Chapter 2. System Locale and Keyboard Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="gui-from_menu-kd
e.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-System_Locale_and_Keyboard_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" id="idm225461416928"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225461416928">1.3.3. Using menus in LXDE, MATE, and XFCE</h3></div></div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="gui-from_menu.html" title="1.3. Launching applications from the Desktop Menu" /><link rel="prev" href="gui-from_menu-kde.html" title="1.3.2. Using KDE menus" /><link rel="next" href="ch-System_Locale_and_Keyboard_Configuration.html" title="Chapter 2. System Locale and Keyboard Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="gui-from_menu-kd
e.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-System_Locale_and_Keyboard_Configuration.html"><strong>Next</strong></a></li></ul><div class="section" id="idm261747132512"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm261747132512">1.3.3. Using menus in LXDE, MATE, and XFCE</h3></div></div></div><div class="para">
Menus in LXDE, MATE, and XFCE have a varied appearance but a very similar structure. They categorize applications, and the contents of a category are displayed by hovering the cursor over the entry. Applications are launched by clicking on an entry.
</div><div class="figure" id="fig-menu_lxde"><div class="figure-contents"><div class="mediaobject"><img src="images/menu_LXDE.png" alt="The LXDE menu" /><div class="longdesc"><div class="para">
LXDE Menu
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/managing_users.png b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/managing_users.png
new file mode 100644
index 0000000..0e020b3
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/managing_users.png differ
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/printconf-main.png b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/printconf-main.png
index dfd18c4..bce2701 100644
Binary files a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/printconf-main.png and b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/printconf-main.png differ
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-filter-enable.png b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-filter-enable.png
new file mode 100644
index 0000000..e0e4051
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-filter-enable.png differ
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-filter-sample.png b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-filter-sample.png
new file mode 100644
index 0000000..66ce188
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-filter-sample.png differ
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-filters.png b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-filters.png
new file mode 100644
index 0000000..40dd5f8
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-filters.png differ
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-logviewer-add.png b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-logviewer-add.png
new file mode 100644
index 0000000..f2cf04d
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-logviewer-add.png differ
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-logviewer-monitoring.png b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-logviewer-monitoring.png
new file mode 100644
index 0000000..5f66789
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-logviewer-monitoring.png differ
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-logviewer.png b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-logviewer.png
new file mode 100644
index 0000000..365d52c
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/redhat-logviewer.png differ
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/rsyslog_message_flow.png b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/rsyslog_message_flow.png
new file mode 100644
index 0000000..7503f4a
Binary files /dev/null and b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/images/rsyslog_message_flow.png differ
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/index.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/index.html
index 6b423ed..e12a3dd 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/index.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/index.html
@@ -6,11 +6,11 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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="idm225455432880" lang="en-US"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="c
enter"><span class="productname">Fedora</span> <span class="productnumber">21</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="idm225455432880" class="title">System Administrator's 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 21</h2></div><p class="edition">Edition 1.0</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
+ </script><link rel="home" href="index.html" title="System Administrator's 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="idm261746106576" lang="en-US"><div class="titlepage"><div><div class="producttitle" font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="c
enter"><span class="productname">Fedora</span> <span class="productnumber">21</span></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h1 id="idm261746106576" class="title">System Administrator's 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 21</h2></div><p class="edition">Edition 1.0</p><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><h3 class="corpauthor">
<span class="inlinemediaobject"><object data="Common_Content/images/title_logo.svg" type="image/svg+xml"> </object></span>
- </h3></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div xml:lang="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</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:jhradilek at redhat.com">jhradilek at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Douglas</span> <span class="surname">Silas</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:silas at redhat.com">silas at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Martin</span> <span class="surname">Prpič</span></h3><d
iv class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:mprpic at redhat.com">mprpic at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:swadeley at redhat.com">swadeley at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Eliška</span> <span class="surname">Slobodová</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:eslobodo at redhat.com">eslobodo at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname
">Tomáš</span> <span class="surname">Čapek</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:tcapek at redhat.com">tcapek at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Petr</span> <span class="surname">Kovář</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:pkovar at redhat.com">pkovar at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Miroslav</span> <span class="surname">Svoboda</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:msvoboda at redhat.com">msvoboda at 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</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</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</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</span> <span class="orgdiv">Engineering Content Services</span></div></div></div></div><hr /><d
iv font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="idm225448994592" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
- Copyright <span class="trademark"></span>© 2014 Red Hat, Inc. and others.
+ </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</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:jhradilek at redhat.com">jhradilek at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Douglas</span> <span class="surname">Silas</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:silas at redhat.com">silas at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Martin</span> <span class="surname">Prpič</span></h3><d
iv class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:mprpic at redhat.com">mprpic at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Stephen</span> <span class="surname">Wadeley</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:swadeley at redhat.com">swadeley at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Eliška</span> <span class="surname">Slobodová</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:eslobodo at redhat.com">eslobodo at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname
">Tomáš</span> <span class="surname">Čapek</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:tcapek at redhat.com">tcapek at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Petr</span> <span class="surname">Kovář</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:pkovar at redhat.com">pkovar at redhat.com</a></code></div><div class="author"><h3 class="author"><span class="firstname">Miroslav</span> <span class="surname">Svoboda</span></h3><div class="affiliation"><span class="orgname">Red Hat</span> <span class="orgdiv">Engineering Content Services</span></div><code class="email"><a class="email" href="mailto:msvoboda at redhat.com">msvoboda at 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</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</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</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</span> <span class="orgdiv">Engineering Content Services</span></div></div></div></div><hr /><d
iv font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div id="idm261737074768" class="legalnotice"><h1 class="legalnotice">Legal Notice</h1><div class="para">
+ Copyright <span class="trademark"></span>© 2015 Red Hat, Inc. and others.
</div><div class="para">
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at <a href="http://creativecommons.org/licenses/by-sa/3.0/">http://creativecommons.org/licenses/by-sa/3.0/</a>. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
</div><div class="para">
@@ -31,4 +31,4 @@
All other trademarks are the property of their respective owners.
</div></div></div><div font-family="sans-serif,Symbol,ZapfDingbats" font-weight="bold" font-size="12pt" text-align="center"><div class="abstract"><h6>Abstract</h6><div class="para">
The <em class="citetitle">System Administrator's Guide</em> documents relevant information regarding the deployment, configuration, and administration of Fedora 21. It is oriented towards system administrators with a basic understanding of the system.
- </div></div></div></div><hr /></div><div class="toc"><dl class="toc"><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#idm225504134496">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="pr01s04.html">4. We Need Feedback!</a></span></dt><dt><span class="section"><a href="pref-Acknowledgments.html">5. Acknowledgments</a></span></dt></dl></dd><dt><span class="part"><a hr
ef="part-Basic_System_Configuration.html">I. Basic System Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-Opening_GUI_Applications.html">1. Opening Graphical Applications</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Opening_GUI_Applications.html#gui-from_cli">1.1. Opening graphical applications from the command line</a></span></dt><dt><span class="section"><a href="gui-alt_f2.html">1.2. Launching Applications with <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> </a></span></dt><dt><span class="section"><a href="gui-from_menu.html">1.3. Launching applications from the Desktop Menu</a></span></dt><dd><dl><dt><span class="section"><a href="gui-from_menu.html#gui-from_menu-gnome">1.3.1. Using GNOME menus</a></span></dt><dt><span class="section"><a href="gui-from_menu-kde.html">1.3.2. Using KDE menus </a></span></dt><dt><span class="section"><a href="ch01s03s03.html">1.3.3. Using menus i
n LXDE, MATE, and XFCE</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-System_Locale_and_Keyboard_Configuration.html">2. System Locale and Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s1-Setting_the_System_Locale">2.1. Setting the System Locale</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Displaying_the_Current_Status">2.1.1. Displaying the Current Status</a></span></dt><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Listing_Available_Locales">2.1.2. Listing Available Locales</a></span></dt><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Setting_the_Locale">2.1.3. Setting the Locale</a></span></dt></dl></dd><dt><span class="section"><a href="s1-Changing_the_Keyboard_Layout.html">2.2. Changing the Keyboard Layout</a></span></dt
><dd><dl><dt><span class="section"><a href="s1-Changing_the_Keyboard_Layout.html#s2-Displaying_the_Current_Settings">2.2.1. Displaying the Current Settings</a></span></dt><dt><span class="section"><a href="s2-Listing_Available_Keymaps.html">2.2.2. Listing Available Keymaps</a></span></dt><dt><span class="section"><a href="s2-Setting_the_Keymap.html">2.2.3. Setting the Keymap</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Keyboard_Configuration-Resources.html">2.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Configuring_the_Date_and_Time.html">3. Configuring the Date and Time</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl">3.1. Using the timedatectl Command</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Display">3.1.1. Displaying
the Current Date and Time</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Time">3.1.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Date">3.1.3. Changing the Current Date</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone">3.1.4. Changing the Time Zone</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-NTP">3.1.5. Synchronizing the System Clock with a Remote Server</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date.html">3.2. Using the date Command</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date.html#sec
t-Configuring_the_Date_and_Time-date-Display">3.2.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date-Time.html">3.2.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date-Date.html">3.2.3. Changing the Current Date</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-hwclock.html">3.3. Using the hwclock Command</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-hwclock.html#sect2-displaying-time-hwclock">3.3.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="sect3-changing-date-time-hwclock.html">3.3.2. Setting the Date and Time</a></span></dt><dt><span class="section"><a href="sect4-synchronizing-date-time-hwclock.html">3.3.3. Synchronizing the Date and Time</a></span></dt></dl></dd><dt><span class="section"><a h
ref="sect-Date_and_Time-Resources.html">3.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Managing_Users_and_Groups.html">4. Managing Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s1-users-groups-introduction">4.1. Introduction to Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">4.1.1. User Private Groups</a></span></dt><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">4.1.2. Shadow Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-configui.html">4.2. Using the User Manager Tool</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-configui.html#s2-redhat-config-users-list">4.2.1. Viewing Users and Groups</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-tools.html">4.3. U
sing Command Line Tools</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-tools.html#s2-users-tools-users-add">4.3.1. Adding a New User</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-add.html">4.3.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="s2-users-tools-password-aging.html">4.3.3. Enabling Password Aging</a></span></dt><dt><span class="section"><a href="s2-users-tools-users-logout.html">4.3.4. Enabling Automatic Logouts</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-directories.html">4.3.5. Creating Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-groups-additional-resources.html">4.4. Additional Resources</a></span></dt></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">5. Yum</a></span></dt><dd><dl><dt><span class="se
ction"><a href="ch-yum.html#sec-Checking_For_and_Updating_Packages">5.1. Checking For and Updating Packages</a></span></dt><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_Updates">5.1.1. Checking For Updates</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Updating_Packages">5.1.2. Updating Packages</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Preserving_Configuration_File_Changes">5.1.3. Preserving Configuration File Changes</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html">5.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">5.2.1. Searching Packages</a></span></dt><dt><span class="section"><a href="sec-Listing_Packages.html">5.2.2. Listing Packages</a></span></dt><dt><span class="section"><a href="sec-Displaying_Package_Information.html">5.2.3. Displaying Package Inf
ormation</a></span></dt><dt><span class="section"><a href="sec-Installing.html">5.2.4. Installing Packages</a></span></dt><dt><span class="section"><a href="sec-Removing.html">5.2.5. Removing Packages</a></span></dt><dt><span class="section"><a href="sec-Yum-Transaction_History.html">5.2.6. Working with Transaction History</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html">5.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">5.3.1. Setting [main] Options</a></span></dt><dt><span class="section"><a href="sec-Setting_repository_Options.html">5.3.2. Setting [repository] Options</a></span></dt><dt><span class="section"><a href="sec-Using_Yum_Variables.html">5.3.3. Using Yum Variables</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Current_Configuration.html">5.3.4. Viewing the Current Conf
iguration</a></span></dt><dt><span class="section"><a href="sec-Managing_Yum_Repositories.html">5.3.5. Adding, Enabling, and Disabling a Yum Repository</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Yum_Repository.html">5.3.6. Creating a Yum Repository</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Yum_Plugins.html">5.4. Yum Plug-ins</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">5.4.1. Enabling, Configuring, and Disabling Yum Plug-ins</a></span></dt><dt><span class="section"><a href="sec-Installing_More_Yum_Plugins.html">5.4.2. Installing Additional Yum Plug-ins</a></span></dt><dt><span class="section"><a href="sec-Plugin_Descriptions.html">5.4.3. Plug-in Descriptions</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Additional_Resources.html">5.5. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="part-Inf
rastructure_Services.html">III. Infrastructure Services</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-Services_and_Daemons.html">6. Services and Daemons</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s1-services-configuring">6.1. Configuring Services</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">6.1.1. Enabling the Service</a></span></dt><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-disabling">6.1.2. Disabling the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-running.html">6.2. Running Services</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-running.html#s3-services-running-checking">6.2.1. Checking the Service Status</a></span></dt><dt><span class="section"><a href="s3-services-running-running.html">6.2.2. Running the Service</a></span></dt><dt><
span class="section"><a href="s3-services-running-stopping.html">6.2.3. Stopping the Service</a></span></dt><dt><span class="section"><a href="s3-services-running-restarting.html">6.2.4. Restarting the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-additional-resources.html">6.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-additional-resources.html#s2-services-additional-resources-installed">6.3.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-services-additional-resources-books.html">6.3.2. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-OpenSSH.html">7. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s1-ssh-protocol">7.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-why">7.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a href="
ch-OpenSSH.html#s2-ssh-features">7.1.2. Main Features</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-versions">7.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">7.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-configuration.html">7.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-configuration.html#s2-ssh-configuration-configs">7.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-sshd.html">7.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-requiring.html">7.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-keypairs.html">7.2.4. Using Key-based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-clients.h
tml">7.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-clients.html#s2-ssh-clients-ssh">7.3.1. Using the ssh Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-scp.html">7.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-sftp.html">7.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">7.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">7.4.1. X11 Forwarding</a></span></dt><dt><span class="section"><a href="s2-ssh-beyondshell-tcpip.html">7.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="s1-openssh-additional-resources.html">7.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-TigerVNC.html">8. TigerVNC</a></sp
an></dt><dd><dl><dt><span class="section"><a href="ch-TigerVNC.html#s1-vnc-server">8.1. VNC Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-TigerVNC.html#s2-vnc-installation">8.1.1. Installing VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#s3-configuring-vnc-server">8.1.2. Configuring VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#s4-starting-vncserver">8.1.3. Starting VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#terminating-vnc-session">8.1.4. Terminating a VNC session</a></span></dt></dl></dd><dt><span class="section"><a href="s5-vnc-viewer.html">8.2. VNC Viewer</a></span></dt><dd><dl><dt><span class="section"><a href="s5-vnc-viewer.html#installing-vncviewer">8.2.1. Installing VNC Viewer</a></span></dt><dt><span class="section"><a href="s6-connecting-vnc-viewer.html">8.2.2. Connecting to VNC Server</a></span></dt><dt><span class="section"><a href="s1-using_ssh
.html">8.2.3. Connecting to VNC Server using SSH</a></span></dt></dl></dd><dt><span class="section"><a href="s9-additional-sources.html">8.3. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="part-Servers.html">IV. Servers</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-Web_Servers.html">9. Web Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Web_Servers.html#s1-The_Apache_HTTP_Server">9.1. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-changes">9.1.1. Notable Changes</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-version2-migrating">9.1.2. Updating the Configuration</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-running">9.1.3. Running the httpd Service</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-editing">9.1.4. Editing the Configuration Fil
es</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-dso">9.1.5. Working with Modules</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-virtualhosts">9.1.6. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-mod_ssl">9.1.7. Setting Up an SSL Server</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-resources">9.1.8. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Mail_Servers.html">10. Mail Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Mail_Servers.html#s1-email-protocols">10.1. Email Protocols</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Mail_Servers.html#s2-email-protocols-send">10.1.1. Mail Transport Protocols</a></span></dt><dt><span class="section"><a href="ch-Mail_Servers.html#s2-email-protocols-client">10.1.2. Mail Access Protocols</a></span></
dt></dl></dd><dt><span class="section"><a href="s1-email-types.html">10.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-types.html#s2-email-types-mta">10.2.1. Mail Transport Agent</a></span></dt><dt><span class="section"><a href="s2-email-types-mda.html">10.2.2. Mail Delivery Agent</a></span></dt><dt><span class="section"><a href="s2-email-types-mua.html">10.2.3. Mail User Agent</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mta.html">10.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mta.html#s2-email-mta-postfix">10.3.1. Postfix</a></span></dt><dt><span class="section"><a href="s2-email-mta-sendmail.html">10.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="s2-email-mta-fetchmail.html">10.3.3. Fetchmail</a></span></dt><dt><span class="section"><a href="s2-email-switchmail.html">10.3.4. Mail Transport Agent (MTA) Configuration</a></span></dt></
dl></dd><dt><span class="section"><a href="s1-email-mda.html">10.4. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mda.html#s2-email-procmail-configuration">10.4.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="s2-email-procmail-recipes.html">10.4.2. Procmail Recipes</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mua.html">10.5. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mua.html#s2-email-security">10.5.1. Securing Communication</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-additional-resources.html">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-additional-resources.html#s2-email-installed-docs">10.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-email-useful-websites.html">10.6.2. Useful Websites</a></span></dt><dt><span class="section"><a hre
f="s2-email-related-books.html">10.6.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Directory_Servers.html">11. Directory Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Directory_Servers.html#s1-OpenLDAP">11.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-introduction">11.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-installation">11.1.2. Installing the OpenLDAP Suite</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-configuration">11.1.3. Configuring an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-running">11.1.4. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-pam">11.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">11.1.6. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-File_and_Print_Servers.html">12. File and Print Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s1-Samba">12.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="ch-File_and_Print_Servers.html#samba-rgs-overview">12.1.1. Introduction to Samba</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-daemons">12.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">12.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">12.1.4. Configuring a Samba Server</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2
-samba-startstop">12.1.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-servers">12.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">12.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">12.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">12.1.9. Samba Network Browsing</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-cups">12.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">12.1.11. Samba Distribution Programs</a></span></dt><dt><span class="section"><a href="ch-Fil
e_and_Print_Servers.html#s2-samba-resources">12.1.12. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="s1-FTP.html">12.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="s1-FTP.html#s2-ftp-protocol">12.2.1. The File Transfer Protocol</a></span></dt><dt><span class="section"><a href="s2-ftp-servers.html">12.2.2. FTP Servers</a></span></dt><dt><span class="section"><a href="s3-ftp-vsftpd-conf.html">12.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-start.html">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf.html">12.2.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dt><span class="section"><a href="s2-ftp-resources.html">12.2.6. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Printer_Configuration.html
">12.3. Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">12.3.1. Starting the Printer Configuration Tool</a></span></dt><dt><span class="section"><a href="sec-Setting_Printer.html">12.3.2. Starting Printer Setup</a></span></dt><dt><span class="section"><a href="sec-Adding_Other_Printer.html">12.3.3. Adding a Local Printer</a></span></dt><dt><span class="section"><a href="s1-printing-jetdirect-printer.html">12.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="s1-printing-ipp-printer.html">12.3.5. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="sec-printing-LPDLPR-printer.html">12.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="s1-printing-smb-printer.html">12.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="s1-printing-select-model.html">12.3.
8. Selecting the Printer Model and Finishing</a></span></dt><dt><span class="section"><a href="s1-printing-test-page.html">12.3.9. Printing a Test Page</a></span></dt><dt><span class="section"><a href="s1-printing-edit.html">12.3.10. Modifying Existing Printers</a></span></dt><dt><span class="section"><a href="s1-printing-additional-resources.html">12.3.11. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configuring_NTP_Using_the_chrony_Suite.html">13. Configuring NTP Using the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-Introduction_to_the_chrony_Suite">13.1. Introduction to the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-differences_between_ntpd_and_chronyd">13.1.1. Differences Between ntpd and chronyd</a></span></dt><dt><span class="section"><a href="ch-Configuring_NTP_Us
ing_the_chrony_Suite.html#sect-Choosing_between_NTP_daemon">13.1.2. Choosing Between NTP Daemons</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Understanding_chrony_and-its_configuration.html">13.2. Understanding chrony and Its Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Understanding_chrony_and-its_configuration.html#sect-Understanding_chronyd">13.2.1. Understanding chronyd</a></span></dt><dt><span class="section"><a href="sect-Understanding_chronyc.html">13.2.2. Understanding chronyc</a></span></dt><dt><span class="section"><a href="sect-Understanding_the_chrony_configuration_commands.html">13.2.3. Understanding the chrony Configuration Commands</a></span></dt><dt><span class="section"><a href="sect-Security_with_chronyc.html">13.2.4. Security with chronyc</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Using_chrony.html">13.3. Using chrony</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Usi
ng_chrony.html#sect-Installing_chrony">13.3.1. Installing chrony</a></span></dt><dt><span class="section"><a href="sect-Checking_the_Status_of_chronyd.html">13.3.2. Checking the Status of chronyd</a></span></dt><dt><span class="section"><a href="sect-Starting_chronyd.html">13.3.3. Starting chronyd</a></span></dt><dt><span class="section"><a href="sect-Stopping_chronyd.html">13.3.4. Stopping chronyd</a></span></dt><dt><span class="section"><a href="sect-Checking_if_chrony_is_synchronized.html">13.3.5. Checking if chrony is Synchronized</a></span></dt><dt><span class="section"><a href="sect-Manually_Adjusting-the-System_Clock.html">13.3.6. Manually Adjusting the System Clock</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Setting_up_chrony_for_different_environments.html">13.4. Setting Up chrony for Different Environments</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Setting_up_chrony_for_different_environments.html#sect-Setting_up_chrony_for_
a_system_which_is_infrequently_connected">13.4.1. Setting Up chrony for a System Which is Infrequently Connected</a></span></dt><dt><span class="section"><a href="sect-Setting_up_chrony_for_a_system_in_an_isolated_network.html">13.4.2. Setting Up chrony for a System in an Isolated Network</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Using_chronyc.html">13.5. Using chronyc</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Using_chronyc.html#sect-Using_chronyc_chronyc_to_control_chronyd">13.5.1. Using chronyc to Control chronyd</a></span></dt><dt><span class="section"><a href="sect-Using_chronyc_for_remote_administration.html">13.5.2. Using chronyc for Remote Administration</a></span></dt></dl></dd><dt><span class="section"><a href="sect-additional_resources.html">13.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sect-additional_resources.html#s2-chrony-docs-inst">13.6.1. Installed Documentation</a></span></dt
><dt><span class="section"><a href="s2-chrony_Online_Documentation.html">13.6.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configuring_NTP_Using_ntpd.html">14. Configuring NTP Using ntpd</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_NTP_Using_ntpd.html#s1-Introduction_to_NTP">14.1. Introduction to NTP</a></span></dt><dt><span class="section"><a href="s1-NTP_Strata.html">14.2. NTP Strata</a></span></dt><dt><span class="section"><a href="s1-Understanding_NTP.html">14.3. Understanding NTP</a></span></dt><dt><span class="section"><a href="s1-Understanding_the_Drift_File.html">14.4. Understanding the Drift File</a></span></dt><dt><span class="section"><a href="s1-UTC_timezones_and_DST.html">14.5. UTC, Timezones, and DST</a></span></dt><dt><span class="section"><a href="s1-Authentication_Options_for_NTP.html">14.6. Authentication Options for NTP</a></span></dt><dt><span class="section"><a href="s1-Manag
ing_the_Time_on_Virtual_Machines.html">14.7. Managing the Time on Virtual Machines</a></span></dt><dt><span class="section"><a href="s1-Understanding_Leap_Seconds.html">14.8. Understanding Leap Seconds</a></span></dt><dt><span class="section"><a href="s1-Understanding_the_ntpd_Configuration_File.html">14.9. Understanding the ntpd Configuration File</a></span></dt><dt><span class="section"><a href="s1-Understanding_the_ntpd_Sysconfig_File.html">14.10. Understanding the ntpd Sysconfig File</a></span></dt><dt><span class="section"><a href="s1-Disabling_chrony.html">14.11. Disabling chrony</a></span></dt><dt><span class="section"><a href="s1-Checking_if_the_NTP_Daemon_is_Installed.html">14.12. Checking if the NTP Daemon is Installed</a></span></dt><dt><span class="section"><a href="s1-Installing_the_NTP_Daemon_ntpd.html">14.13. Installing the NTP Daemon (ntpd)</a></span></dt><dt><span class="section"><a href="s1-Checking_the_status_of_NTP.html">14.14. Checking the Status of NTP<
/a></span></dt><dt><span class="section"><a href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html">14.15. Configure the Firewall to Allow Incoming NTP Packets</a></span></dt><dd><dl><dt><span class="section"><a href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html#s2-Change_the_firewall_settings">14.15.1. Change the Firewall Settings</a></span></dt><dt><span class="section"><a href="s2-Open_Ports_in_the_firewall_for_ntp_packets.html">14.15.2. Open Ports in the Firewall for NTP Packets</a></span></dt></dl></dd><dt><span class="section"><a href="s1-Configure_ntpdate_Servers.html">14.16. Configure ntpdate Servers</a></span></dt><dt><span class="section"><a href="s1-Configure_NTP.html">14.17. Configure NTP</a></span></dt><dd><dl><dt><span class="section"><a href="s1-Configure_NTP.html#s2-Configure_Access_Control_to_an_NTP_service">14.17.1. Configure Access Control to an NTP Service</a></span></dt><dt><span class="section"><a href="s2_Configure_Rate_Limi
ting_Access_to_an_NTP_Service.html">14.17.2. Configure Rate Limiting Access to an NTP Service</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Peer_Address.html">14.17.3. Adding a Peer Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Server_Address.html">14.17.4. Adding a Server Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Broadcast_or_Mutlticast_Server_Address.html">14.17.5. Adding a Broadcast or Multicast Server Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Manycast_Client_Address.html">14.17.6. Adding a Manycast Client Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Broadcastclient_Address.html">14.17.7. Adding a Broadcast Client Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_manycastserver_Address.html">14.17.8. Adding a Manycast Server Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_multicastclient_Address.html">14.17.9. A
dding a Multicast Client Address</a></span></dt><dt><span class="section"><a href="s2_Configuring_the_burst_option.html">14.17.10. Configuring the Burst Option</a></span></dt><dt><span class="section"><a href="s2_Configuring_the_iburst_Option.html">14.17.11. Configuring the iburst Option</a></span></dt><dt><span class="section"><a href="s2_Configuring_Symmetric_Authentication_Using_a_Key.html">14.17.12. Configuring Symmetric Authentication Using a Key</a></span></dt><dt><span class="section"><a href="s2_Configuring_the_Poll_Interval.html">14.17.13. Configuring the Poll Interval</a></span></dt><dt><span class="section"><a href="s2_Configuring_Server_Preference.html">14.17.14. Configuring Server Preference</a></span></dt><dt><span class="section"><a href="s2_Configuring_the_Time-To-Live_for_NTP_Packets.html">14.17.15. Configuring the Time-to-Live for NTP Packets</a></span></dt><dt><span class="section"><a href="s2_Configuring_The_Version_of_NTP_to_use.html">14.17.16. Configuri
ng the NTP Version to Use</a></span></dt></dl></dd><dt><span class="section"><a href="s1-Configuring_the_Hardware_Clock_update.html">14.18. Configuring the Hardware Clock Update</a></span></dt><dt><span class="section"><a href="s1-Configuring_Clock_Sources.html">14.19. Configuring Clock Sources</a></span></dt><dt><span class="section"><a href="s1-ntpd_additional-resources.html">14.20. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ntpd_additional-resources.html#s2-ntpd-docs-inst">14.20.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-ntpd_useful-websites.html">14.20.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configuring_PTP_Using_ptp4l.html">15. Configuring PTP Using ptp4l</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Introduction_to_PTP">15.1. Introduction to PTP</a></span></dt><dd><dl><dt><span class="section
"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Understanding_PTP">15.1.1. Understanding PTP</a></span></dt><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Advantages_of_PTP">15.1.2. Advantages of PTP</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_PTP.html">15.2. Using PTP</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_PTP.html#sec-Checking_for_Driver_and_Hardware_Support">15.2.1. Checking for Driver and Hardware Support</a></span></dt><dt><span class="section"><a href="sec-Installing_PTP.html">15.2.2. Installing PTP</a></span></dt><dt><span class="section"><a href="sec-Starting_ptp4l.html">15.2.3. Starting ptp4l</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Specifying_a_Configuration_File.html">15.3. Specifying a Configuration File</a></span></dt><dt><span class="section"><a href="sec-Using_the_PTP_Management_Client.html">15.4. Using the PTP Management Client</a></span></dt><dt><span
class="section"><a href="sec-Synchronizing_the_Clocks.html">15.5. Synchronizing the Clocks</a></span></dt><dt><span class="section"><a href="sec-Verifying_Time_Synchronization.html">15.6. Verifying Time Synchronization</a></span></dt><dt><span class="section"><a href="sec-Serving_PTP_Time_with_NTP.html">15.7. Serving PTP Time with NTP</a></span></dt><dt><span class="section"><a href="sec-Serving_NTP_Time_with_PTP.html">15.8. Serving NTP Time with PTP</a></span></dt><dt><span class="section"><a href="sec-Improving_Accuracy.html">15.9. Improving Accuracy</a></span></dt><dt><span class="section"><a href="sec-PTP_additional_resources.html">15.10. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-PTP_additional_resources.html#sec-PTP-docs-inst">15.10.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-PTP_useful-websites.html">15.10.2. Useful Websites</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"
><a href="part-Monitoring_and_Automation.html">V. 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. Viewing System Processes</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-ps">16.1.1. Using the ps Command</a></span></dt><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-top">16.1.2. Using the top Command</a></span></dt><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-system_monitor">16.1.3. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-memory-usage.html">16.2. Viewing Memory Usage</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinf
o-memory-usage.html#s2-sysinfo-memory-usage-free">16.2.1. Using the free Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-memory-usage-system_monitor.html">16.2.2. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-cpu.html">16.3. Viewing CPU Usage</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-cpu.html#s2-sysinfo-cpu-system_monitor">16.3.1. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-filesystems.html">16.4. Viewing Block Devices and File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-filesystems.html#s2-sysinfo-filesystems-lsblk">16.4.1. Using the lsblk Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-blkid.html">16.4.2. Using the blkid Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-partx.html">16.4.3. Using the partx Command</a></sp
an></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-findmnt.html">16.4.4. Using the findmnt Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-df.html">16.4.5. Using the df Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-du.html">16.4.6. Using the du Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-system_monitor.html">16.4.7. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-hardware.html">16.5. Viewing Hardware Information</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-hardware.html#s2-sysinfo-hardware-lspci">16.5.1. Using the lspci Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-hardware-lsusb.html">16.5.2. Using the lsusb Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-hardware-lspcmcia.html">16.5.3. Using the lspcmcia Command</a></span></dt><dt><span
class="section"><a href="s2-sysinfo-hardware-lscpu.html">16.5.4. Using the lscpu Command</a></span></dt></dl></dd><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP.html">16.6. Monitoring Performance with Net-SNMP</a></span></dt><dd><dl><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP.html#sect-System_Monitoring_Tools-Net-SNMP-Installing">16.6.1. Installing Net-SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Running.html">16.6.2. Running the Net-SNMP Daemon</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html">16.6.3. Configuring Net-SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html">16.6.4. Retrieving Performance Data over SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Extending.html">16.6.5. Extending Net-SNMP</a></span></dt></d
l></dd><dt><span class="section"><a href="s1-sysinfo-additional-resources.html">16.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">16.7.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 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></s
pan></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#sect-Cron-Installing">18.1.1. Installing Cron and Anacron</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#sect-Cron-Running">18.1.2. Running the Crond Service</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">18.1.3. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">18.1.4. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="
ch-Automating_System_Tasks.html#s2-autotasks-cron-access">18.1.5. 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.6. Black and 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#sect-At_and_Batch_Installation">18.2.1. Installing At and Batch</a></span></dt><dt><span class="section"><a href="sect-Atd-Running.html">18.2.2. Running the At Service</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-configuring.html">18.2.3. Configuring an At Job</a></span></dt><dt><span class="section"><a href="s2-autotasks-batch-configuring.html">18.2.4. Configuring a Batch Job</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-viewing.html">18.2.5. Viewing Pending Jobs</a></span></dt><dt><span
class="section"><a href="s2-autotasks-commandline-options.html">18.2.6. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-controlling-access.html">18.2.7. Controlling Access to At and Batch</a></span></dt></dl></dd><dt><span class="section"><a href="s1-autotasks-additional-resources.html">18.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-OProfile.html">19. OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OProfile.html#s1-oprofile-overview-tools">19.1. Overview of Tools</a></span></dt><dt><span class="section"><a href="s1-oprofile-configuring.html">19.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-configuring.html#s2-oprofile-kernel">19.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="s2-oprofile-events.html">19.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a hr
ef="s2-oprofile-starting-separate.html">19.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-starting.html">19.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="s1-oprofile-saving-data.html">19.4. Saving Data</a></span></dt><dt><span class="section"><a href="s1-oprofile-analyzing-data.html">19.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">19.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opreport-single.html">19.5.2. Using opreport on a Single Executable</a></span></dt><dt><span class="section"><a href="s2-oprofile-module-output.html">19.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opannotate.html">19.5.4. Using <code class="command">o
pannotate</code> </a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-dev-oprofile.html">19.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="s1-oprofile-example-usage.html">19.7. Example Usage</a></span></dt><dt><span class="section"><a href="s1-oprofile-java-support.html">19.8. OProfile Support for Java</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-java-support.html#s1-oprofile-java-profiling">19.8.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-gui.html">19.9. Graphical Interface</a></span></dt><dt><span class="section"><a href="s1-oprofile-and-systemtap.html">19.10. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="s1-oprofile-additional-resources.html">19.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-additional-resources.html#s1-oprofile-installed-
docs">19.11.1. Installed Docs</a></span></dt><dt><span class="section"><a href="s2-oprofile-useful-websites.html">19.11.2. Useful Websites</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="part-Kernel_Module_and_Driver_Configuration.html">VI. 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-upgrade.html">20.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="sec-Verifying_the_Ini
tial_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 2 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_M
odule.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="s1-kernel-modules-additional-resources.html">21.7. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="ch-RPM.html">A. RPM</a></span></dt><dd><dl><dt><span class="section"><a href="ch-RPM.html#s1-rpm-design">A.1. RPM 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-findin
g">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 Upgrading</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="app-Revision_History.html">B. 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>
\ No newline at end of file
+ </div></div></div></div><hr /></div><div class="toc"><dl class="toc"><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#idm261755936352">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="pr01s04.html">4. We Need Feedback!</a></span></dt><dt><span class="section"><a href="pref-Acknowledgments.html">5. Acknowledgments</a></span></dt></dl></dd><dt><span class="part"><a hr
ef="part-Basic_System_Configuration.html">I. Basic System Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-Opening_GUI_Applications.html">1. Opening Graphical Applications</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Opening_GUI_Applications.html#gui-from_cli">1.1. Opening graphical applications from the command line</a></span></dt><dt><span class="section"><a href="gui-alt_f2.html">1.2. Launching Applications with <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> </a></span></dt><dt><span class="section"><a href="gui-from_menu.html">1.3. Launching applications from the Desktop Menu</a></span></dt><dd><dl><dt><span class="section"><a href="gui-from_menu.html#gui-from_menu-gnome">1.3.1. Using GNOME menus</a></span></dt><dt><span class="section"><a href="gui-from_menu-kde.html">1.3.2. Using KDE menus </a></span></dt><dt><span class="section"><a href="ch01s03s03.html">1.3.3. Using menus i
n LXDE, MATE, and XFCE</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-System_Locale_and_Keyboard_Configuration.html">2. System Locale and Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s1-Setting_the_System_Locale">2.1. Setting the System Locale</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Displaying_the_Current_Status">2.1.1. Displaying the Current Status</a></span></dt><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Listing_Available_Locales">2.1.2. Listing Available Locales</a></span></dt><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Setting_the_Locale">2.1.3. Setting the Locale</a></span></dt></dl></dd><dt><span class="section"><a href="s1-Changing_the_Keyboard_Layout.html">2.2. Changing the Keyboard Layout</a></span></dt
><dd><dl><dt><span class="section"><a href="s1-Changing_the_Keyboard_Layout.html#s2-Displaying_the_Current_Settings">2.2.1. Displaying the Current Settings</a></span></dt><dt><span class="section"><a href="s2-Listing_Available_Keymaps.html">2.2.2. Listing Available Keymaps</a></span></dt><dt><span class="section"><a href="s2-Setting_the_Keymap.html">2.2.3. Setting the Keymap</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Keyboard_Configuration-Resources.html">2.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Configuring_the_Date_and_Time.html">3. Configuring the Date and Time</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl">3.1. Using the timedatectl Command</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Display">3.1.1. Displaying
the Current Date and Time</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Time">3.1.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Date">3.1.3. Changing the Current Date</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone">3.1.4. Changing the Time Zone</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-NTP">3.1.5. Synchronizing the System Clock with a Remote Server</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date.html">3.2. Using the date Command</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date.html#sec
t-Configuring_the_Date_and_Time-date-Display">3.2.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date-Time.html">3.2.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date-Date.html">3.2.3. Changing the Current Date</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-hwclock.html">3.3. Using the hwclock Command</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-hwclock.html#sect2-displaying-time-hwclock">3.3.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="sect3-changing-date-time-hwclock.html">3.3.2. Setting the Date and Time</a></span></dt><dt><span class="section"><a href="sect4-synchronizing-date-time-hwclock.html">3.3.3. Synchronizing the Date and Time</a></span></dt></dl></dd><dt><span class="section"><a h
ref="sect-Date_and_Time-Resources.html">3.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Managing_Users_and_Groups.html">4. Managing Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s1-users-groups-introduction">4.1. Introduction to Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">4.1.1. User Private Groups</a></span></dt><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">4.1.2. Shadow Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-configui.html">4.2. Managing Users in a Graphical Environment</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-configui.html#s2-redhat-config-users-list">4.2.1. Using the Users Settings Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users
-tools.html">4.3. Using Command Line Tools</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-tools.html#s2-users-tools-users-add">4.3.1. Adding a New User</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-add.html">4.3.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="s2-users-tools-password-aging.html">4.3.3. Enabling Password Aging</a></span></dt><dt><span class="section"><a href="s2-users-tools-users-logout.html">4.3.4. Enabling Automatic Logouts</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-directories.html">4.3.5. Creating Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Users_and_Groups-Resources.html">4.4. Additional Resources</a></span></dt></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">5. Yum</a></span></dt><dd><dl><dt><
span class="section"><a href="ch-yum.html#sec-Checking_For_and_Updating_Packages">5.1. Checking For and Updating Packages</a></span></dt><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_Updates">5.1.1. Checking For Updates</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Updating_Packages">5.1.2. Updating Packages</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Preserving_Configuration_File_Changes">5.1.3. Preserving Configuration File Changes</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html">5.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">5.2.1. Searching Packages</a></span></dt><dt><span class="section"><a href="sec-Listing_Packages.html">5.2.2. Listing Packages</a></span></dt><dt><span class="section"><a href="sec-Displaying_Package_Information.html">5.2.3. Displayi
ng Package Information</a></span></dt><dt><span class="section"><a href="sec-Installing.html">5.2.4. Installing Packages</a></span></dt><dt><span class="section"><a href="sec-Removing.html">5.2.5. Removing Packages</a></span></dt><dt><span class="section"><a href="sec-Yum-Transaction_History.html">5.2.6. Working with Transaction History</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html">5.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">5.3.1. Setting [main] Options</a></span></dt><dt><span class="section"><a href="sec-Setting_repository_Options.html">5.3.2. Setting [repository] Options</a></span></dt><dt><span class="section"><a href="sec-Using_Yum_Variables.html">5.3.3. Using Yum Variables</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Current_Configuration.html">5.3.4. Viewing th
e Current Configuration</a></span></dt><dt><span class="section"><a href="sec-Managing_Yum_Repositories.html">5.3.5. Adding, Enabling, and Disabling a Yum Repository</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Yum_Repository.html">5.3.6. Creating a Yum Repository</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Yum_Plugins.html">5.4. Yum Plug-ins</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">5.4.1. Enabling, Configuring, and Disabling Yum Plug-ins</a></span></dt><dt><span class="section"><a href="sec-Installing_More_Yum_Plugins.html">5.4.2. Installing Additional Yum Plug-ins</a></span></dt><dt><span class="section"><a href="sec-Plugin_Descriptions.html">5.4.3. Plug-in Descriptions</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Additional_Resources.html">5.5. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a
href="part-Infrastructure_Services.html">III. Infrastructure Services</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-Services_and_Daemons.html">6. Services and Daemons</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s1-services-configuring">6.1. Configuring Services</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">6.1.1. Enabling the Service</a></span></dt><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-disabling">6.1.2. Disabling the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-running.html">6.2. Running Services</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-running.html#s3-services-running-checking">6.2.1. Checking the Service Status</a></span></dt><dt><span class="section"><a href="s3-services-running-running.html">6.2.2. Running the Service</a></s
pan></dt><dt><span class="section"><a href="s3-services-running-stopping.html">6.2.3. Stopping the Service</a></span></dt><dt><span class="section"><a href="s3-services-running-restarting.html">6.2.4. Restarting the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-additional-resources.html">6.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-additional-resources.html#s2-services-additional-resources-installed">6.3.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-services-additional-resources-books.html">6.3.2. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-OpenSSH.html">7. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s1-ssh-protocol">7.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-why">7.1.1. Why Use SSH?</a></span></dt><dt><span class="sect
ion"><a href="ch-OpenSSH.html#s2-ssh-features">7.1.2. Main Features</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-versions">7.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">7.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-configuration.html">7.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-configuration.html#s2-ssh-configuration-configs">7.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-sshd.html">7.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-requiring.html">7.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-keypairs.html">7.2.4. Using Key-based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="s1
-ssh-clients.html">7.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-clients.html#s2-ssh-clients-ssh">7.3.1. Using the ssh Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-scp.html">7.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-sftp.html">7.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">7.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">7.4.1. X11 Forwarding</a></span></dt><dt><span class="section"><a href="s2-ssh-beyondshell-tcpip.html">7.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="s1-openssh-additional-resources.html">7.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-TigerVNC.html">8. Ti
gerVNC</a></span></dt><dd><dl><dt><span class="section"><a href="ch-TigerVNC.html#s1-vnc-server">8.1. VNC Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-TigerVNC.html#s2-vnc-installation">8.1.1. Installing VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#s3-configuring-vnc-server">8.1.2. Configuring VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#s4-starting-vncserver">8.1.3. Starting VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#terminating-vnc-session">8.1.4. Terminating a VNC Session</a></span></dt></dl></dd><dt><span class="section"><a href="s5-vnc-viewer.html">8.2. VNC Viewer</a></span></dt><dd><dl><dt><span class="section"><a href="s5-vnc-viewer.html#installing-vncviewer">8.2.1. Installing VNC Viewer</a></span></dt><dt><span class="section"><a href="s6-connecting-vnc-viewer.html">8.2.2. Connecting to VNC Server</a></span></dt><dt><span class="section"><a href
="s1-using_ssh.html">8.2.3. Connecting to VNC Server Using SSH</a></span></dt></dl></dd><dt><span class="section"><a href="s9-additional-sources.html">8.3. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="part-Servers.html">IV. Servers</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-Web_Servers.html">9. Web Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Web_Servers.html#s1-The_Apache_HTTP_Server">9.1. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-changes">9.1.1. Notable Changes</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-version2-migrating">9.1.2. Updating the Configuration</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-running">9.1.3. Running the httpd Service</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-editing">9.1.4. Editing the Con
figuration Files</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-dso">9.1.5. Working with Modules</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-virtualhosts">9.1.6. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-mod_ssl">9.1.7. Setting Up an SSL Server</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-resources">9.1.8. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Mail_Servers.html">10. Mail Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Mail_Servers.html#s1-email-protocols">10.1. Email Protocols</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Mail_Servers.html#s2-email-protocols-send">10.1.1. Mail Transport Protocols</a></span></dt><dt><span class="section"><a href="ch-Mail_Servers.html#s2-email-protocols-client">10.1.2. Mail Access Protocol
s</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-types.html">10.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-types.html#s2-email-types-mta">10.2.1. Mail Transport Agent</a></span></dt><dt><span class="section"><a href="s2-email-types-mda.html">10.2.2. Mail Delivery Agent</a></span></dt><dt><span class="section"><a href="s2-email-types-mua.html">10.2.3. Mail User Agent</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mta.html">10.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mta.html#s2-email-mta-postfix">10.3.1. Postfix</a></span></dt><dt><span class="section"><a href="s2-email-mta-sendmail.html">10.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="s2-email-mta-fetchmail.html">10.3.3. Fetchmail</a></span></dt><dt><span class="section"><a href="s2-email-switchmail.html">10.3.4. Mail Transport Agent (MTA) Configuration</a>
</span></dt></dl></dd><dt><span class="section"><a href="s1-email-mda.html">10.4. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mda.html#s2-email-procmail-configuration">10.4.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="s2-email-procmail-recipes.html">10.4.2. Procmail Recipes</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mua.html">10.5. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mua.html#s2-email-security">10.5.1. Securing Communication</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-additional-resources.html">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-additional-resources.html#s2-email-installed-docs">10.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-email-useful-websites.html">10.6.2. Useful Websites</a></span></dt><dt><span class="s
ection"><a href="s2-email-related-books.html">10.6.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Directory_Servers.html">11. Directory Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Directory_Servers.html#s1-OpenLDAP">11.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-introduction">11.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-installation">11.1.2. Installing the OpenLDAP Suite</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-configuration">11.1.3. Configuring an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-selinux-openldap">11.1.4. SELinux Policy for Applications Using LDAP</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-running">11.1.5. Running an OpenLDAP Server</a></
span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-pam">11.1.6. Configuring a System to Authenticate Using OpenLDAP</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-resources">11.1.7. Additional Resources</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s3-ldap-related-books">11.1.8. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-File_and_Print_Servers.html">12. File and Print Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s1-Samba">12.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="ch-File_and_Print_Servers.html#samba-rgs-overview">12.1.1. Introduction to Samba</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-daemons">12.1.2. Samba Daemons and Related Services</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.htm
l#s2-samba-connect-share">12.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">12.1.4. Configuring a Samba Server</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-startstop">12.1.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-servers">12.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">12.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">12.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">12.1.9. Samba Network Browsing</a></span></dt><dt><span class="section"><a href
="ch-File_and_Print_Servers.html#s2-samba-cups">12.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">12.1.11. Samba Distribution Programs</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-resources">12.1.12. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="s1-FTP.html">12.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="s1-FTP.html#s2-ftp-protocol">12.2.1. The File Transfer Protocol</a></span></dt><dt><span class="section"><a href="s2-ftp-servers.html">12.2.2. FTP Servers</a></span></dt><dt><span class="section"><a href="s3-ftp-vsftpd-conf.html">12.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-start.html">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s
2-ftp-vsftpd-conf.html">12.2.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dt><span class="section"><a href="s2-ftp-resources.html">12.2.6. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Printer_Configuration.html">12.3. Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">12.3.1. Starting the Printers Configuration Tool</a></span></dt><dt><span class="section"><a href="sec-Setting_Printer.html">12.3.2. Starting Printer Setup</a></span></dt><dt><span class="section"><a href="sec-Adding_Other_Printer.html">12.3.3. Adding a Local Printer</a></span></dt><dt><span class="section"><a href="s1-printing-jetdirect-printer.html">12.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="s1-printing-ipp-printer.html">12.3.5. Adding an IPP Printer</a></span></dt><dt><span class="section"><a h
ref="sec-printing-LPDLPR-printer.html">12.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="s1-printing-smb-printer.html">12.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="s1-printing-select-model.html">12.3.8. Selecting the Printer Model and Finishing</a></span></dt><dt><span class="section"><a href="s1-printing-test-page.html">12.3.9. Printing a Test Page</a></span></dt><dt><span class="section"><a href="s1-printing-edit.html">12.3.10. Modifying Existing Printers</a></span></dt><dt><span class="section"><a href="s1-printing-additional-resources.html">12.3.11. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configuring_NTP_Using_the_chrony_Suite.html">13. Configuring NTP Using the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-Introduction_to_the_chrony_Suite">13.1. Introduction
to the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-differences_between_ntpd_and_chronyd">13.1.1. Differences Between ntpd and chronyd</a></span></dt><dt><span class="section"><a href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-Choosing_between_NTP_daemon">13.1.2. Choosing Between NTP Daemons</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Understanding_chrony_and-its_configuration.html">13.2. Understanding chrony and Its Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Understanding_chrony_and-its_configuration.html#sect-Understanding_chronyd">13.2.1. Understanding chronyd</a></span></dt><dt><span class="section"><a href="sect-Understanding_chronyc.html">13.2.2. Understanding chronyc</a></span></dt><dt><span class="section"><a href="sect-Understanding_the_chrony_configuration_commands.html">13.2.3. Understanding the chrony Configuration Command
s</a></span></dt><dt><span class="section"><a href="sect-Security_with_chronyc.html">13.2.4. Security with chronyc</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Using_chrony.html">13.3. Using chrony</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Using_chrony.html#sect-Installing_chrony">13.3.1. Installing chrony</a></span></dt><dt><span class="section"><a href="sect-Checking_the_Status_of_chronyd.html">13.3.2. Checking the Status of chronyd</a></span></dt><dt><span class="section"><a href="sect-Starting_chronyd.html">13.3.3. Starting chronyd</a></span></dt><dt><span class="section"><a href="sect-Stopping_chronyd.html">13.3.4. Stopping chronyd</a></span></dt><dt><span class="section"><a href="sect-Checking_if_chrony_is_synchronized.html">13.3.5. Checking if chrony is Synchronized</a></span></dt><dt><span class="section"><a href="sect-Manually_Adjusting-the-System_Clock.html">13.3.6. Manually Adjusting the System Clock</a></span></dt></dl></d
d><dt><span class="section"><a href="sect-Setting_up_chrony_for_different_environments.html">13.4. Setting Up chrony for Different Environments</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Setting_up_chrony_for_different_environments.html#sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">13.4.1. Setting Up chrony for a System Which is Infrequently Connected</a></span></dt><dt><span class="section"><a href="sect-Setting_up_chrony_for_a_system_in_an_isolated_network.html">13.4.2. Setting Up chrony for a System in an Isolated Network</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Using_chronyc.html">13.5. Using chronyc</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Using_chronyc.html#sect-Using_chronyc_chronyc_to_control_chronyd">13.5.1. Using chronyc to Control chronyd</a></span></dt><dt><span class="section"><a href="sect-Using_chronyc_for_remote_administration.html">13.5.2. Using chronyc for Remote Admini
stration</a></span></dt></dl></dd><dt><span class="section"><a href="sect-additional_resources.html">13.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sect-additional_resources.html#s2-chrony-docs-inst">13.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-chrony_Online_Documentation.html">13.6.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configuring_NTP_Using_ntpd.html">14. Configuring NTP Using ntpd</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_NTP_Using_ntpd.html#s1-Introduction_to_NTP">14.1. Introduction to NTP</a></span></dt><dt><span class="section"><a href="s1-NTP_Strata.html">14.2. NTP Strata</a></span></dt><dt><span class="section"><a href="s1-Understanding_NTP.html">14.3. Understanding NTP</a></span></dt><dt><span class="section"><a href="s1-Understanding_the_Drift_File.html">14.4. Understanding the Drift File</a></span></
dt><dt><span class="section"><a href="s1-UTC_timezones_and_DST.html">14.5. UTC, Timezones, and DST</a></span></dt><dt><span class="section"><a href="s1-Authentication_Options_for_NTP.html">14.6. Authentication Options for NTP</a></span></dt><dt><span class="section"><a href="s1-Managing_the_Time_on_Virtual_Machines.html">14.7. Managing the Time on Virtual Machines</a></span></dt><dt><span class="section"><a href="s1-Understanding_Leap_Seconds.html">14.8. Understanding Leap Seconds</a></span></dt><dt><span class="section"><a href="s1-Understanding_the_ntpd_Configuration_File.html">14.9. Understanding the ntpd Configuration File</a></span></dt><dt><span class="section"><a href="s1-Understanding_the_ntpd_Sysconfig_File.html">14.10. Understanding the ntpd Sysconfig File</a></span></dt><dt><span class="section"><a href="s1-Disabling_chrony.html">14.11. Disabling chrony</a></span></dt><dt><span class="section"><a href="s1-Checking_if_the_NTP_Daemon_is_Installed.html">14.12. Checki
ng if the NTP Daemon is Installed</a></span></dt><dt><span class="section"><a href="s1-Installing_the_NTP_Daemon_ntpd.html">14.13. Installing the NTP Daemon (ntpd)</a></span></dt><dt><span class="section"><a href="s1-Checking_the_status_of_NTP.html">14.14. Checking the Status of NTP</a></span></dt><dt><span class="section"><a href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html">14.15. Configure the Firewall to Allow Incoming NTP Packets</a></span></dt><dd><dl><dt><span class="section"><a href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html#s2-Change_the_firewall_settings">14.15.1. Change the Firewall Settings</a></span></dt><dt><span class="section"><a href="s2-Open_Ports_in_the_firewall_for_ntp_packets.html">14.15.2. Open Ports in the Firewall for NTP Packets</a></span></dt></dl></dd><dt><span class="section"><a href="s1-Configure_ntpdate_Servers.html">14.16. Configure ntpdate Servers</a></span></dt><dt><span class="section"><a href="s1-Configur
e_NTP.html">14.17. Configure NTP</a></span></dt><dd><dl><dt><span class="section"><a href="s1-Configure_NTP.html#s2-Configure_Access_Control_to_an_NTP_service">14.17.1. Configure Access Control to an NTP Service</a></span></dt><dt><span class="section"><a href="s2_Configure_Rate_Limiting_Access_to_an_NTP_Service.html">14.17.2. Configure Rate Limiting Access to an NTP Service</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Peer_Address.html">14.17.3. Adding a Peer Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Server_Address.html">14.17.4. Adding a Server Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Broadcast_or_Mutlticast_Server_Address.html">14.17.5. Adding a Broadcast or Multicast Server Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Manycast_Client_Address.html">14.17.6. Adding a Manycast Client Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Broadcastclient_Address.
html">14.17.7. Adding a Broadcast Client Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_manycastserver_Address.html">14.17.8. Adding a Manycast Server Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_multicastclient_Address.html">14.17.9. Adding a Multicast Client Address</a></span></dt><dt><span class="section"><a href="s2_Configuring_the_burst_option.html">14.17.10. Configuring the Burst Option</a></span></dt><dt><span class="section"><a href="s2_Configuring_the_iburst_Option.html">14.17.11. Configuring the iburst Option</a></span></dt><dt><span class="section"><a href="s2_Configuring_Symmetric_Authentication_Using_a_Key.html">14.17.12. Configuring Symmetric Authentication Using a Key</a></span></dt><dt><span class="section"><a href="s2_Configuring_the_Poll_Interval.html">14.17.13. Configuring the Poll Interval</a></span></dt><dt><span class="section"><a href="s2_Configuring_Server_Preference.html">14.17.14. Configuring Server Pr
eference</a></span></dt><dt><span class="section"><a href="s2_Configuring_the_Time-To-Live_for_NTP_Packets.html">14.17.15. Configuring the Time-to-Live for NTP Packets</a></span></dt><dt><span class="section"><a href="s2_Configuring_The_Version_of_NTP_to_use.html">14.17.16. Configuring the NTP Version to Use</a></span></dt></dl></dd><dt><span class="section"><a href="s1-Configuring_the_Hardware_Clock_update.html">14.18. Configuring the Hardware Clock Update</a></span></dt><dt><span class="section"><a href="s1-Configuring_Clock_Sources.html">14.19. Configuring Clock Sources</a></span></dt><dt><span class="section"><a href="s1-ntpd_additional-resources.html">14.20. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ntpd_additional-resources.html#s2-ntpd-docs-inst">14.20.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-ntpd_useful-websites.html">14.20.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span cl
ass="chapter"><a href="ch-Configuring_PTP_Using_ptp4l.html">15. Configuring PTP Using ptp4l</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Introduction_to_PTP">15.1. Introduction to PTP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Understanding_PTP">15.1.1. Understanding PTP</a></span></dt><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Advantages_of_PTP">15.1.2. Advantages of PTP</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_PTP.html">15.2. Using PTP</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_PTP.html#sec-Checking_for_Driver_and_Hardware_Support">15.2.1. Checking for Driver and Hardware Support</a></span></dt><dt><span class="section"><a href="sec-Installing_PTP.html">15.2.2. Installing PTP</a></span></dt><dt><span class="section"><a href="sec-Starting_ptp4l.html">15.2.3. Starting ptp4l</a></span>
</dt></dl></dd><dt><span class="section"><a href="sec-Specifying_a_Configuration_File.html">15.3. Specifying a Configuration File</a></span></dt><dt><span class="section"><a href="sec-Using_the_PTP_Management_Client.html">15.4. Using the PTP Management Client</a></span></dt><dt><span class="section"><a href="sec-Synchronizing_the_Clocks.html">15.5. Synchronizing the Clocks</a></span></dt><dt><span class="section"><a href="sec-Verifying_Time_Synchronization.html">15.6. Verifying Time Synchronization</a></span></dt><dt><span class="section"><a href="sec-Serving_PTP_Time_with_NTP.html">15.7. Serving PTP Time with NTP</a></span></dt><dt><span class="section"><a href="sec-Serving_NTP_Time_with_PTP.html">15.8. Serving NTP Time with PTP</a></span></dt><dt><span class="section"><a href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html">15.9. Synchronize to PTP or NTP Time Using timemaster</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Synchronize_to_PTP_or_NTP
_Time_Using_timemaster.html#sec-Starting_timemaster_as_a_Service">15.9.1. Starting timemaster as a Service</a></span></dt><dt><span class="section"><a href="sec-Understanding_the_timemaster_Configuration_File.html">15.9.2. Understanding the timemaster Configuration File</a></span></dt><dt><span class="section"><a href="sec-Configuring_timemaster_Options.html">15.9.3. Configuring timemaster Options</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Improving_Accuracy.html">15.10. Improving Accuracy</a></span></dt><dt><span class="section"><a href="sec-PTP_additional_resources.html">15.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-PTP_additional_resources.html#sec-PTP-docs-inst">15.11.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-PTP_useful-websites.html">15.11.2. Useful Websites</a></span></dt></dl></dd></dl></dd></dl></dd><dt><span class="part"><a href="part-Monitoring_and_Automation.htm
l">V. 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. Viewing System Processes</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-ps">16.1.1. Using the ps Command</a></span></dt><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-top">16.1.2. Using the top Command</a></span></dt><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-system_monitor">16.1.3. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-memory-usage.html">16.2. Viewing Memory Usage</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-memory-usage.html#s2-sysinfo-memory-usage-
free">16.2.1. Using the free Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-memory-usage-system_monitor.html">16.2.2. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-cpu.html">16.3. Viewing CPU Usage</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-cpu.html#s2-sysinfo-cpu-system_monitor">16.3.1. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-filesystems.html">16.4. Viewing Block Devices and File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-filesystems.html#s2-sysinfo-filesystems-lsblk">16.4.1. Using the lsblk Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-blkid.html">16.4.2. Using the blkid Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-partx.html">16.4.3. Using the partx Command</a></span></dt><dt><span class="section"><a href="s
2-sysinfo-filesystems-findmnt.html">16.4.4. Using the findmnt Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-df.html">16.4.5. Using the df Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-du.html">16.4.6. Using the du Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-system_monitor.html">16.4.7. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-hardware.html">16.5. Viewing Hardware Information</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-hardware.html#s2-sysinfo-hardware-lspci">16.5.1. Using the lspci Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-hardware-lsusb.html">16.5.2. Using the lsusb Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-hardware-lspcmcia.html">16.5.3. Using the lspcmcia Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-hardwar
e-lscpu.html">16.5.4. Using the lscpu Command</a></span></dt></dl></dd><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP.html">16.6. Monitoring Performance with Net-SNMP</a></span></dt><dd><dl><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP.html#sect-System_Monitoring_Tools-Net-SNMP-Installing">16.6.1. Installing Net-SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Running.html">16.6.2. Running the Net-SNMP Daemon</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html">16.6.3. Configuring Net-SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html">16.6.4. Retrieving Performance Data over SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Extending.html">16.6.5. Extending Net-SNMP</a></span></dt></dl></dd><dt><span class="section"><a href="s1
-sysinfo-additional-resources.html">16.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">16.7.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-logfiles-locating">17.1. Locating Log Files</a></span></dt><dt><span class="section"><a href="s1-basic_configuration_of_rsyslog.html">17.2. Basic Configuration of Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="s1-basic_configuration_of_rsyslog.html#s2-Filters">17.2.1. Filters</a></span></dt><dt><span class="section"><a href="s2-Actions.html">17.2.2. Actions</a></span></dt><dt><span class="section"><a href="s2-Templates.html">17.2.3. Templates</a></span></dt><dt><span class="section"><a href="s2-global_d
irectives.html">17.2.4. Global Directives</a></span></dt><dt><span class="section"><a href="s2-log_rotation.html">17.2.5. Log Rotation</a></span></dt><dt><span class="section"><a href="s2-using_the_new_configuration_format.html">17.2.6. Using the New Configuration Format</a></span></dt><dt><span class="section"><a href="s2-Rulesets.html">17.2.7. Rulesets</a></span></dt><dt><span class="section"><a href="s2-compatibility_with_syslogd.html">17.2.8. Compatibility with syslogd</a></span></dt></dl></dd><dt><span class="section"><a href="s1-working_with_queues_in_rsyslog.html">17.3. Working with Queues in Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="s1-working_with_queues_in_rsyslog.html#s2-defining_queues">17.3.1. Defining Queues</a></span></dt><dt><span class="section"><a href="s2-managing_queues.html">17.3.2. Managing Queues</a></span></dt></dl></dd><dt><span class="section"><a href="s1-using_rsyslog_modules.html">17.4. Using Rsyslog Modules</a></span></dt>
<dd><dl><dt><span class="section"><a href="s1-using_rsyslog_modules.html#s2-importing_text_files">17.4.1. Importing Text Files</a></span></dt><dt><span class="section"><a href="s2-exporting_messages_to_a_database.html">17.4.2. Exporting Messages to a Database</a></span></dt><dt><span class="section"><a href="s2-enabling_encrypted_transport.html">17.4.3. Enabling Encrypted Transport</a></span></dt><dt><span class="section"><a href="s2-using_RELP.html">17.4.4. Using RELP</a></span></dt></dl></dd><dt><span class="section"><a href="s1-interaction_of_rsyslog_and_journal.html">17.5. Interaction of Rsyslog and Journal</a></span></dt><dt><span class="section"><a href="s1-structured_logging_with_rsyslog.html">17.6. Structured Logging with Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="s1-structured_logging_with_rsyslog.html#s2-importing_data_from_journal">17.6.1. Importing Data from Journal</a></span></dt><dt><span class="section"><a href="s2-filtering_structured_m
essages.html">17.6.2. Filtering Structured Messages</a></span></dt><dt><span class="section"><a href="s2-parsing_JSON.html">17.6.3. Parsing JSON</a></span></dt><dt><span class="section"><a href="s2-storing_messages_in_the_mongodb.html">17.6.4. Storing Messages in the MongoDB</a></span></dt></dl></dd><dt><span class="section"><a href="s1-debugging_rsyslog.html">17.7. Debugging Rsyslog</a></span></dt><dt><span class="section"><a href="s1-Using_the_Journal.html">17.8. Using the Journal</a></span></dt><dd><dl><dt><span class="section"><a href="s1-Using_the_Journal.html#s2-Viewing_Log_Files">17.8.1. Viewing Log Files</a></span></dt><dt><span class="section"><a href="s2-Access_Control.html">17.8.2. Access Control</a></span></dt><dt><span class="section"><a href="s2-Using_The_Live_View.html">17.8.3. Using The Live View</a></span></dt><dt><span class="section"><a href="s2-Filtering_Messages.html">17.8.4. Filtering Messages</a></span></dt><dt><span class="section"><a href="s2-Enablin
g_Persistent_Storage.html">17.8.5. Enabling Persistent Storage</a></span></dt></dl></dd><dt><span class="section"><a href="s1-managing_log_files_in_a_graphical_environment.html">17.9. Managing Log Files in a Graphical Environment</a></span></dt><dd><dl><dt><span class="section"><a href="s1-managing_log_files_in_a_graphical_environment.html#s2-logfiles-viewing">17.9.1. Viewing Log Files</a></span></dt><dt><span class="section"><a href="s2-logfiles-adding.html">17.9.2. Adding a Log File</a></span></dt><dt><span class="section"><a href="s2-logfiles-examining.html">17.9.3. Monitoring Log Files</a></span></dt></dl></dd><dt><span class="section"><a href="s1-log-files-additional-resources.html">17.10. Additional Resources</a></span></dt></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#sect-Cron-Installing">18.1.1. Installing Cron and Anacron</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#sect-Cron-Running">18.1.2. Running the Crond Service</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">18.1.3. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">18.1.4. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-autotasks-cron-access">18.1.5. 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.6. Black and 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></d
t><dd><dl><dt><span class="section"><a href="s1-autotasks-at-batch.html#sect-At_and_Batch_Installation">18.2.1. Installing At and Batch</a></span></dt><dt><span class="section"><a href="sect-Atd-Running.html">18.2.2. Running the At Service</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-configuring.html">18.2.3. Configuring an At Job</a></span></dt><dt><span class="section"><a href="s2-autotasks-batch-configuring.html">18.2.4. Configuring a Batch Job</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-viewing.html">18.2.5. Viewing Pending Jobs</a></span></dt><dt><span class="section"><a href="s2-autotasks-commandline-options.html">18.2.6. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-controlling-access.html">18.2.7. Controlling Access to At and Batch</a></span></dt></dl></dd><dt><span class="section"><a href="s1-autotasks-additional-resources.html">18.3. Additional Resources</a></
span></dt></dl></dd><dt><span class="chapter"><a href="ch-OProfile.html">19. OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OProfile.html#s1-oprofile-overview-tools">19.1. Overview of Tools</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OProfile.html#s2-operf_vs_opcontrol">19.1.1. operf vs. opcontrol</a></span></dt></dl></dd><dt><span class="section"><a href="s1-using-operf.html">19.2. Using operf</a></span></dt><dd><dl><dt><span class="section"><a href="s1-using-operf.html#s2-operf-kernel">19.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="s2-operf-events.html">19.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="s2-operf-categorization.html">19.2.3. Categorization of Samples</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-configuring.html">19.3. Configuring OProfile Using Legacy Mode</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-c
onfiguring.html#s2-oprofile-kernel">19.3.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="s2-oprofile-events.html">19.3.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="s2-oprofile-starting-separate.html">19.3.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-starting.html">19.4. Starting and Stopping OProfile Using Legacy Mode</a></span></dt><dt><span class="section"><a href="s1-oprofile-saving-data.html">19.5. Saving Data in Legacy Mode</a></span></dt><dt><span class="section"><a href="s1-oprofile-analyzing-data.html">19.6. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">19.6.1. Using <code class="command">opreport</code></a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opreport-single.html">19.6.2. Using opreport on a Single Executable</a></
span></dt><dt><span class="section"><a href="s2-oprofile-module-output.html">19.6.3. Getting More Detailed Output on the Modules</a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opannotate.html">19.6.4. Using <code class="command">opannotate</code></a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-dev-oprofile.html">19.7. Understanding the /dev/oprofile/ directory </a></span></dt><dt><span class="section"><a href="s1-oprofile-example-usage.html">19.8. Example Usage</a></span></dt><dt><span class="section"><a href="s1-oprofile-java-support.html">19.9. OProfile Support for Java</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-java-support.html#s1-oprofile-java-profiling">19.9.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-gui.html">19.10. Graphical Interface</a></span></dt><dt><span class="section"><a href="s1-oprofile-and-systemtap.html">19.11. OProfile and SystemTa
p</a></span></dt><dt><span class="section"><a href="s1-oprofile_additional_resources.html">19.12. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="part-Kernel_Module_and_Driver_Configuration.html">VI. Kernel, Module and Driver Configuration</a></span></dt><dd><dl><dt><span class="chapter"><a href="ch-Working_with_the_GRUB_2_Boot_Loader.html">20. Working with the GRUB 2 Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Working_with_the_GRUB_2_Boot_Loader.html#sec-Configuring_the_GRUB_2_Boot_Loader">20.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="sec-Customizing_GRUB_2_Menu.html">20.2. Customizing GRUB 2 Menu</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Customizing_GRUB_2_Menu.html#sec-Changing_the_Default_Boot_Entry">20.2.1. Changing the Default Boot Entry</a></span></dt><dt><span class="section"><a href="sec-Editing_an_Entry.html">20.2.2. Editing an Entry
</a></span></dt><dt><span class="section"><a href="sec-Adding_a_new_Entry.html">20.2.3. Adding a new Entry</a></span></dt><dt><span class="section"><a href="sec-Using_only_a_Custom_Menu.html">20.2.4. Creating a Custom Menu</a></span></dt></dl></dd><dt><span class="section"><a href="sec-GRUB_2_Password_Protection.html">20.3. GRUB 2 Password Protection</a></span></dt><dd><dl><dt><span class="section"><a href="sec-GRUB_2_Password_Protection.html#sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries">20.3.1. Setting Up Users and Password Protection, Specifying Menu Entries</a></span></dt><dt><span class="section"><a href="sec-Password_Encryption.html">20.3.2. Password Encryption</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Reinstalling_GRUB_2.html">20.4. Reinstalling GRUB 2</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Reinstalling_GRUB_2.html#sec-Using_the_grub2-install_Command">20.4.1. Using the grub2-install Command</a></span>
</dt><dt><span class="section"><a href="sec-Resetting_and_Reinstalling_GRUB_2.html">20.4.2. Resetting and Reinstalling GRUB 2</a></span></dt></dl></dd><dt><span class="section"><a href="sec-GRUB_2_over_Serial_Console.html">20.5. GRUB 2 over Serial Console</a></span></dt><dd><dl><dt><span class="section"><a href="sec-GRUB_2_over_Serial_Console.html#sec-Configuring_GRUB_2">20.5.1. Configuring GRUB 2</a></span></dt><dt><span class="section"><a href="sec-Using_screen_to_Connect_to_the_Serial_Console.html">20.5.2. Using screen to Connect to the Serial Console</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Terminal_Menu_Editing_During_Boot.html">20.6. Terminal Menu Editing During Boot</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Terminal_Menu_Editing_During_Boot.html#sec-Booting_to_Rescue_Mode">20.6.1. Booting to Rescue Mode</a></span></dt><dt><span class="section"><a href="sec-Booting_to_Emergency_Mode.html">20.6.2. Booting to Emergency Mode</a><
/span></dt><dt><span class="section"><a href="sec-Changing_and_Resetting_the_Root_Password.html">20.6.3. Changing and Resetting the Root Password</a></span></dt></dl></dd><dt><span class="section"><a href="sec-UEFI_Secure_Boot.html">20.7. UEFI Secure Boot</a></span></dt><dd><dl><dt><span class="section"><a href="sec-UEFI_Secure_Boot.html#sec-UEFI_Secure_Boot_Support_in_Fedora">20.7.1. UEFI Secure Boot Support in Fedora</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html">20.8. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Manually_Upgrading_the_Kernel.html">21. Manually Upgrading the Kernel</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">21.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="s1-kernel-preparing.html">21.2. Preparing to Upgrade</a></span></dt><dt><span c
lass="section"><a href="s1-kernel-download.html">21.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="s1-kernel-perform-upgrade.html">21.4. Performing the Upgrade</a></span></dt><dt><span class="section"><a href="sec-Verifying_the_Initial_RAM_Disk_Image.html">21.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="s1-kernel-boot-loader.html">21.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">21.6.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-iseries.html">21.6.2. Configuring the OS/400 Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-pseries.html">21.6.3. Configuring the YABOOT Boot Loader</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Working_with_Kernel_Modules.html">22. Working with Ker
nel Modules</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="section"><a href="sec-Displaying_Information_About_a_Module.html">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="sec-Loading_a_Module.html">22.3. Loading a Module</a></span></dt><dt><span class="section"><a href="sec-Unloading_a_Module.html">22.4. Unloading a Module</a></span></dt><dt><span class="section"><a href="sec-Setting_Module_Parameters.html">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="sec-Persistent_Module_Loading.html">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="sect-signing-kernel-modules-for-secure-boot.html">22.7. Signing Kernel Modules for Secure Boot</a></span></dt><dd><dl><dt><span class="section"><a href="sect-signing-kernel-m
odules-for-secure-boot.html#sect-prerequisites">22.7.1. Prerequisites</a></span></dt><dt><span class="section"><a href="sect-kernel-module-authentication.html">22.7.2. Kernel Module Authentication</a></span></dt><dt><span class="section"><a href="sect-generating-a-public-private-x509-key-pair.html">22.7.3. Generating a Public and Private X.509 Key Pair</a></span></dt><dt><span class="section"><a href="sect-enrolling-public-key-on-target-system.html">22.7.4. Enrolling Public Key on Target System</a></span></dt><dt><span class="section"><a href="sect-signing-kernel-module-with-the-private-key.html">22.7.5. Signing Kernel Module with the Private Key</a></span></dt><dt><span class="section"><a href="sect-loading-signed-kernel-module.html">22.7.6. Loading Signed Kernel Module</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kernel-modules-additional-resources.html">22.8. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="appendix"><a href="ch-R
PM.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#sec-Installing_and_Upgrading">A.2.1. Installing and Upgrading Packages</a></span></dt><dt><span class="section"><a href="s2-rpm-uninstalling.html">A.2.2. Uninstalling Packages</a></span></dt><dt><span class="section"><a href="s2-rpm-freshening.html">A.2.3. Freshening Packages</a></span></dt><dt><span class="section"><a href="s2-rpm-querying.html">A.2.4. Querying Packages</a></span></dt><dt><span class="section"><a href="s2-rpm-verifying.html">A.2.5. Verifying Packages</a></span></dt></dl></dd><dt><span class="section"><a href="s1-find-verify-rpm.html">A.3. Finding and Verifying RPM Packages</a></span></dt><dd><dl><dt><span class="section"><a href="s1-find-verify-rpm.html#s2-rpm-finding">A.3.1. Fin
ding RPM Packages</a></span></dt><dt><span class="section"><a href="s1-check-rpm-sig.html">A.3.2. Checking Package Signatures</a></span></dt></dl></dd><dt><span class="section"><a href="s1-rpm-usage-examples.html">A.4. Common Examples of RPM Usage</a></span></dt><dt><span class="section"><a href="s1-rpm-additional-resources.html">A.5. Additional Resources</a></span></dt></dl></dd><dt><span class="appendix"><a href="app-Revision_History.html">B. 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>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ix01.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ix01.html
index 6eb2e36..794c76b 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ix01.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/ix01.html
@@ -6,4 +6,4 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="app-Revision_History.html" title="Appendix B. 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="idm225464361424"><div class="titlepage"><div><div><h1 class="title"
>Index</h1></div></div></div><div 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 Configuration</a></dt><dt> /dev/oprofile/ , <a class="indexterm" href="s1-oprofile-dev-oprofile.html">Understanding /dev/oprofile/ </a></dt><dt>/dev/shm, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the df Command</a></dt><dt>/run, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the df Command</a></dt><dt>/sys/fs/cgroup, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the df Command</a></dt><dt> /var/spool/anacron , <a class="indexterm" href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">Configuring Anacron Jobs</a></dt><dt> /var/spool/cron , <a class="indexterm" href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt></dl></div><div class="indexdiv"><h3></h3><dl><dt> (see OProfile)</dt></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>adding</dt><dd><dl><dt>group, <a class="indexterm" href="s2-users-tools-groups-add.html">Adding a New Group</a>
</dt><dt>user, <a class="indexterm" href="s1-users-tools.html#s2-users-tools-users-add">Adding a New User</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>Apache HTTP Server</dt><dd><dl><dt>additional resources</dt><dd><dl><dt>installable documentation, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-resources">Additional Resources</a></dt><dt>installed documentation, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-
resources">Additional Resources</a></dt><dt>useful websites, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-resources">Additional Resources</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">Verifying 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="i
ndexterm" 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-directiv
es">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 Dire
ctives</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-W
eb_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-httpdconf-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" hr
ef="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="indexterm" href="ch-Web_Servers.html#s3-apache-mpm-common">Common Multi-Processing Module Directives</a></dt><dt>NameVirtualHost, <a class="indexterm" href="ch-Web_Serv
ers.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">Common 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="indexterm" href="ch-Web_Servers.html#s3-apache-mpm-common">Common Multi-Processing Module Directives</a></dt><dt>SuexecUserGroup, <a class="indexterm" href="ch-Web_Ser
vers.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-htt
pdconf-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-Web_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 m
od_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_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 a
n 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="indexte
rm" href="ch-Web_Servers.html#s3-apache-running-stopping">Stopping the Service</a></dt><dt>version 2.4</dt><dd><dl><dt>changes, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-changes">Notable Changes</a></dt><dt>updating from version 2.2, <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>Automated Tasks, <a class="indexterm" href="ch-Automating_System_Tasks.html">Automating System Tasks</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>blkid, <a class="indexterm" href="s2-sysinfo-filesystems-blkid.html">Using the blkid Command</a></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="s2-users-tools-password-aging.html">Enabling Password Aging</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>CPU usage, <a class="indexterm" href="s1-sysinfo-cpu.html">Viewing CPU Usage</a></dt><dt>cron, <a class="indexterm" href="ch-Automating_System_Tasks.html#s1-autotasks-cron-anacron">Cron 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#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt></dl></dd><dt> crontab , <a class="indexterm" href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt><dt>CUPS (see Printer Configuration)</dt></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>df, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the df Co
mmand</a></dt><dt>directory server (see OpenLDAP)</dt><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>drivers (see kernel module)</dt><dt>du, <a class="indexterm" href="s2-sysinfo-filesystems-du.html">Using the du Command</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>ECDSA keys</dt><dd><dl><dt>generating, <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><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 w
ebsites, <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>mail server</dt><dd><dl><dt>Dovecot, <a class="indexterm" href="ch-Mail_Servers.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.htm
l#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 Clients</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 Ag
ent</a></dt></dl></dd></dl></dd><dt>expiration of password, forcing, <a class="indexterm" href="s2-users-tools-password-aging.html">Enabling Password Aging</a></dt></dl></div><div class="indexdiv"><h3>F</h3><dl><dt> Fedora Hat RPM Guide , <a class="indexterm" href="s2-rpm-related-books.html">Related Books</a></dt><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="pr01s04.html">We Need 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-global">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 systems, <a class="indexterm" href="s1-sysinfo-filesystems.html">Viewing
Block Devices and File Systems</a></dt><dt>findmnt, <a class="indexterm" href="s2-sysinfo-filesystems-findmnt.html">Using the findmnt Command</a></dt><dt>findsmb, <a class="indexterm" href="ch-File_and_Print_Servers.html#s3-samba-connect-share-cmdline">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>free, <a class="indexterm" href="s1-sysinfo-memory-usage.html#s2-sysinfo-memory-usage-free">Using the free Command</a></dt><dt>FTP, <a class="indexterm" href="s1-FTP.html">FTP</a></dt><dd><dl><dt>(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 Mode
s</a></dt><dt>definition of, <a class="indexterm" href="s1-FTP.html">FTP</a></dt><dt>introducing, <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></dl></div><div class="indexdiv"><h3>G</h3><dl><dt> gnome-system-log (see Log File Viewer )</dt><dt>gnome-system-monitor, <a class="indexterm" href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="s2-sysinfo-memory-usage-system_monitor.html">Using the System Monitor Tool</a>, <a class="indexterm" href="s1-sysinfo-cpu.html#s2-sysinfo-cpu-system_mo
nitor">Using the System Monitor Tool</a>, <a class="indexterm" href="s2-sysinfo-filesystems-system_monitor.html">Using the System Monitor Tool</a></dt><dt>GnuPG</dt><dd><dl><dt>checking RPM package signatures, <a class="indexterm" href="s1-check-rpm-sig.html">Checking a Package's Signature</a></dt></dl></dd><dt>group configuration</dt><dd><dl><dt>groupadd, <a class="indexterm" href="s2-users-tools-groups-add.html">Adding a New Group</a></dt><dt>viewing list of groups, <a class="indexterm" href="s1-users-configui.html">Using the 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">Additional Resources</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="s2-users-tools-groups-directories.html">Creating Group Directories</a></dt><dt>tools for management of</dt><dd><dl><dt>groupadd, <a class="indexterm" href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">User Private Groups</a>, <a class="indexterm" href="s1-users-tools.html">Using Command Line Tools</a></dt><dt>system-config-users, <a class="indexterm" href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">User Private Groups</a></dt><dt>User Manager, <a class="indexterm" href="s1-users-tools.html">Using Command Line Tools</a></dt></dl></dd><dt>user private, <a class="indexterm" href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">User Private Groups</a></dt></dl></dd><dt>GRUB 2 boot loader</dt><dd><dl><dt>configuration file, <a class="indexterm" href="s
1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">Configuring the GRUB 2 Boot Loader</a></dt><dt>configuring, <a class="indexterm" href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">Configuring the GRUB 2 Boot Loader</a></dt></dl></dd><dt>GUI, <a class="indexterm" href="ch-Opening_GUI_Applications.html">Opening Graphical Applications</a></dt></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>hardware</dt><dd><dl><dt>viewing, <a class="indexterm" href="s1-sysinfo-hardware.html">Viewing Hardware Information</a></dt></dl></dd><dt>HTTP server (see Apache HTTP Server)</dt><dt>httpd (see Apache HTTP Server)</dt></dl></div><div class="indexdiv"><h3>I</h3><dl><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 Ima
ge</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 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>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 class="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="in
dexterm" 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 module</dt><dd><dl><dt>definition, <a class="indexterm" href="ch-Working_with_Kernel_Modules.html">Working with Kernel Modules</a></dt><dt>directories</dt><dd><dl><dt>/etc/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>files</dt><dd><dl><dt>/proc/modules, <a class="indexterm" href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded Modules</a></dt></dl></dd><dt>listing</dt><dd><dl><dt>currently loaded modules, <a class="indexterm" href="ch-Working_with_Kernel_Modules.html#sec-Listing_Current
ly-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>supplying, <a class="indexterm" href="sec-Setting_Module_Parameters.html">Setting Module Parameters</a></dt></dl></dd><dt>unloading, <a class="indexterm" href="sec-Unloading_a_Module.html">Unloading a Module</a></dt><dt>utilities</dt><dd><dl><dt>insmod, <a class="indexterm" href="sec-Loading_a_Module.html">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 Modul
es</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 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-kern
el-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, <a class="indexterm" href="ch-System_Locale_and_Keyboard_Configuration.html">System Locale and Keyboard Configuration</a></dt><dd><dl><dt>layout, <a class="indexterm" href="s1-Changing_the_Keyboard_Layout.html"
>Changing the Keyboard Layout</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>L</h3><dl><dt>LDAP (see OpenLDAP)</dt><dt>localectl (see keyboard configuration)</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>lsblk, <a class="indexterm" href="s1-sysinfo-filesystems.html#s2-sysinfo-filesystems-lsblk">Using the lsblk Command</a></dt
><dt>lscpu, <a class="indexterm" href="s2-sysinfo-hardware-lscpu.html">Using the lscpu Command</a></dt><dt>lsmod, <a class="indexterm" href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded Modules</a></dt><dd><dl><dt>(see also kernel module)</dt></dl></dd><dt>lspci, <a class="indexterm" href="s1-sysinfo-hardware.html#s2-sysinfo-hardware-lspci">Using the lspci Command</a></dt><dt>lspcmcia, <a class="indexterm" href="s2-sysinfo-hardware-lspcmcia.html">Using the lspcmcia Command</a></dt><dt>lsusb, <a class="indexterm" href="s2-sysinfo-hardware-lsusb.html">Using the lsusb Command</a></dt></dl></div><div class="indexdiv"><h3>M</h3><dl><dt>Mail 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">Viewing 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 kernel 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></dl></div><div class="indexdiv"><h3>N</h3><dl><dt> net program, <a class="indexterm" href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution Programs</a></dt><dt> nmblookup program, <a class="indexterm" href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution Programs</a></dt></dl></div><div class="indexdiv"><h3>O</h3><dl><dt> opannotate (see OProfile)</dt><dt> opcontrol (see OProfile)</dt><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" href="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">Cha
nging the Database-Specific Configuration</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><d
t>/etc/openldap/slapd.d/cn=config/olcDatabase={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-schem
a">Extending Schema</a></dt><dt>stopping, <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 SS
H)</dt><dt>additional resources, <a class="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>ECDSA 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>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-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>ECDSA, <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 Pairs</a></dt></dl></dd><dt>using key-based authentication, <a class="indexterm" href="s2-ssh-configuration-keypairs.html">Using 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 Resourc
es</a></dt><dt>SSL (see SSL)</dt><dt>TLS (see TLS)</dt></dl></dd><dt> ophelp , <a class="indexterm" href="s2-oprofile-events.html">Setting Events to Monitor</a></dt><dt> opreport (see OProfile)</dt><dt>OProfile, <a class="indexterm" href="ch-OProfile.html">OProfile</a></dt><dd><dl><dt> /dev/oprofile/ , <a class="indexterm" href="s1-oprofile-dev-oprofile.html">Understanding /dev/oprofile/ </a></dt><dt>additional resources, <a class="indexterm" href="s1-oprofile-additional-resources.html">Additional Resources</a></dt><dt>configuring, <a class="indexterm" href="s1-oprofile-configuring.html">Configuring OProfile</a></dt><dd><dl><dt>separating profiles, <a class="indexterm" href="s2-oprofile-starting-separate.html">Separating Kernel and User-space Profiles</a></dt></dl></dd><dt>events</dt><dd><dl><dt>sampling rate, <a class="indexterm" href="s2-oprofile-events.html#s3-oprofile-events-sampling">Sampling Rate</a></dt><dt>setting, <a class="indexterm" href="s2-oprofile-events.html"
>Setting Events to Monitor</a></dt></dl></dd><dt>Java, <a class="indexterm" href="s1-oprofile-java-support.html">OProfile Support for Java</a></dt><dt>monitoring the kernel, <a class="indexterm" href="s1-oprofile-configuring.html#s2-oprofile-kernel">Specifying the Kernel</a></dt><dt> opannotate , <a class="indexterm" href="s2-oprofile-reading-opannotate.html">Using opannotate </a></dt><dt> opcontrol , <a class="indexterm" href="s1-oprofile-configuring.html">Configuring OProfile</a></dt><dd><dl><dt> --no-vmlinux , <a class="indexterm" href="s1-oprofile-configuring.html#s2-oprofile-kernel">Specifying the Kernel</a></dt><dt> --start , <a class="indexterm" href="s1-oprofile-starting.html">Starting and Stopping OProfile</a></dt><dt> --vmlinux= , <a class="indexterm" href="s1-oprofile-configuring.html#s2-oprofile-kernel">Specifying the Kernel</a></dt></dl></dd><dt> ophelp , <a class="indexterm" href="s2-oprofile-events.html">Setting Events to Monitor</a></dt><dt> opreport , <a cla
ss="indexterm" href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">Using opreport </a>, <a class="indexterm" href="s2-oprofile-module-output.html">Getting more detailed output on the modules</a></dt><dd><dl><dt>on a single executable, <a class="indexterm" href="s2-oprofile-reading-opreport-single.html">Using opreport on a Single Executable</a></dt></dl></dd><dt> oprofiled , <a class="indexterm" href="s1-oprofile-starting.html">Starting and Stopping OProfile</a></dt><dd><dl><dt>log file, <a class="indexterm" href="s1-oprofile-starting.html">Starting and Stopping OProfile</a></dt></dl></dd><dt>overview of tools, <a class="indexterm" href="ch-OProfile.html#s1-oprofile-overview-tools">Overview of Tools</a></dt><dt>reading data, <a class="indexterm" href="s1-oprofile-analyzing-data.html">Analyzing the Data</a></dt><dt>saving data, <a class="indexterm" href="s1-oprofile-saving-data.html">Saving Data</a></dt><dt>starting, <a class="indexterm" href="s1-oprofile-start
ing.html">Starting and Stopping OProfile</a></dt><dt>SystemTap, <a class="indexterm" href="s1-oprofile-and-systemtap.html">OProfile and SystemTap</a></dt><dt>unit mask, <a class="indexterm" href="s2-oprofile-events.html#s3-oprofile-events-unit-masks">Unit Masks</a></dt></dl></dd><dt> oprofiled (see OProfile)</dt><dt> oprof_start , <a class="indexterm" href="s1-oprofile-gui.html">Graphical Interface</a></dt><dt>OS/400 boot loader</dt><dd><dl><dt>configuration file, <a class="indexterm" href="s2-kernel-boot-loader-iseries.html">Configuring the OS/400 Boot Loader</a></dt><dt>configuring, <a class="indexterm" href="s2-kernel-boot-loader-iseries.html">Configuring the OS/400 Boot Loader</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>package</dt><dd><dl><dt>kernel RPM, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html">Manually Upgrading the Kernel</a></dt></dl></dd><dt>packages</dt><dd><dl><dt>dependencies, <a class="indexterm" href="sec-Insta
lling_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</dt><dd><dl><dt>yum info, <a class="indexterm" href="sec-Displaying_Package_Information.html">Displaying Package Information</a></dt></dl></dd><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>Fedora installation media, <a class="indexterm" href="s1-rpm-using.html#s2-rpm-finding">Finding RPM Packages</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>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 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><d
t>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>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">List
ing 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-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>obtaining list of files, <a class="indexterm" href="s1-rpm-impressing.html">Practical and Common Examples of RPM Usage</a></dt><dt>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-Removin
g.html">Removing Packages</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.html">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 for 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>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>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>upgrading RPM, <a class="indexterm" href="sec-Installing_and_Upgrading.html">Installing and Upgrading</a></dt><dt>Yum instead of RPM, <a class="indexterm" href="ch-RPM.html">RPM</a></dt></dl></dd><dt>partx, <a class="indexterm" href="s2-sysinfo-filesystems-partx.html">Using the partx Command</a></dt><dt>password</dt><dd><dl><dt>aging, <a class="indexterm" href="s2-users-tools-password-aging.html">Enabling Password Aging</a></dt><dt>expire, <a class="indexterm" href="s2-users-tools-password-aging.html">Enabling Password Aging</a></dt></dl></dd><dt>passwords</dt><dd><dl><dt>shadow, <a class="indexterm" href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">Shadow Passwords</a></dt></dl></dd><dt> pdbedit program, <a class="indexterm" href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution Programs</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 c
lass="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>Printer Configuration</dt><dd><dl><dt>CUPS, <a class="indexterm" href="sec-Printer_Configuration.html">Printer Configuration</a></dt><dt>IPP Printers, <a class="indexterm" href="s1-printing-ipp-printer.html">Adding an IPP Printer</a></dt><dt>LDP/LPR Printers, <a class="indexterm" href="sec-printing-LPDLPR-printer.html">Adding an LPD/LPR Host or Printer</a></dt><dt>Local Printers, <a class="indexterm" href="sec-Adding_Other_Printer.html">Adding a Local Printer</a></dt><dt>New Printer, <a class="indexterm" href="sec-Setting_Printer.html">Starting Printer Setup</a></dt><dt>Print Jobs, <a class="indexterm" href="s1-printing-edit.html#s1-printing-managing">Managing Print Jobs</a></dt><dt>Samba Printers, <a class="indexterm" href="s1-printing-s
mb-printer.html">Adding a Samba (SMB) printer</a></dt><dt>Settings, <a class="indexterm" href="s1-printing-edit.html#idm225476918928">The Settings Page</a></dt><dt>Sharing Printers, <a class="indexterm" href="s1-printing-edit.html#sec-Sharing_Printers">Sharing Printers</a></dt></dl></dd><dt>printers (see Printer Configuration)</dt><dt>processes, <a class="indexterm" href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">Viewing 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.htm
l#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 lockfiles, <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-reci
pes.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#s2-sysinfo-system-processes-ps">Using the ps Command</a></dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>RAM, <a class="indexterm" href="s1-sysinfo-memory-usage.html">Viewing Memory Usage</a></dt><dt>rcp, <a class="indexterm" href="s2-ssh-clients-scp.html">Using the scp Utility</a></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> rpcclient 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-Inst
alling_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 Goa
ls</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 a
nd 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> 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-db
s">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 Servi
ces</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-samba-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">Introdu
ction 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></dl></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> nmblo
okup , <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>Samba Printers, <a class="indexterm" href="s1-printing-smb-printer.html">Adding a Samba (SMB) printer</a></dt><dt>Security Modes, <a class="indexterm" href="ch-File_and_Print_Servers.html#s2-samba-security-modes">Samba Security Modes</a></dt><dd><dl><dt>Active Directory Security Mode, <a class="indexterm" href="ch-File_and_Pr
int_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-contr
oller">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-samba-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><d
t>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">Samba 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_a
nd_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> security plug-in (see Security)</dt><dt>Security-Related Packages</dt><dd><dl><dt>updating security-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 chang
es, <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-mta-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-s
endmail.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_Daemons.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="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">Shadow Passwords</a></dt></dl></dd><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-F
ile_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 Programs</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#s2-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="s2-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><d
t>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 HTTP Server)</dt><dt>stunnel, <a class="indexterm" href="s1-email-mua.html#s3-email-security-servers">Securing Email Client Communications</a></dt><dt>system analysis</dt><dd><dl><dt>OProfile (see OProfile)</dt></dl></dd><dt>system information</dt><dd><dl><dt>cpu usage, <a class="indexterm" href="s1-sysinfo-cpu.html">Viewing CPU Usage</a></dt><dt>file systems, <a class="indexterm" href="s1-sysinfo-filesystems.html">Viewing Block Devices and File Systems</a></dt><dd><dl><dt>/dev/shm, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the df Command</a></dt><dt>/run, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the d
f Command</a></dt><dt>/sys/fs/cgroup, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the df Command</a></dt></dl></dd><dt>gathering, <a class="indexterm" href="ch-System_Monitoring_Tools.html">System Monitoring Tools</a></dt><dt>hardware, <a class="indexterm" href="s1-sysinfo-hardware.html">Viewing Hardware Information</a></dt><dt>memory usage, <a class="indexterm" href="s1-sysinfo-memory-usage.html">Viewing Memory Usage</a></dt><dt>processes, <a class="indexterm" href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">Viewing System Processes</a></dt><dd><dl><dt>currently running, <a class="indexterm" href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-top">Using the top Command</a></dt></dl></dd></dl></dd><dt>System Monitor, <a class="indexterm" href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="s2-sysinfo-memory-usage-system_monitor.html"
>Using the System Monitor Tool</a>, <a class="indexterm" href="s1-sysinfo-cpu.html#s2-sysinfo-cpu-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="s2-sysinfo-filesystems-system_monitor.html">Using the System Monitor Tool</a></dt><dt>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>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>top, <a class="indexterm" href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-top">Using the top Command</a></dt></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>user configuration</dt><dd><dl><dt>command line configuration</dt><dd><dl><d
t>chage, <a class="indexterm" href="s2-users-tools-password-aging.html">Enabling Password Aging</a></dt><dt>passwd, <a class="indexterm" href="s1-users-tools.html#s2-users-tools-users-add">Adding a New User</a></dt><dt>useradd, <a class="indexterm" href="s1-users-tools.html#s2-users-tools-users-add">Adding a New User</a></dt></dl></dd><dt>password</dt><dd><dl><dt>forcing expiration of, <a class="indexterm" href="s2-users-tools-password-aging.html">Enabling Password Aging</a></dt></dl></dd><dt>viewing list of users, <a class="indexterm" href="s1-users-configui.html">Using the 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-tools-groups-directories.html">Creating 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-tools-users-add
">Adding a New User</a></dt></dl></dd><dt>users (see user 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">Additional Resources</a></dt></dl></dd><dt>introducing, <a class="indexterm" href="ch-Managing_Users_and_Groups.html">Managing Users and Groups</a></dt><dt>tools for management of</dt><dd><dl><dt>User Manager, <a class="indexterm" href="s1-users-tools.html">Using Command Line Tools</a></dt><dt>useradd, <a class="indexterm" href="s1-users-tools.html">Using Command Line 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 host (see Apache HTTP Server)</dt><dt> vsftpd , <a class="indexterm" href="s2-ftp-servers.html">FTP Ser
vers</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 opt
ions, <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-net">Network Opt
ions</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 Passwords</a></d
t></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 plug-ins, <a class="indexterm" href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring, and Disabling Yum Plug-ins</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 plug-ins, <a class="indexterm" href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring, and
Disabling Yum Plug-ins</a></dt><dt>displaying packages</dt><dd><dl><dt>yum info, <a class="indexterm" href="sec-Displaying_Package_Information.html">Displaying Package Information</a></dt></dl></dd><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 plug-ins, <a class="indexterm" href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring, and Disabling Yum Plug-ins</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>plug-ins</dt><dd><dl><dt>fs-snapshot, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plug-in Descriptions</a></dt><dt>presto, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plug-in Descriptions</a></dt><dt>refresh-packagekit, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plug-in Descriptions
</a></dt><dt>rhnplugin, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plug-in Descriptions</a></dt><dt>security, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plug-in Descriptions</a></dt></dl></dd><dt>repository, <a class="indexterm" href="sec-Managing_Yum_Repositories.html">Adding, Enabling, and Disabling a Yum Repository</a>, <a class="indexterm" href="sec-Creating_a_Yum_Repository.html">Creating a Yum Repository</a></dt><dt>searching for 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>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>set
ting [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 plug-ins, <a class="indexterm" href="sec-Yum_Plugins.html">Yum Plug-ins</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 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_Packages">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 B. 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>
\ No newline at end of file
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="app-Revision_History.html" title="Appendix B. 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="idm261718202960"><div class="titlepage"><div><div><h1 class="title"
>Index</h1></div></div></div><div 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 Configuration</a></dt><dt>/dev/oprofile/, <a class="indexterm" href="s1-oprofile-dev-oprofile.html">Understanding the /dev/oprofile/ directory </a></dt><dt>/dev/shm, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the df Command</a></dt><dt>/run, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the df Command</a></dt><dt>/sys/fs/cgroup, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the df Command</a></dt><dt> /var/spool/anacron , <a class="indexterm" href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">Configuring Anacron Jobs</a></dt><dt> /var/spool/cron , <a class="indexterm" href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt></dl></div><div class="indexdiv"><h3></h3><dl><dt> (see OProfile)</dt></dl></div><div class="indexdiv"><h3>A</h3><dl><dt>adding</dt><dd><dl><dt>group, <a class="indexterm" href="s2-users-tools-groups-add.html">Adding a N
ew Group</a></dt><dt>user, <a class="indexterm" href="s1-users-tools.html#s2-users-tools-users-add">Adding a New User</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>Apache HTTP Server</dt><dd><dl><dt>additional resources</dt><dd><dl><dt>installable documentation, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-resources">Additional Resources</a></dt><dt>installed documentation, <a class="indexterm" href="ch-Web_Servers.htm
l#s2-apache-resources">Additional Resources</a></dt><dt>useful websites, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-resources">Additional Resources</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">Verifying 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">C
ommon 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-httpdc
onf-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 htt
pd.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-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>IndexIgnore, <a class="indexterm" href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Commo
n 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="i
ndexterm" 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="indexterm" 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">Common httpd.conf Directives</a></dt><dt>ScriptAlias, <a class="indexterm" href="ch-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf Dir
ectives</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="indexterm" 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#s
3-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-Web_Servers.html#s3-apache-httpdconf-directives">Common httpd.conf Directives</a></dt><dt>/var/www/cgi-bin/, <a class="indexterm" href="ch-Web_Servers.ht
ml#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">En
abling 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_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-keyp
air">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 cl
ass="indexterm" href="ch-Web_Servers.html#s3-apache-running-stopping">Stopping the Service</a></dt><dt>version 2.4</dt><dd><dl><dt>changes, <a class="indexterm" href="ch-Web_Servers.html#s2-apache-changes">Notable Changes</a></dt><dt>updating from version 2.2, <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>Automated Tasks, <a class="indexterm" href="ch-Automating_System_Tasks.html">Automating System Tasks</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>blkid, <a class="indexterm" href="s2-sysinfo-filesystems-blkid.html">Using the blkid Command</a></dt><dt>boot loader</dt><dd><dl><dt>GRUB 2 boot loader, <a class="indexterm" href="ch-Working_with_the_GRUB_2_Boot_Loader.html">Working with the GRUB 2 Boot Loader</a></dt><dt>verifying, <a class="indexterm" href="s1-kernel-boot-loader.html">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="s2-users-tools-password-aging.
html">Enabling Password Aging</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>CPU usage, <a class="indexterm" href="s1-sysinfo-cpu.html">Viewing CPU Usage</a></dt><dt>cron, <a class="indexterm" href="ch-Automating_System_Tasks.html#s1-autotasks-cron-anacron">Cron 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#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt></dl></dd><dt> crontab , <a class="indexterm" href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">Configuring Cron Jobs</a></dt><dt>CUPS (see Prin
ter Configuration)</dt></dl></div><div class="indexdiv"><h3>D</h3><dl><dt>df, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the df Command</a></dt><dt>directory server (see OpenLDAP)</dt><dt>documentation</dt><dd><dl><dt>finding installed, <a class="indexterm" href="s1-rpm-usage-examples.html">Common Examples of RPM Usage</a></dt></dl></dd><dt>drivers (see kernel module)</dt><dt>du, <a class="indexterm" href="s2-sysinfo-filesystems-du.html">Using the du Command</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt>ECDSA keys</dt><dd><dl><dt>generating, <a class="indexterm" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-generating">Generating Key Pairs</a></dt></dl></dd><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>mail server</dt><dd><dl><dt>Dovecot, <a class="indexterm" href="ch-Mail_Servers.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 Clients</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-typ
es.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>expiration of password, forcing, <a class="indexterm" href="s2-users-tools-password-aging.html">Enabling Password Aging</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-find-verify-rpm.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="pr01s04.html">We Need 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-comma
nds">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-global">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 systems, <a class="indexterm
" href="s1-sysinfo-filesystems.html">Viewing Block Devices and File Systems</a></dt><dt>findmnt, <a class="indexterm" href="s2-sysinfo-filesystems-findmnt.html">Using the findmnt Command</a></dt><dt>findsmb, <a class="indexterm" href="ch-File_and_Print_Servers.html#s3-samba-connect-share-cmdline">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>free, <a class="indexterm" href="s1-sysinfo-memory-usage.html#s2-sysinfo-memory-usage-free">Using the free Command</a></dt><dt>FTP, <a class="indexterm" href="s1-FTP.html">FTP</a></dt><dd><dl><dt>(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-proto
col-multiport">Multiple Ports, Multiple Modes</a></dt><dt>definition of, <a class="indexterm" href="s1-FTP.html">FTP</a></dt><dt>introducing, <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></dl></div><div class="indexdiv"><h3>G</h3><dl><dt>gnome-system-log (see System Log)</dt><dt>gnome-system-monitor, <a class="indexterm" href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="s2-sysinfo-memory-usage-system_monitor.html">Using the System Monitor Tool</a>, <a class="indexterm" href="s1-sysinf
o-cpu.html#s2-sysinfo-cpu-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="s2-sysinfo-filesystems-system_monitor.html">Using the System Monitor Tool</a></dt><dt>GnuPG</dt><dd><dl><dt>checking RPM package signatures, <a class="indexterm" href="s1-check-rpm-sig.html">Checking Package Signatures</a></dt></dl></dd><dt>group configuration</dt><dd><dl><dt>groupadd, <a class="indexterm" href="s2-users-tools-groups-add.html">Adding a New Group</a></dt><dt>viewing list of groups, <a class="indexterm" href="s1-users-configui.html">Managing Users in a Graphical Environment</a></dt></dl></dd><dt>groups (see group configuration)</dt><dd><dl><dt>additional resources, <a class="indexterm" href="sect-Users_and_Groups-Resources.html">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="sect-Users_and_Groups-Resources.html">Additional Resources</a></dt></dl></dd><dt>GID, <a class="indexterm" href="ch-Managing_Users_and_Group
s.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="s2-users-tools-groups-directories.html">Creating Group Directories</a></dt><dt>tools for management of</dt><dd><dl><dt>groupadd, <a class="indexterm" href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">User Private Groups</a>, <a class="indexterm" href="s1-users-tools.html">Using Command Line Tools</a></dt></dl></dd><dt>user private, <a class="indexterm" href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">User Private Groups</a></dt></dl></dd><dt>GRUB 2</dt><dd><dl><dt>configuring GRUB 2, <a class="indexterm" href="ch-Working_with_the_GRUB_2_Boot_Loader.html">Working with the GRUB 2 Boot Loader</a></dt><dt>customizing GRUB 2, <a class="indexterm" href="ch-Working_with_the_GRUB_2_Boot_Loader.html">Working with the GRUB 2 Boot Loader</
a></dt><dt>reinstalling GRUB 2, <a class="indexterm" href="ch-Working_with_the_GRUB_2_Boot_Loader.html">Working with the GRUB 2 Boot Loader</a></dt></dl></dd><dt>GRUB 2 boot loader</dt><dd><dl><dt>configuration file, <a class="indexterm" href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">Configuring the GRUB 2 Boot Loader</a></dt><dt>configuring, <a class="indexterm" href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">Configuring the GRUB 2 Boot Loader</a></dt></dl></dd><dt>GUI, <a class="indexterm" href="ch-Opening_GUI_Applications.html">Opening Graphical Applications</a></dt></dl></div><div class="indexdiv"><h3>H</h3><dl><dt>hardware</dt><dd><dl><dt>viewing, <a class="indexterm" href="s1-sysinfo-hardware.html">Viewing Hardware Information</a></dt></dl></dd><dt>HTTP server (see Apache HTTP Server)</dt><dt>httpd (see Apache HTTP Server)</dt></dl></div><div class="indexdiv"><h3>I</h3><dl><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-find-verify-rpm.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 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>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 class="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 module</dt><dd><dl><dt>definition, <a class="indexterm" href="ch-Working_with_Kernel_Modules.html">Working with Kernel Modules</a></dt><dt>directories</dt><dd><dl><dt>/etc/modules-load.d/, <a class="indexterm" href="sec-Persistent_Module_Loading.html">Persistent Module Loading</a></dt><dt> /lib/modules/kernel_version/kernel/drivers/ , <a class="indexterm" href="sec-Loading_a_Module.html">Loading a Module</a></dt></dl></dd><dt>files</dt><dd><dl><dt>/proc/modules, <a class="indexterm" href="ch-Working_wi
th_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded Modules</a></dt></dl></dd><dt>listing</dt><dd><dl><dt>currently loaded modules, <a class="indexterm" href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded Modules</a></dt><dt>module information, <a class="indexterm" href="sec-Displaying_Information_About_a_Module.html">Displaying Information About a Module</a></dt></dl></dd><dt>loading</dt><dd><dl><dt>at the boot time, <a class="indexterm" href="sec-Persistent_Module_Loading.html">Persistent Module Loading</a></dt><dt>for the current session, <a class="indexterm" href="sec-Loading_a_Module.html">Loading a Module</a></dt></dl></dd><dt>module parameters</dt><dd><dl><dt>supplying, <a class="indexterm" href="sec-Setting_Module_Parameters.html">Setting Module Parameters</a></dt></dl></dd><dt>unloading, <a class="indexterm" href="sec-Unloading_a_Module.html">Unloading a Module</a></dt><dt>utiliti
es</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 Packages</a></dt></dl></dd><dt>kernel-devel</dt><dd><dl><dt>kernel headers and makefiles, <a clas
s="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, <a class="indexterm" href="ch-System_Locale_and_Keyboard_Configuration.html">System Locale and Keyboard Configuration</a></dt><dd><dl><dt>layout,
<a class="indexterm" href="s1-Changing_the_Keyboard_Layout.html">Changing the Keyboard Layout</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>L</h3><dl><dt>LDAP (see OpenLDAP)</dt><dt>localectl (see keyboard configuration)</dt><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 System Log)</dt><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="ch-Viewing_and_Managing_Log_Files.html#s1-logfiles-locating">Locating Log Files</a></dt><dt>monitoring, <a class="indexterm" href="s2-logfiles-examining.html">Monitoring Log Files</a></dt><dt>rotating, <a class="indexterm" href="ch-Viewing_and_Managing_Log_Files.html#s1-logfiles-locating">Locating Log Files</a></dt><dt>rsyslogd daemon, <a class="indexterm" href="ch-Viewing_and_Managing_Log_Files.html">Viewing and Managing Log F
iles</a></dt><dt>viewing, <a class="indexterm" href="s1-managing_log_files_in_a_graphical_environment.html#s2-logfiles-viewing">Viewing Log Files</a></dt></dl></dd><dt>logrotate, <a class="indexterm" href="ch-Viewing_and_Managing_Log_Files.html#s1-logfiles-locating">Locating Log Files</a></dt><dt>lsblk, <a class="indexterm" href="s1-sysinfo-filesystems.html#s2-sysinfo-filesystems-lsblk">Using the lsblk Command</a></dt><dt>lscpu, <a class="indexterm" href="s2-sysinfo-hardware-lscpu.html">Using the lscpu Command</a></dt><dt>lsmod, <a class="indexterm" href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">Listing Currently-Loaded Modules</a></dt><dd><dl><dt>(see also kernel module)</dt></dl></dd><dt>lspci, <a class="indexterm" href="s1-sysinfo-hardware.html#s2-sysinfo-hardware-lspci">Using the lspci Command</a></dt><dt>lspcmcia, <a class="indexterm" href="s2-sysinfo-hardware-lspcmcia.html">Using the lspcmcia Command</a></dt><dt>lsusb, <a class="indexte
rm" href="s2-sysinfo-hardware-lsusb.html">Using the lsusb Command</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">Viewing 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 kernel 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></dl></div><div class="indexdiv"><h3>N</h3><dl><dt> net program, <a class="indexterm" href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution Programs</a></dt><dt> nmblookup program, <a class="indexterm" href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution Programs</a></dt></dl></div><div class="indexdiv"><h3>O</h3><dl><dt>opannotate (see OProfile)</dt><
dt>opcontrol (see OProfile)</dt><dt>OpenLDAP</dt><dd><dl><dt>backends, <a class="indexterm" href="ch-Directory_Servers.html#s3-loading_modules_or_backends">Loading Modules and Backends</a></dt><dt>checking status, <a class="indexterm" href="ch-Directory_Servers.html#s3-ldap-running-status">Verifying 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><dt>TLS, <a class="indexterm" href="ch-Directory_Servers.html#s3-esta
blishing_a_secure_connection">Establishing a Secure Connection</a>, <a class="indexterm" href="ch-Directory_Servers.html#s3-setting_up_replication">Setting Up Replication</a>, <a class="indexterm" href="ch-Directory_Servers.html#s3-loading_modules_or_backends">Loading Modules and Backends</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" href="ch-Directory_Servers.htm
l#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 Configuration</a></dt><dt>olcWriteTimeou
t, <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>, <a class="indexterm" href="ch-Directory_Servers.html#s3-setting_up_replication">Setting Up Replication</a>, <a class="indexterm" href="ch-Directory_Servers.html#s3-loading_modules_or_backends">Loading Modules and Backends</a></dt><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>, <a class="ind
exterm" href="ch-Directory_Servers.html#s3-establishing_a_secure_connection">Establishing a Secure Connection</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>, <a class="indexterm" href="ch-Directory_Servers.html#s3-establishing_a_secure_connection">Establishing a Secure Connection</a></dt><dt>/etc/openldap/slapd.d/cn=config/olcDatabase={1}bdb.ldif, <a class="indexterm" href="ch-Directory_Servers.html#s3-ldap-configuration-database">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>modules, <a class="indexterm" href="ch-Directory_
Servers.html#s3-loading_modules_or_backends">Loading Modules and Backends</a></dt><dt>packages, <a class="indexterm" href="ch-Directory_Servers.html#s2-ldap-installation">Installing the OpenLDAP Suite</a></dt><dt>replication, <a class="indexterm" href="ch-Directory_Servers.html#s3-setting_up_replication">Setting Up Replication</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>security, <a class="indexterm" href="ch-Directory_Servers.html#s3-establishing_a_secure_connection">Establishing a Secure Connection</a></dt><dt>stopping, <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 class="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>ECDSA 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>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-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>ECDSA, <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 Pairs</a></dt></dl></dd><dt>using key-based authentication, <a class="indexterm" href="s2-ssh-configuration-keypairs.html">Using 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>ophelp, <a class="indexterm" href="s2-oprofile-events.html">Setting Events to Monitor</a></dt><dt
>opreport (see OProfile)</dt><dt>OProfile, <a class="indexterm" href="ch-OProfile.html">OProfile</a></dt><dd><dl><dt>/dev/oprofile/, <a class="indexterm" href="s1-oprofile-dev-oprofile.html">Understanding the /dev/oprofile/ directory </a></dt><dt>additional resources, <a class="indexterm" href="s1-oprofile_additional_resources.html">Additional Resources</a></dt><dt>configuring, <a class="indexterm" href="s1-oprofile-configuring.html">Configuring OProfile Using Legacy Mode</a></dt><dd><dl><dt>separating profiles, <a class="indexterm" href="s2-oprofile-starting-separate.html">Separating Kernel and User-space Profiles</a></dt></dl></dd><dt>events</dt><dd><dl><dt>sampling rate, <a class="indexterm" href="s2-oprofile-events.html#s3-oprofile-events-sampling">Sampling Rate</a></dt><dt>setting, <a class="indexterm" href="s2-oprofile-events.html">Setting Events to Monitor</a></dt></dl></dd><dt>Java, <a class="indexterm" href="s1-oprofile-java-support.html">OProfile Support for Java</
a></dt><dt>monitoring the kernel, <a class="indexterm" href="s1-oprofile-configuring.html#s2-oprofile-kernel">Specifying the Kernel</a></dt><dt> opannotate , <a class="indexterm" href="s2-oprofile-reading-opannotate.html">Using opannotate</a></dt><dt>opcontrol, <a class="indexterm" href="s1-oprofile-configuring.html">Configuring OProfile Using Legacy Mode</a></dt><dd><dl><dt> --no-vmlinux , <a class="indexterm" href="s1-oprofile-configuring.html#s2-oprofile-kernel">Specifying the Kernel</a></dt><dt> --start , <a class="indexterm" href="s1-oprofile-starting.html">Starting and Stopping OProfile Using Legacy Mode</a></dt><dt>--vmlinux=, <a class="indexterm" href="s1-oprofile-configuring.html#s2-oprofile-kernel">Specifying the Kernel</a></dt></dl></dd><dt> ophelp , <a class="indexterm" href="s2-oprofile-events.html">Setting Events to Monitor</a></dt><dt> opreport , <a class="indexterm" href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">Using opreport</a>, <a cla
ss="indexterm" href="s2-oprofile-module-output.html">Getting More Detailed Output on the Modules</a></dt><dd><dl><dt>on a single executable, <a class="indexterm" href="s2-oprofile-reading-opreport-single.html">Using opreport on a Single Executable</a></dt></dl></dd><dt> oprofiled , <a class="indexterm" href="s1-oprofile-starting.html">Starting and Stopping OProfile Using Legacy Mode</a></dt><dd><dl><dt>log file, <a class="indexterm" href="s1-oprofile-starting.html">Starting and Stopping OProfile Using Legacy Mode</a></dt></dl></dd><dt>overview of tools, <a class="indexterm" href="ch-OProfile.html#s1-oprofile-overview-tools">Overview of Tools</a></dt><dt>reading data, <a class="indexterm" href="s1-oprofile-analyzing-data.html">Analyzing the Data</a></dt><dt>saving data, <a class="indexterm" href="s1-oprofile-saving-data.html">Saving Data in Legacy Mode</a></dt><dt>starting, <a class="indexterm" href="s1-oprofile-starting.html">Starting and Stopping OProfile Using Legacy Mode<
/a></dt><dt>SystemTap, <a class="indexterm" href="s1-oprofile-and-systemtap.html">OProfile and SystemTap</a></dt><dt>unit mask, <a class="indexterm" href="s2-oprofile-events.html#s3-oprofile-events-unit-masks">Unit Masks</a></dt></dl></dd><dt>oprofiled (see OProfile)</dt><dt>oprof_start, <a class="indexterm" href="s1-oprofile-gui.html">Graphical Interface</a></dt><dt>OS/400 boot loader</dt><dd><dl><dt>configuration file, <a class="indexterm" href="s2-kernel-boot-loader-iseries.html">Configuring the OS/400 Boot Loader</a></dt><dt>configuring, <a class="indexterm" href="s2-kernel-boot-loader-iseries.html">Configuring the OS/400 Boot Loader</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>P</h3><dl><dt>package</dt><dd><dl><dt>kernel RPM, <a class="indexterm" href="ch-Manually_Upgrading_the_Kernel.html">Manually Upgrading the Kernel</a></dt></dl></dd><dt>packages</dt><dd><dl><dt>dependencies, <a class="indexterm" href="s1-rpm-using.html#s3-rpm-unresolved-dependency">Satisf
ying Unresolved Dependencies</a></dt><dt>determining file ownership with, <a class="indexterm" href="s1-rpm-usage-examples.html">Common Examples of RPM Usage</a></dt><dt>displaying packages</dt><dd><dl><dt>yum info, <a class="indexterm" href="sec-Displaying_Package_Information.html">Displaying Package Information</a></dt></dl></dd><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>Fedora installation media, <a class="indexterm" href="s1-find-verify-rpm.html#s2-rpm-finding">Finding RPM Packages</a></dt><dt>finding deleted files from, <a class="indexterm" href="s1-rpm-usage-examples.html">Common Examples of RPM Usage</a></dt><dt>finding Fedora RPM packages, <a class="indexterm" href="s1-find-verify-rpm.html#s2-rpm-finding">Finding RPM Packages</a></dt><dt>initial RPM repositories, <a class="indexterm" href="s1-find-verify-rpm.html#s2-rpm-finding">Fin
ding RPM Packages</a></dt><dt>installing a package group with Yum, <a class="indexterm" href="sec-Installing.html">Installing Packages</a></dt><dt>installing RPM, <a class="indexterm" href="s1-rpm-using.html#sec-Installing_and_Upgrading">Installing and Upgrading Packages</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-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>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-rpm-usage-exampl
es.html">Common Examples of RPM Usage</a></dt><dt>obtaining list of files, <a class="indexterm" href="s1-rpm-usage-examples.html">Common Examples of RPM Usage</a></dt><dt>packages and package groups, <a class="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-usage-examples.html">Common Examples of RPM Usage</a></dt><dt>removing, <a class="indexterm" href="s2-rpm-uninstalling.html">Uninstalling Packages</a></dt><dt>removing package groups with Yum, <a class="indexterm" href="sec-Removing.html">Removing Packages</a></dt><dt>RPM, <a class="indexterm" href="ch-RPM.html">RPM</a></dt><dd><dl><dt>already installed, <a class="indexterm" href="s1-rpm-using.html#s3-rpm-errors">Replacing Already-Installed Packages</a
></dt><dt>configuration file changes, <a class="indexterm" href="s1-rpm-using.html#sec-Configuration_File_Changes">Preserving Changes in Configuration Files</a></dt><dt>conflict, <a class="indexterm" href="s1-rpm-using.html#s3-rpm-conflicting-files">Resolving File Conflicts</a></dt><dt>failed dependencies, <a class="indexterm" href="s1-rpm-using.html#s3-rpm-unresolved-dependency">Satisfying Unresolved Dependencies</a></dt><dt>freshening, <a class="indexterm" href="s2-rpm-freshening.html">Freshening Packages</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.html">Querying Packages</a></dt><dt>removing, <a class="indexterm" href="s2-rpm-uninstalling.html">Uninstalling Packages</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-usage-examples.html">Common Examples of RPM Usage</a>
</dt><dt>uninstalling, <a class="indexterm" href="s2-rpm-uninstalling.html">Uninstalling Packages</a></dt><dt>verifying, <a class="indexterm" href="s2-rpm-verifying.html">Verifying Packages</a></dt></dl></dd><dt>searching for 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>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>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>upgrading RPM, <a class="indexterm" href="s1-rpm-using.html#sec-Installing_and_Upgrading">Installing and Upgrading Packages</a></dt><dt>Yum instead of RPM, <a class="indexterm"
href="ch-RPM.html">RPM</a></dt></dl></dd><dt>partx, <a class="indexterm" href="s2-sysinfo-filesystems-partx.html">Using the partx Command</a></dt><dt>password</dt><dd><dl><dt>aging, <a class="indexterm" href="s2-users-tools-password-aging.html">Enabling Password Aging</a></dt><dt>expire, <a class="indexterm" href="s2-users-tools-password-aging.html">Enabling Password Aging</a></dt></dl></dd><dt>passwords</dt><dd><dl><dt>shadow, <a class="indexterm" href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">Shadow Passwords</a></dt></dl></dd><dt> pdbedit program, <a class="indexterm" href="ch-File_and_Print_Servers.html#s2-samba-programs">Samba Distribution Programs</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" h
ref="s2-email-switchmail.html">Mail Transport Agent (MTA) Configuration</a></dt><dt>Printer Configuration</dt><dd><dl><dt>CUPS, <a class="indexterm" href="sec-Printer_Configuration.html">Printer Configuration</a></dt><dt>IPP Printers, <a class="indexterm" href="s1-printing-ipp-printer.html">Adding an IPP Printer</a></dt><dt>LDP/LPR Printers, <a class="indexterm" href="sec-printing-LPDLPR-printer.html">Adding an LPD/LPR Host or Printer</a></dt><dt>Local Printers, <a class="indexterm" href="sec-Adding_Other_Printer.html">Adding a Local Printer</a></dt><dt>New Printer, <a class="indexterm" href="sec-Setting_Printer.html">Starting Printer Setup</a></dt><dt>Print Jobs, <a class="indexterm" href="s1-printing-edit.html#s1-printing-managing">Managing Print Jobs</a></dt><dt>Samba Printers, <a class="indexterm" href="s1-printing-smb-printer.html">Adding a Samba (SMB) printer</a></dt><dt>Settings, <a class="indexterm" href="s1-printing-edit.html#idm261784076384">The Settings Page</a></
dt><dt>Sharing Printers, <a class="indexterm" href="s1-printing-edit.html#sec-Sharing_Printers">Sharing Printers</a></dt></dl></dd><dt>printers (see Printer Configuration)</dt><dt>processes, <a class="indexterm" href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">Viewing 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 lockfiles, <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_Monitorin
g_Tools.html#s2-sysinfo-system-processes-ps">Using the ps Command</a></dt></dl></div><div class="indexdiv"><h3>R</h3><dl><dt>RAM, <a class="indexterm" href="s1-sysinfo-memory-usage.html">Viewing Memory Usage</a></dt><dt>rcp, <a class="indexterm" href="s2-ssh-clients-scp.html">Using the scp Utility</a></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> rpcclient 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="s1-rpm-using.html#s3-rpm-errors">Replacing Already-Installed Packages</a></dt><dt>basic modes, <a class="indexterm" href="s1-rpm-using.html">Using RPM</a></dt><dt>ch
ecking package signatures, <a class="indexterm" href="s1-check-rpm-sig.html">Checking Package Signatures</a></dt><dt>configuration file changes, <a class="indexterm" href="s1-rpm-using.html#sec-Configuration_File_Changes">Preserving Changes in Configuration Files</a></dt><dd><dl><dt>conf.rpmsave, <a class="indexterm" href="s1-rpm-using.html#sec-Configuration_File_Changes">Preserving Changes in Configuration Files</a></dt></dl></dd><dt>conflicts, <a class="indexterm" href="s1-rpm-using.html#s3-rpm-conflicting-files">Resolving File Conflicts</a></dt><dt>dependencies, <a class="indexterm" href="s1-rpm-using.html#s3-rpm-unresolved-dependency">Satisfying Unresolved Dependencies</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 Go
als</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-usage-examples.html">Common Examples of RPM Usage</a></dt><dt>documentation with, <a class="indexterm" href="s1-rpm-usage-examples.html">Common Examples of RPM Usage</a></dt><dt>failed dependencies, <a class="indexterm" href="s1-rpm-using.html#s3-rpm-unresolved-dependency">Satisfying Unresolved Dependencies</a></dt><dt>file conflicts</dt><dd><dl><dt>resolving, <a class="indexterm" href="s1-rpm-using.html#s3-rpm-conflicting-files">Resolving File Conflicts</a></dt></dl></dd><dt>file name, <a class="indexterm" href="s1-rpm-using.html#sec-Installing_and_Upgrading">Installing and Upgrading Packages</a></dt><dt>finding and verifying RPM packages, <a class="indexterm" href="s1-find-verify-rpm.html">Finding and Verifying RPM Packages</a></dt><dt>finding deleted files with, <a class="indexterm" h
ref="s1-rpm-usage-examples.html">Common Examples of RPM Usage</a></dt><dt>finding Fedora RPM packages, <a class="indexterm" href="s1-find-verify-rpm.html#s2-rpm-finding">Finding RPM Packages</a></dt><dt>freshening, <a class="indexterm" href="s2-rpm-freshening.html">Freshening Packages</a></dt><dt>GnuPG, <a class="indexterm" href="s1-check-rpm-sig.html">Checking Package Signatures</a></dt><dt>installing, <a class="indexterm" href="s1-rpm-using.html#sec-Installing_and_Upgrading">Installing and Upgrading Packages</a></dt><dt>online documentation, <a class="indexterm" href="s1-rpm-additional-resources.html">Additional Resources</a></dt><dt>querying, <a class="indexterm" href="s2-rpm-querying.html">Querying Packages</a></dt><dt>querying for file list, <a class="indexterm" href="s1-rpm-usage-examples.html">Common Examples of RPM Usage</a></dt><dt>querying uninstalled packages, <a class="indexterm" href="s1-rpm-usage-examples.html">Common Examples of RPM Usage</a></dt><dt>see also,
<a class="indexterm" href="s1-rpm-additional-resources.html">Additional Resources</a></dt><dt>tips, <a class="indexterm" href="s1-rpm-usage-examples.html">Common Examples of RPM Usage</a></dt><dt>uninstalling, <a class="indexterm" href="s2-rpm-uninstalling.html">Uninstalling Packages</a></dt><dt>upgrading, <a class="indexterm" href="s1-rpm-using.html#sec-Installing_and_Upgrading">Installing and Upgrading Packages</a></dt><dt>verification, <a class="indexterm" href="s2-rpm-verifying.html">Verifying Packages</a></dt><dt>verifying, <a class="indexterm" href="s2-rpm-verifying.html">Verifying Packages</a></dt><dt>website, <a class="indexterm" href="s1-rpm-additional-resources.html">Additional Resources</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>rsyslog, <a class="indexterm" href="c
h-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">S
amba 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-sam
ba-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-samba-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></dl></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-sa
mba-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>Samba Printers, <a class="indexterm" href="s1-printing-smb-printer.html">Adding a Samba (SMB) printer</a></dt><dt>Security Modes, <a class="ind
exterm" 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-serve
rs">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-samba-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-sta
rtstop">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">Samba 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 examp
le, <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="indexte
rm" 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> security plug-in (see Security)</dt><dt>Security-Related Packages</dt><dd><dl><dt>updating security-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">Add
itional 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-mta-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_Daemons.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="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">Shadow Passwords</a></dt></dl></dd><dt>slapd (see OpenLDAP)</d
t><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 Programs</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#s2-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 Co
nnection</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="s2-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-Op
enSSH.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-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 HTTP Server)</dt><dt>stunnel, <a class="indexterm" href="s1-email-mua.html#s3-email-security-servers">Securing Email Client Communications</a></dt><dt>system analysis</dt><dd><dl><dt>OProfile (see OProfile)</dt></dl></dd><dt>system information</dt><dd><dl><dt>cpu usage, <a class="indexterm" href="s1-sysinfo-cpu.html">Viewing CPU Usage</a></dt><dt>file systems, <a class="indexterm" href="s1-sysinfo-filesystems.html">Viewing Block Devices and File Systems</a></dt><dd><d
l><dt>/dev/shm, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the df Command</a></dt><dt>/run, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the df Command</a></dt><dt>/sys/fs/cgroup, <a class="indexterm" href="s2-sysinfo-filesystems-df.html">Using the df Command</a></dt></dl></dd><dt>gathering, <a class="indexterm" href="ch-System_Monitoring_Tools.html">System Monitoring Tools</a></dt><dt>hardware, <a class="indexterm" href="s1-sysinfo-hardware.html">Viewing Hardware Information</a></dt><dt>memory usage, <a class="indexterm" href="s1-sysinfo-memory-usage.html">Viewing Memory Usage</a></dt><dt>processes, <a class="indexterm" href="ch-System_Monitoring_Tools.html#s1-sysinfo-system-processes">Viewing System Processes</a></dt><dd><dl><dt>currently running, <a class="indexterm" href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-top">Using the top Command</a></dt></dl></dd></dl></dd><dt>System Log</dt><dd><dl><dt>filtering, <a
class="indexterm" href="s1-managing_log_files_in_a_graphical_environment.html#s2-logfiles-viewing">Viewing Log Files</a></dt><dt>monitoring, <a class="indexterm" href="s2-logfiles-examining.html">Monitoring Log Files</a></dt><dt>refresh rate, <a class="indexterm" href="s1-managing_log_files_in_a_graphical_environment.html#s2-logfiles-viewing">Viewing Log Files</a></dt><dt>searching, <a class="indexterm" href="s1-managing_log_files_in_a_graphical_environment.html#s2-logfiles-viewing">Viewing Log Files</a></dt></dl></dd><dt>System Monitor, <a class="indexterm" href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="s2-sysinfo-memory-usage-system_monitor.html">Using the System Monitor Tool</a>, <a class="indexterm" href="s1-sysinfo-cpu.html#s2-sysinfo-cpu-system_monitor">Using the System Monitor Tool</a>, <a class="indexterm" href="s2-sysinfo-filesystems-system_monitor.html">Using the System
Monitor Tool</a></dt><dt> 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>the Users settings tool (see user configuration)</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>top, <a class="indexterm" href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-top">Using the top Command</a></dt></dl></div><div class="indexdiv"><h3>U</h3><dl><dt>user configuration</dt><dd><dl><dt>command line configuration</dt><dd><dl><dt>chage, <a class="indexterm" href="s2-users-tools-password-aging.html">Enabling Password Aging</a></dt><dt>passwd, <a class="indexterm" href="s1-users-tools.html#s2-users-tools-users-add">Adding a New User</a></dt><dt>useradd, <a class="indexterm" href="s
1-users-tools.html#s2-users-tools-users-add">Adding a New User</a></dt></dl></dd><dt>password</dt><dd><dl><dt>forcing expiration of, <a class="indexterm" href="s2-users-tools-password-aging.html">Enabling Password Aging</a></dt></dl></dd><dt>viewing list of users, <a class="indexterm" href="s1-users-configui.html">Managing Users in a Graphical Environment</a></dt></dl></dd><dt>user private groups (see groups)</dt><dd><dl><dt>and shared directories, <a class="indexterm" href="s2-users-tools-groups-directories.html">Creating 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-tools-users-add">Adding a New User</a></dt></dl></dd><dt>users (see user configuration)</dt><dd><dl><dt>additional resources, <a class="indexterm" href="sect-Users_and_Groups-Resources.html">Additional Resources</a></dt><dd><dl><dt>installed documentation, <a class="indexterm" href="sect-Users_and_Grou
ps-Resources.html">Additional Resources</a></dt></dl></dd><dt>introducing, <a class="indexterm" href="ch-Managing_Users_and_Groups.html">Managing Users and Groups</a></dt><dt>tools for management of</dt><dd><dl><dt>the Users setting tool, <a class="indexterm" href="s1-users-tools.html">Using Command Line Tools</a></dt><dt>useradd, <a class="indexterm" href="s1-users-tools.html">Using Command Line 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 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 Documentati
on</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" h
ref="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-net">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>RP
M</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 usi
ng 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 Passwords</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 plug-ins, <a class="indexterm" href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring, and Disabling Yum Plug-ins</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 plug-ins, <a class="indexterm" href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring, and Disabling Yum Plug-ins</a></dt><dt>displaying packages</dt><dd><dl><dt>yum info, <a class="indexterm" href="sec-Displaying_Package_Information.html">Displaying Package Information</a></dt></dl></dd><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 plug-ins, <a class="indexterm" href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">Enabling, Configuring, and Disabling Yum Plug-ins</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.h
tml">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>plug-ins</dt><dd><dl><dt>fs-snapshot, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plug-in Descriptions</a></dt><dt>presto, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plug-in Descriptions</a></dt><dt>refresh-packagekit, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plug-in Descriptions</a></dt><dt>rhnplugin, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plug-in Descriptions</a></dt><dt>security, <a class="indexterm" href="sec-Plugin_Descriptions.html">Plug-in Descriptions</a></dt></dl></dd><dt>repository, <a class="indexterm" href="sec-Managing_Yum_Reposito
ries.html">Adding, Enabling, and Disabling a Yum Repository</a>, <a class="indexterm" href="sec-Creating_a_Yum_Repository.html">Creating a Yum Repository</a></dt><dt>searching for 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>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 plug-ins, <a class="indexterm" href="sec-Yum_Plugins.html">Yum Plug-ins</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 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>upd
ating packages, <a class="indexterm" href="ch-yum.html#sec-Updating_Packages">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 B. 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>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Basic_System_Configuration.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Basic_System_Configuration.html
index e7b6197..8df1222 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Basic_System_Configuration.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Basic_System_Configuration.html
@@ -6,6 +6,6 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="pref-Acknowledgments.html" title="5. Acknowledgments" /><link rel="next" href="ch-Opening_GUI_Applications.html" title="Chapter 1. Opening Graphical Applications" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Acknowledgments.html"><strong>Prev</strong></a></li><li class="next">
<a accesskey="n" href="ch-Opening_GUI_Applications.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="idm225468635136"><div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="pref-Acknowledgments.html" title="5. Acknowledgments" /><link rel="next" href="ch-Opening_GUI_Applications.html" title="Chapter 1. Opening Graphical Applications" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Acknowledgments.html"><strong>Prev</strong></a></li><li class="next">
<a accesskey="n" href="ch-Opening_GUI_Applications.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="idm261783994688"><div></div><div class="para">
This part covers basic system administration tasks such as keyboard configuration, date and time configuration, managing users and groups, and gaining privileges.
- </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="ch-Opening_GUI_Applications.html">1. Opening Graphical Applications</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Opening_GUI_Applications.html#gui-from_cli">1.1. Opening graphical applications from the command line</a></span></dt><dt><span class="section"><a href="gui-alt_f2.html">1.2. Launching Applications with <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> </a></span></dt><dt><span class="section"><a href="gui-from_menu.html">1.3. Launching applications from the Desktop Menu</a></span></dt><dd><dl><dt><span class="section"><a href="gui-from_menu.html#gui-from_menu-gnome">1.3.1. Using GNOME menus</a></span></dt><dt><span class="section"><a href="gui-from_menu-kde.html">1.3.2. Using KDE menus </a></span></dt><dt><span class="section"><a href="ch01s03s03.html">1.3.3. Using menus in LXDE, MATE
, and XFCE</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-System_Locale_and_Keyboard_Configuration.html">2. System Locale and Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s1-Setting_the_System_Locale">2.1. Setting the System Locale</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Displaying_the_Current_Status">2.1.1. Displaying the Current Status</a></span></dt><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Listing_Available_Locales">2.1.2. Listing Available Locales</a></span></dt><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Setting_the_Locale">2.1.3. Setting the Locale</a></span></dt></dl></dd><dt><span class="section"><a href="s1-Changing_the_Keyboard_Layout.html">2.2. Changing the Keyboard Layout</a></span></dt><dd><dl><dt
><span class="section"><a href="s1-Changing_the_Keyboard_Layout.html#s2-Displaying_the_Current_Settings">2.2.1. Displaying the Current Settings</a></span></dt><dt><span class="section"><a href="s2-Listing_Available_Keymaps.html">2.2.2. Listing Available Keymaps</a></span></dt><dt><span class="section"><a href="s2-Setting_the_Keymap.html">2.2.3. Setting the Keymap</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Keyboard_Configuration-Resources.html">2.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Configuring_the_Date_and_Time.html">3. Configuring the Date and Time</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl">3.1. Using the timedatectl Command</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Display">3.1.1. Displaying the Current
Date and Time</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Time">3.1.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Date">3.1.3. Changing the Current Date</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone">3.1.4. Changing the Time Zone</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-NTP">3.1.5. Synchronizing the System Clock with a Remote Server</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date.html">3.2. Using the date Command</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date.html#sect-Configurin
g_the_Date_and_Time-date-Display">3.2.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date-Time.html">3.2.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date-Date.html">3.2.3. Changing the Current Date</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-hwclock.html">3.3. Using the hwclock Command</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-hwclock.html#sect2-displaying-time-hwclock">3.3.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="sect3-changing-date-time-hwclock.html">3.3.2. Setting the Date and Time</a></span></dt><dt><span class="section"><a href="sect4-synchronizing-date-time-hwclock.html">3.3.3. Synchronizing the Date and Time</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Da
te_and_Time-Resources.html">3.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Managing_Users_and_Groups.html">4. Managing Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s1-users-groups-introduction">4.1. Introduction to Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">4.1.1. User Private Groups</a></span></dt><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">4.1.2. Shadow Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-configui.html">4.2. Using the User Manager Tool</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-configui.html#s2-redhat-config-users-list">4.2.1. Viewing Users and Groups</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-tools.html">4.3. Using Command
Line Tools</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-tools.html#s2-users-tools-users-add">4.3.1. Adding a New User</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-add.html">4.3.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="s2-users-tools-password-aging.html">4.3.3. Enabling Password Aging</a></span></dt><dt><span class="section"><a href="s2-users-tools-users-logout.html">4.3.4. Enabling Automatic Logouts</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-directories.html">4.3.5. Creating Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-groups-additional-resources.html">4.4. Additional Resources</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Acknowledgments.html"><strong>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-Opening_GUI_Applications.html"><strong>Next</strong>Chapter 1. Opening Graphical Applications</a></li></ul></body></html>
\ No newline at end of file
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="ch-Opening_GUI_Applications.html">1. Opening Graphical Applications</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Opening_GUI_Applications.html#gui-from_cli">1.1. Opening graphical applications from the command line</a></span></dt><dt><span class="section"><a href="gui-alt_f2.html">1.2. Launching Applications with <span class="keycap"><strong>Alt</strong></span>+<span class="keycap"><strong>F2</strong></span> </a></span></dt><dt><span class="section"><a href="gui-from_menu.html">1.3. Launching applications from the Desktop Menu</a></span></dt><dd><dl><dt><span class="section"><a href="gui-from_menu.html#gui-from_menu-gnome">1.3.1. Using GNOME menus</a></span></dt><dt><span class="section"><a href="gui-from_menu-kde.html">1.3.2. Using KDE menus </a></span></dt><dt><span class="section"><a href="ch01s03s03.html">1.3.3. Using menus in LXDE, MATE
, and XFCE</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-System_Locale_and_Keyboard_Configuration.html">2. System Locale and Keyboard Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s1-Setting_the_System_Locale">2.1. Setting the System Locale</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Displaying_the_Current_Status">2.1.1. Displaying the Current Status</a></span></dt><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Listing_Available_Locales">2.1.2. Listing Available Locales</a></span></dt><dt><span class="section"><a href="ch-System_Locale_and_Keyboard_Configuration.html#s2-Setting_the_Locale">2.1.3. Setting the Locale</a></span></dt></dl></dd><dt><span class="section"><a href="s1-Changing_the_Keyboard_Layout.html">2.2. Changing the Keyboard Layout</a></span></dt><dd><dl><dt
><span class="section"><a href="s1-Changing_the_Keyboard_Layout.html#s2-Displaying_the_Current_Settings">2.2.1. Displaying the Current Settings</a></span></dt><dt><span class="section"><a href="s2-Listing_Available_Keymaps.html">2.2.2. Listing Available Keymaps</a></span></dt><dt><span class="section"><a href="s2-Setting_the_Keymap.html">2.2.3. Setting the Keymap</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Keyboard_Configuration-Resources.html">2.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Configuring_the_Date_and_Time.html">3. Configuring the Date and Time</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl">3.1. Using the timedatectl Command</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Display">3.1.1. Displaying the Current
Date and Time</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Time">3.1.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Date">3.1.3. Changing the Current Date</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-Time_Zone">3.1.4. Changing the Time Zone</a></span></dt><dt><span class="section"><a href="ch-Configuring_the_Date_and_Time.html#sect-Configuring_the_Date_and_Time-timedatectl-NTP">3.1.5. Synchronizing the System Clock with a Remote Server</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date.html">3.2. Using the date Command</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date.html#sect-Configurin
g_the_Date_and_Time-date-Display">3.2.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date-Time.html">3.2.2. Changing the Current Time</a></span></dt><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-date-Date.html">3.2.3. Changing the Current Date</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-hwclock.html">3.3. Using the hwclock Command</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Configuring_the_Date_and_Time-hwclock.html#sect2-displaying-time-hwclock">3.3.1. Displaying the Current Date and Time</a></span></dt><dt><span class="section"><a href="sect3-changing-date-time-hwclock.html">3.3.2. Setting the Date and Time</a></span></dt><dt><span class="section"><a href="sect4-synchronizing-date-time-hwclock.html">3.3.3. Synchronizing the Date and Time</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Da
te_and_Time-Resources.html">3.4. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Managing_Users_and_Groups.html">4. Managing Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s1-users-groups-introduction">4.1. Introduction to Users and Groups</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-private-groups">4.1.1. User Private Groups</a></span></dt><dt><span class="section"><a href="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">4.1.2. Shadow Passwords</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-configui.html">4.2. Managing Users in a Graphical Environment</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-configui.html#s2-redhat-config-users-list">4.2.1. Using the Users Settings Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-users-tools.html"
>4.3. Using Command Line Tools</a></span></dt><dd><dl><dt><span class="section"><a href="s1-users-tools.html#s2-users-tools-users-add">4.3.1. Adding a New User</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-add.html">4.3.2. Adding a New Group</a></span></dt><dt><span class="section"><a href="s2-users-tools-password-aging.html">4.3.3. Enabling Password Aging</a></span></dt><dt><span class="section"><a href="s2-users-tools-users-logout.html">4.3.4. Enabling Automatic Logouts</a></span></dt><dt><span class="section"><a href="s2-users-tools-groups-directories.html">4.3.5. Creating Group Directories</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Users_and_Groups-Resources.html">4.4. Additional Resources</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="pref-Acknowledgments.html"><strong>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-Opening_GUI_Applications.html"><strong>Next</strong>Chapter 1. Opening Graphical Applications</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Infrastructure_Services.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Infrastructure_Services.html
index 98b3be7..9b9cd5b 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Infrastructure_Services.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Infrastructure_Services.html
@@ -6,6 +6,6 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="sec-Additional_Resources.html" title="5.5. Additional Resources" /><link rel="next" href="ch-Services_and_Daemons.html" title="Chapter 6. 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="sec-Additional_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 III. Infrastructure Services</h1></div></div></div><div class="partintro" id="idm225458463584"><div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="sec-Additional_Resources.html" title="5.5. Additional Resources" /><link rel="next" href="ch-Services_and_Daemons.html" title="Chapter 6. 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="sec-Additional_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 III. Infrastructure Services</h1></div></div></div><div class="partintro" id="idm261745348448"><div></div><div class="para">
This part provides information on how to configure services and daemons, configure authentication, and enable remote logins.
- </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="ch-Services_and_Daemons.html">6. Services and Daemons</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s1-services-configuring">6.1. Configuring Services</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">6.1.1. Enabling the Service</a></span></dt><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-disabling">6.1.2. Disabling the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-running.html">6.2. Running Services</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-running.html#s3-services-running-checking">6.2.1. Checking the Service Status</a></span></dt><dt><span class="section"><a href="s3-services-running-running.html">6.2.2. Running the Service</a></span></dt><
dt><span class="section"><a href="s3-services-running-stopping.html">6.2.3. Stopping the Service</a></span></dt><dt><span class="section"><a href="s3-services-running-restarting.html">6.2.4. Restarting the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-additional-resources.html">6.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-additional-resources.html#s2-services-additional-resources-installed">6.3.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-services-additional-resources-books.html">6.3.2. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-OpenSSH.html">7. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s1-ssh-protocol">7.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-why">7.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a hr
ef="ch-OpenSSH.html#s2-ssh-features">7.1.2. Main Features</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-versions">7.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">7.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-configuration.html">7.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-configuration.html#s2-ssh-configuration-configs">7.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-sshd.html">7.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-requiring.html">7.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-keypairs.html">7.2.4. Using Key-based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-clien
ts.html">7.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-clients.html#s2-ssh-clients-ssh">7.3.1. Using the ssh Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-scp.html">7.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-sftp.html">7.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">7.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">7.4.1. X11 Forwarding</a></span></dt><dt><span class="section"><a href="s2-ssh-beyondshell-tcpip.html">7.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="s1-openssh-additional-resources.html">7.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-TigerVNC.html">8. TigerVNC</a>
</span></dt><dd><dl><dt><span class="section"><a href="ch-TigerVNC.html#s1-vnc-server">8.1. VNC Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-TigerVNC.html#s2-vnc-installation">8.1.1. Installing VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#s3-configuring-vnc-server">8.1.2. Configuring VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#s4-starting-vncserver">8.1.3. Starting VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#terminating-vnc-session">8.1.4. Terminating a VNC session</a></span></dt></dl></dd><dt><span class="section"><a href="s5-vnc-viewer.html">8.2. VNC Viewer</a></span></dt><dd><dl><dt><span class="section"><a href="s5-vnc-viewer.html#installing-vncviewer">8.2.1. Installing VNC Viewer</a></span></dt><dt><span class="section"><a href="s6-connecting-vnc-viewer.html">8.2.2. Connecting to VNC Server</a></span></dt><dt><span class="section"><a href="s1-using
_ssh.html">8.2.3. Connecting to VNC Server using SSH</a></span></dt></dl></dd><dt><span class="section"><a href="s9-additional-sources.html">8.3. Additional Resources</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Additional_Resources.html"><strong>Prev</strong>5.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="ch-Services_and_Daemons.html"><strong>Next</strong>Chapter 6. Services and Daemons</a></li></ul></body></html>
\ No newline at end of file
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="ch-Services_and_Daemons.html">6. Services and Daemons</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s1-services-configuring">6.1. Configuring Services</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-enabling">6.1.1. Enabling the Service</a></span></dt><dt><span class="section"><a href="ch-Services_and_Daemons.html#s3-services-configuration-disabling">6.1.2. Disabling the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-running.html">6.2. Running Services</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-running.html#s3-services-running-checking">6.2.1. Checking the Service Status</a></span></dt><dt><span class="section"><a href="s3-services-running-running.html">6.2.2. Running the Service</a></span></dt><
dt><span class="section"><a href="s3-services-running-stopping.html">6.2.3. Stopping the Service</a></span></dt><dt><span class="section"><a href="s3-services-running-restarting.html">6.2.4. Restarting the Service</a></span></dt></dl></dd><dt><span class="section"><a href="s1-services-additional-resources.html">6.3. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-services-additional-resources.html#s2-services-additional-resources-installed">6.3.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-services-additional-resources-books.html">6.3.2. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-OpenSSH.html">7. OpenSSH</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s1-ssh-protocol">7.1. The SSH Protocol</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-why">7.1.1. Why Use SSH?</a></span></dt><dt><span class="section"><a hr
ef="ch-OpenSSH.html#s2-ssh-features">7.1.2. Main Features</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-versions">7.1.3. Protocol Versions</a></span></dt><dt><span class="section"><a href="ch-OpenSSH.html#s2-ssh-conn">7.1.4. Event Sequence of an SSH Connection</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-configuration.html">7.2. An OpenSSH Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-configuration.html#s2-ssh-configuration-configs">7.2.1. Configuration Files</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-sshd.html">7.2.2. Starting an OpenSSH Server</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-requiring.html">7.2.3. Requiring SSH for Remote Connections</a></span></dt><dt><span class="section"><a href="s2-ssh-configuration-keypairs.html">7.2.4. Using Key-based Authentication</a></span></dt></dl></dd><dt><span class="section"><a href="s1-ssh-clien
ts.html">7.3. OpenSSH Clients</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ssh-clients.html#s2-ssh-clients-ssh">7.3.1. Using the ssh Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-scp.html">7.3.2. Using the <code class="command">scp</code> Utility</a></span></dt><dt><span class="section"><a href="s2-ssh-clients-sftp.html">7.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">7.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">7.4.1. X11 Forwarding</a></span></dt><dt><span class="section"><a href="s2-ssh-beyondshell-tcpip.html">7.4.2. Port Forwarding</a></span></dt></dl></dd><dt><span class="section"><a href="s1-openssh-additional-resources.html">7.5. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-TigerVNC.html">8. TigerVNC</a>
</span></dt><dd><dl><dt><span class="section"><a href="ch-TigerVNC.html#s1-vnc-server">8.1. VNC Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-TigerVNC.html#s2-vnc-installation">8.1.1. Installing VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#s3-configuring-vnc-server">8.1.2. Configuring VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#s4-starting-vncserver">8.1.3. Starting VNC Server</a></span></dt><dt><span class="section"><a href="ch-TigerVNC.html#terminating-vnc-session">8.1.4. Terminating a VNC Session</a></span></dt></dl></dd><dt><span class="section"><a href="s5-vnc-viewer.html">8.2. VNC Viewer</a></span></dt><dd><dl><dt><span class="section"><a href="s5-vnc-viewer.html#installing-vncviewer">8.2.1. Installing VNC Viewer</a></span></dt><dt><span class="section"><a href="s6-connecting-vnc-viewer.html">8.2.2. Connecting to VNC Server</a></span></dt><dt><span class="section"><a href="s1-using
_ssh.html">8.2.3. Connecting to VNC Server Using SSH</a></span></dt></dl></dd><dt><span class="section"><a href="s9-additional-sources.html">8.3. Additional Resources</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Additional_Resources.html"><strong>Prev</strong>5.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="ch-Services_and_Daemons.html"><strong>Next</strong>Chapter 6. Services and Daemons</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Kernel_Module_and_Driver_Configuration.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Kernel_Module_and_Driver_Configuration.html
index 9f1a711..c19a4a4 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Kernel_Module_and_Driver_Configuration.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Kernel_Module_and_Driver_Configuration.html
@@ -6,6 +6,6 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="s2-oprofile-useful-websites.html" title="19.11.2. Useful Websites" /><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="s2-oprofile-useful-websites.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 VI. Kernel, Module and Driver Configuration</h1></div></div></div><div class="partintro" id="idm225463146160"><div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="s1-oprofile_additional_resources.html" title="19.12. Additional Resources" /><link rel="next" href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="Chapter 20. Working with the GRUB 2 Boot Loader" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile_additional_resources.htm
l"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Working_with_the_GRUB_2_Boot_Loader.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 VI. Kernel, Module and Driver Configuration</h1></div></div></div><div class="partintro" id="idm261738998016"><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 class="toc"><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-boo
t-loader.html#s3-kernel-boot-loader-grub">20.6.1. Configuring the GRUB 2 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="s1-kernel-modules-additional-resources.html">21.7. Additional Resources</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-useful-websites.html"><strong>Prev</strong>19.11.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-Manually_Upgrading_the_Kernel.html"><strong>Next</strong>Chapter 20. Manually Upgrading the Kernel</a></li></ul></body></html>
\ No newline at end of file
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="ch-Working_with_the_GRUB_2_Boot_Loader.html">20. Working with the GRUB 2 Boot Loader</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Working_with_the_GRUB_2_Boot_Loader.html#sec-Configuring_the_GRUB_2_Boot_Loader">20.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="sec-Customizing_GRUB_2_Menu.html">20.2. Customizing GRUB 2 Menu</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Customizing_GRUB_2_Menu.html#sec-Changing_the_Default_Boot_Entry">20.2.1. Changing the Default Boot Entry</a></span></dt><dt><span class="section"><a href="sec-Editing_an_Entry.html">20.2.2. Editing an Entry</a></span></dt><dt><span class="section"><a href="sec-Adding_a_new_Entry.html">20.2.3. Adding a new Entry</a></span></dt><dt><span class="section"><a href="sec-Using_only_a_Custom_Menu.html">20.2.4. Creating a Custom Me
nu</a></span></dt></dl></dd><dt><span class="section"><a href="sec-GRUB_2_Password_Protection.html">20.3. GRUB 2 Password Protection</a></span></dt><dd><dl><dt><span class="section"><a href="sec-GRUB_2_Password_Protection.html#sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries">20.3.1. Setting Up Users and Password Protection, Specifying Menu Entries</a></span></dt><dt><span class="section"><a href="sec-Password_Encryption.html">20.3.2. Password Encryption</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Reinstalling_GRUB_2.html">20.4. Reinstalling GRUB 2</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Reinstalling_GRUB_2.html#sec-Using_the_grub2-install_Command">20.4.1. Using the grub2-install Command</a></span></dt><dt><span class="section"><a href="sec-Resetting_and_Reinstalling_GRUB_2.html">20.4.2. Resetting and Reinstalling GRUB 2</a></span></dt></dl></dd><dt><span class="section"><a href="sec-GRUB_2_over_Serial_Console.htm
l">20.5. GRUB 2 over Serial Console</a></span></dt><dd><dl><dt><span class="section"><a href="sec-GRUB_2_over_Serial_Console.html#sec-Configuring_GRUB_2">20.5.1. Configuring GRUB 2</a></span></dt><dt><span class="section"><a href="sec-Using_screen_to_Connect_to_the_Serial_Console.html">20.5.2. Using screen to Connect to the Serial Console</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Terminal_Menu_Editing_During_Boot.html">20.6. Terminal Menu Editing During Boot</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Terminal_Menu_Editing_During_Boot.html#sec-Booting_to_Rescue_Mode">20.6.1. Booting to Rescue Mode</a></span></dt><dt><span class="section"><a href="sec-Booting_to_Emergency_Mode.html">20.6.2. Booting to Emergency Mode</a></span></dt><dt><span class="section"><a href="sec-Changing_and_Resetting_the_Root_Password.html">20.6.3. Changing and Resetting the Root Password</a></span></dt></dl></dd><dt><span class="section"><a href="sec-UEFI_Secur
e_Boot.html">20.7. UEFI Secure Boot</a></span></dt><dd><dl><dt><span class="section"><a href="sec-UEFI_Secure_Boot.html#sec-UEFI_Secure_Boot_Support_in_Fedora">20.7.1. UEFI Secure Boot Support in Fedora</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html">20.8. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-Manually_Upgrading_the_Kernel.html">21. Manually Upgrading the Kernel</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">21.1. Overview of Kernel Packages</a></span></dt><dt><span class="section"><a href="s1-kernel-preparing.html">21.2. Preparing to Upgrade</a></span></dt><dt><span class="section"><a href="s1-kernel-download.html">21.3. Downloading the Upgraded Kernel</a></span></dt><dt><span class="section"><a href="s1-kernel-perform-upgrade.html">21.4. Performing the Upgrade</a></span></dt><dt><sp
an class="section"><a href="sec-Verifying_the_Initial_RAM_Disk_Image.html">21.5. Verifying the Initial RAM Disk Image</a></span></dt><dt><span class="section"><a href="s1-kernel-boot-loader.html">21.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">21.6.1. Configuring the GRUB 2 Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-iseries.html">21.6.2. Configuring the OS/400 Boot Loader</a></span></dt><dt><span class="section"><a href="s2-kernel-boot-loader-pseries.html">21.6.3. Configuring the YABOOT Boot Loader</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Working_with_Kernel_Modules.html">22. Working with Kernel Modules</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">22.1. Listing Currently-Loaded Modules</a></span></dt><dt><span class="secti
on"><a href="sec-Displaying_Information_About_a_Module.html">22.2. Displaying Information About a Module</a></span></dt><dt><span class="section"><a href="sec-Loading_a_Module.html">22.3. Loading a Module</a></span></dt><dt><span class="section"><a href="sec-Unloading_a_Module.html">22.4. Unloading a Module</a></span></dt><dt><span class="section"><a href="sec-Setting_Module_Parameters.html">22.5. Setting Module Parameters</a></span></dt><dt><span class="section"><a href="sec-Persistent_Module_Loading.html">22.6. Persistent Module Loading</a></span></dt><dt><span class="section"><a href="sect-signing-kernel-modules-for-secure-boot.html">22.7. Signing Kernel Modules for Secure Boot</a></span></dt><dd><dl><dt><span class="section"><a href="sect-signing-kernel-modules-for-secure-boot.html#sect-prerequisites">22.7.1. Prerequisites</a></span></dt><dt><span class="section"><a href="sect-kernel-module-authentication.html">22.7.2. Kernel Module Authentication</a></span></dt><dt><spa
n class="section"><a href="sect-generating-a-public-private-x509-key-pair.html">22.7.3. Generating a Public and Private X.509 Key Pair</a></span></dt><dt><span class="section"><a href="sect-enrolling-public-key-on-target-system.html">22.7.4. Enrolling Public Key on Target System</a></span></dt><dt><span class="section"><a href="sect-signing-kernel-module-with-the-private-key.html">22.7.5. Signing Kernel Module with the Private Key</a></span></dt><dt><span class="section"><a href="sect-loading-signed-kernel-module.html">22.7.6. Loading Signed Kernel Module</a></span></dt></dl></dd><dt><span class="section"><a href="s1-kernel-modules-additional-resources.html">22.8. Additional Resources</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile_additional_resources.html"><strong>Prev</strong>19.12. 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-Working_with_the_GRUB_2_Boot_Loader.html"><strong>Next</strong>Chapter 20. Working with the GRUB 2 Boot Loader</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Monitoring_and_Automation.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Monitoring_and_Automation.html
index 72d6ffe..80e59b5 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Monitoring_and_Automation.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Monitoring_and_Automation.html
@@ -6,6 +6,6 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="sec-PTP_useful-websites.html" title="15.10.2. Useful Websites" /><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="sec-PTP_useful-websites.html"><strong>Prev</strong></a></li><li class="n
ext"><a accesskey="n" href="ch-System_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 V. Monitoring and Automation</h1></div></div></div><div class="partintro" id="idm225507247088"><div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="sec-PTP_useful-websites.html" title="15.11.2. Useful Websites" /><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="sec-PTP_useful-websites.html"><strong>Prev</strong></a></li><li class="n
ext"><a accesskey="n" href="ch-System_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 V. Monitoring and Automation</h1></div></div></div><div class="partintro" id="idm261739082608"><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 class="toc"><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. Viewing System Processes</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-ps">16.1.1. Using the ps Command</a></span></dt><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-top">16.1.2. Using the top Command</a></span></dt><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-system_monitor">16.1.3. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-memory-usage.html">16.2. Viewing Memory Usage</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-memory-usage.h
tml#s2-sysinfo-memory-usage-free">16.2.1. Using the free Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-memory-usage-system_monitor.html">16.2.2. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-cpu.html">16.3. Viewing CPU Usage</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-cpu.html#s2-sysinfo-cpu-system_monitor">16.3.1. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-filesystems.html">16.4. Viewing Block Devices and File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-filesystems.html#s2-sysinfo-filesystems-lsblk">16.4.1. Using the lsblk Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-blkid.html">16.4.2. Using the blkid Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-partx.html">16.4.3. Using the partx Command</a></span></dt><dt><spa
n class="section"><a href="s2-sysinfo-filesystems-findmnt.html">16.4.4. Using the findmnt Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-df.html">16.4.5. Using the df Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-du.html">16.4.6. Using the du Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-system_monitor.html">16.4.7. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-hardware.html">16.5. Viewing Hardware Information</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-hardware.html#s2-sysinfo-hardware-lspci">16.5.1. Using the lspci Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-hardware-lsusb.html">16.5.2. Using the lsusb Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-hardware-lspcmcia.html">16.5.3. Using the lspcmcia Command</a></span></dt><dt><span class="section"
><a href="s2-sysinfo-hardware-lscpu.html">16.5.4. Using the lscpu Command</a></span></dt></dl></dd><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP.html">16.6. Monitoring Performance with Net-SNMP</a></span></dt><dd><dl><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP.html#sect-System_Monitoring_Tools-Net-SNMP-Installing">16.6.1. Installing Net-SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Running.html">16.6.2. Running the Net-SNMP Daemon</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html">16.6.3. Configuring Net-SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html">16.6.4. Retrieving Performance Data over SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Extending.html">16.6.5. Extending Net-SNMP</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-sysinfo-additional-resources.html">16.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">16.7.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 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><sp
an 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#sect-Cron-Installing">18.1.1. Installing Cron and Anacron</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#sect-Cron-Running">18.1.2. Running the Crond Service</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">18.1.3. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">18.1.4. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="ch-Automating_Sy
stem_Tasks.html#s2-autotasks-cron-access">18.1.5. 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.6. Black and 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#sect-At_and_Batch_Installation">18.2.1. Installing At and Batch</a></span></dt><dt><span class="section"><a href="sect-Atd-Running.html">18.2.2. Running the At Service</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-configuring.html">18.2.3. Configuring an At Job</a></span></dt><dt><span class="section"><a href="s2-autotasks-batch-configuring.html">18.2.4. Configuring a Batch Job</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-viewing.html">18.2.5. Viewing Pending Jobs</a></span></dt><dt><span class="section"
><a href="s2-autotasks-commandline-options.html">18.2.6. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-controlling-access.html">18.2.7. Controlling Access to At and Batch</a></span></dt></dl></dd><dt><span class="section"><a href="s1-autotasks-additional-resources.html">18.3. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-OProfile.html">19. OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OProfile.html#s1-oprofile-overview-tools">19.1. Overview of Tools</a></span></dt><dt><span class="section"><a href="s1-oprofile-configuring.html">19.2. Configuring OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-configuring.html#s2-oprofile-kernel">19.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="s2-oprofile-events.html">19.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="s2-oprofile-
starting-separate.html">19.2.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-starting.html">19.3. Starting and Stopping OProfile</a></span></dt><dt><span class="section"><a href="s1-oprofile-saving-data.html">19.4. Saving Data</a></span></dt><dt><span class="section"><a href="s1-oprofile-analyzing-data.html">19.5. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">19.5.1. Using <code class="command">opreport</code> </a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opreport-single.html">19.5.2. Using opreport on a Single Executable</a></span></dt><dt><span class="section"><a href="s2-oprofile-module-output.html">19.5.3. Getting more detailed output on the modules</a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opannotate.html">19.5.4. Using <code class="command">opannotate</code>
</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-dev-oprofile.html">19.6. Understanding <code class="filename">/dev/oprofile/</code> </a></span></dt><dt><span class="section"><a href="s1-oprofile-example-usage.html">19.7. Example Usage</a></span></dt><dt><span class="section"><a href="s1-oprofile-java-support.html">19.8. OProfile Support for Java</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-java-support.html#s1-oprofile-java-profiling">19.8.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-gui.html">19.9. Graphical Interface</a></span></dt><dt><span class="section"><a href="s1-oprofile-and-systemtap.html">19.10. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="s1-oprofile-additional-resources.html">19.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-additional-resources.html#s1-oprofile-installed-docs">19.11.1. I
nstalled Docs</a></span></dt><dt><span class="section"><a href="s2-oprofile-useful-websites.html">19.11.2. Useful Websites</a></span></dt></dl></dd></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-PTP_useful-websites.html"><strong>Prev</strong>15.10.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-System_Monitoring_Tools.html"><strong>Next</strong>Chapter 16. System Monitoring Tools</a></li></ul></body></html>
\ No newline at end of file
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><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. Viewing System Processes</a></span></dt><dd><dl><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-ps">16.1.1. Using the ps Command</a></span></dt><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-top">16.1.2. Using the top Command</a></span></dt><dt><span class="section"><a href="ch-System_Monitoring_Tools.html#s2-sysinfo-system-processes-system_monitor">16.1.3. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-memory-usage.html">16.2. Viewing Memory Usage</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-memory-usage.h
tml#s2-sysinfo-memory-usage-free">16.2.1. Using the free Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-memory-usage-system_monitor.html">16.2.2. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-cpu.html">16.3. Viewing CPU Usage</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-cpu.html#s2-sysinfo-cpu-system_monitor">16.3.1. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-filesystems.html">16.4. Viewing Block Devices and File Systems</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-filesystems.html#s2-sysinfo-filesystems-lsblk">16.4.1. Using the lsblk Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-blkid.html">16.4.2. Using the blkid Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-partx.html">16.4.3. Using the partx Command</a></span></dt><dt><spa
n class="section"><a href="s2-sysinfo-filesystems-findmnt.html">16.4.4. Using the findmnt Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-df.html">16.4.5. Using the df Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-du.html">16.4.6. Using the du Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-filesystems-system_monitor.html">16.4.7. Using the System Monitor Tool</a></span></dt></dl></dd><dt><span class="section"><a href="s1-sysinfo-hardware.html">16.5. Viewing Hardware Information</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-hardware.html#s2-sysinfo-hardware-lspci">16.5.1. Using the lspci Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-hardware-lsusb.html">16.5.2. Using the lsusb Command</a></span></dt><dt><span class="section"><a href="s2-sysinfo-hardware-lspcmcia.html">16.5.3. Using the lspcmcia Command</a></span></dt><dt><span class="section"
><a href="s2-sysinfo-hardware-lscpu.html">16.5.4. Using the lscpu Command</a></span></dt></dl></dd><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP.html">16.6. Monitoring Performance with Net-SNMP</a></span></dt><dd><dl><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP.html#sect-System_Monitoring_Tools-Net-SNMP-Installing">16.6.1. Installing Net-SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Running.html">16.6.2. Running the Net-SNMP Daemon</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Configuring.html">16.6.3. Configuring Net-SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Retrieving.html">16.6.4. Retrieving Performance Data over SNMP</a></span></dt><dt><span class="section"><a href="sect-System_Monitoring_Tools-Net-SNMP-Extending.html">16.6.5. Extending Net-SNMP</a></span></dt></dl></dd><dt><span
class="section"><a href="s1-sysinfo-additional-resources.html">16.7. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-sysinfo-additional-resources.html#s2-sysinfo-installed-docs">16.7.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-logfiles-locating">17.1. Locating Log Files</a></span></dt><dt><span class="section"><a href="s1-basic_configuration_of_rsyslog.html">17.2. Basic Configuration of Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="s1-basic_configuration_of_rsyslog.html#s2-Filters">17.2.1. Filters</a></span></dt><dt><span class="section"><a href="s2-Actions.html">17.2.2. Actions</a></span></dt><dt><span class="section"><a href="s2-Templates.html">17.2.3. Templates</a></span></dt><dt><span class="s
ection"><a href="s2-global_directives.html">17.2.4. Global Directives</a></span></dt><dt><span class="section"><a href="s2-log_rotation.html">17.2.5. Log Rotation</a></span></dt><dt><span class="section"><a href="s2-using_the_new_configuration_format.html">17.2.6. Using the New Configuration Format</a></span></dt><dt><span class="section"><a href="s2-Rulesets.html">17.2.7. Rulesets</a></span></dt><dt><span class="section"><a href="s2-compatibility_with_syslogd.html">17.2.8. Compatibility with syslogd</a></span></dt></dl></dd><dt><span class="section"><a href="s1-working_with_queues_in_rsyslog.html">17.3. Working with Queues in Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="s1-working_with_queues_in_rsyslog.html#s2-defining_queues">17.3.1. Defining Queues</a></span></dt><dt><span class="section"><a href="s2-managing_queues.html">17.3.2. Managing Queues</a></span></dt></dl></dd><dt><span class="section"><a href="s1-using_rsyslog_modules.html">17.4. Using Rsy
slog Modules</a></span></dt><dd><dl><dt><span class="section"><a href="s1-using_rsyslog_modules.html#s2-importing_text_files">17.4.1. Importing Text Files</a></span></dt><dt><span class="section"><a href="s2-exporting_messages_to_a_database.html">17.4.2. Exporting Messages to a Database</a></span></dt><dt><span class="section"><a href="s2-enabling_encrypted_transport.html">17.4.3. Enabling Encrypted Transport</a></span></dt><dt><span class="section"><a href="s2-using_RELP.html">17.4.4. Using RELP</a></span></dt></dl></dd><dt><span class="section"><a href="s1-interaction_of_rsyslog_and_journal.html">17.5. Interaction of Rsyslog and Journal</a></span></dt><dt><span class="section"><a href="s1-structured_logging_with_rsyslog.html">17.6. Structured Logging with Rsyslog</a></span></dt><dd><dl><dt><span class="section"><a href="s1-structured_logging_with_rsyslog.html#s2-importing_data_from_journal">17.6.1. Importing Data from Journal</a></span></dt><dt><span class="section"><a hre
f="s2-filtering_structured_messages.html">17.6.2. Filtering Structured Messages</a></span></dt><dt><span class="section"><a href="s2-parsing_JSON.html">17.6.3. Parsing JSON</a></span></dt><dt><span class="section"><a href="s2-storing_messages_in_the_mongodb.html">17.6.4. Storing Messages in the MongoDB</a></span></dt></dl></dd><dt><span class="section"><a href="s1-debugging_rsyslog.html">17.7. Debugging Rsyslog</a></span></dt><dt><span class="section"><a href="s1-Using_the_Journal.html">17.8. Using the Journal</a></span></dt><dd><dl><dt><span class="section"><a href="s1-Using_the_Journal.html#s2-Viewing_Log_Files">17.8.1. Viewing Log Files</a></span></dt><dt><span class="section"><a href="s2-Access_Control.html">17.8.2. Access Control</a></span></dt><dt><span class="section"><a href="s2-Using_The_Live_View.html">17.8.3. Using The Live View</a></span></dt><dt><span class="section"><a href="s2-Filtering_Messages.html">17.8.4. Filtering Messages</a></span></dt><dt><span class="
section"><a href="s2-Enabling_Persistent_Storage.html">17.8.5. Enabling Persistent Storage</a></span></dt></dl></dd><dt><span class="section"><a href="s1-managing_log_files_in_a_graphical_environment.html">17.9. Managing Log Files in a Graphical Environment</a></span></dt><dd><dl><dt><span class="section"><a href="s1-managing_log_files_in_a_graphical_environment.html#s2-logfiles-viewing">17.9.1. Viewing Log Files</a></span></dt><dt><span class="section"><a href="s2-logfiles-adding.html">17.9.2. Adding a Log File</a></span></dt><dt><span class="section"><a href="s2-logfiles-examining.html">17.9.3. Monitoring Log Files</a></span></dt></dl></dd><dt><span class="section"><a href="s1-log-files-additional-resources.html">17.10. Additional Resources</a></span></dt></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#sect-Cron-Installing">18.1.1. Installing Cron and Anacron</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#sect-Cron-Running">18.1.2. Running the Crond Service</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-anacron-jobs">18.1.3. Configuring Anacron Jobs</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-configuring-cron-jobs">18.1.4. Configuring Cron Jobs</a></span></dt><dt><span class="section"><a href="ch-Automating_System_Tasks.html#s2-autotasks-cron-access">18.1.5. 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.6. Black and 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#sect-At_and_Batch_Installation">18.2.1. Installing At and Batch</a></span></dt><dt><span class="section"><a href="sect-Atd-Running.html">18.2.2. Running the At Service</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-configuring.html">18.2.3. Configuring an At Job</a></span></dt><dt><span class="section"><a href="s2-autotasks-batch-configuring.html">18.2.4. Configuring a Batch Job</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-viewing.html">18.2.5. Viewing Pending Jobs</a></span></dt><dt><span class="section"><a href="s2-autotasks-commandline-options.html">18.2.6. Additional Command Line Options</a></span></dt><dt><span class="section"><a href="s2-autotasks-at-batch-controlling-access.html">18.2.7. Controlling Access to At and Batch</a></span></dt></dl></dd><dt><span class="section"><a href="s1-autotasks-additional-resources.html">18.3
. Additional Resources</a></span></dt></dl></dd><dt><span class="chapter"><a href="ch-OProfile.html">19. OProfile</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OProfile.html#s1-oprofile-overview-tools">19.1. Overview of Tools</a></span></dt><dd><dl><dt><span class="section"><a href="ch-OProfile.html#s2-operf_vs_opcontrol">19.1.1. operf vs. opcontrol</a></span></dt></dl></dd><dt><span class="section"><a href="s1-using-operf.html">19.2. Using operf</a></span></dt><dd><dl><dt><span class="section"><a href="s1-using-operf.html#s2-operf-kernel">19.2.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="s2-operf-events.html">19.2.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="s2-operf-categorization.html">19.2.3. Categorization of Samples</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-configuring.html">19.3. Configuring OProfile Using Legacy Mode</a></span></dt><dd><dl><dt><span class="sec
tion"><a href="s1-oprofile-configuring.html#s2-oprofile-kernel">19.3.1. Specifying the Kernel</a></span></dt><dt><span class="section"><a href="s2-oprofile-events.html">19.3.2. Setting Events to Monitor</a></span></dt><dt><span class="section"><a href="s2-oprofile-starting-separate.html">19.3.3. Separating Kernel and User-space Profiles</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-starting.html">19.4. Starting and Stopping OProfile Using Legacy Mode</a></span></dt><dt><span class="section"><a href="s1-oprofile-saving-data.html">19.5. Saving Data in Legacy Mode</a></span></dt><dt><span class="section"><a href="s1-oprofile-analyzing-data.html">19.6. Analyzing the Data</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-analyzing-data.html#s2-oprofile-reading-opreport">19.6.1. Using <code class="command">opreport</code></a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opreport-single.html">19.6.2. Using opreport
on a Single Executable</a></span></dt><dt><span class="section"><a href="s2-oprofile-module-output.html">19.6.3. Getting More Detailed Output on the Modules</a></span></dt><dt><span class="section"><a href="s2-oprofile-reading-opannotate.html">19.6.4. Using <code class="command">opannotate</code></a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-dev-oprofile.html">19.7. Understanding the /dev/oprofile/ directory </a></span></dt><dt><span class="section"><a href="s1-oprofile-example-usage.html">19.8. Example Usage</a></span></dt><dt><span class="section"><a href="s1-oprofile-java-support.html">19.9. OProfile Support for Java</a></span></dt><dd><dl><dt><span class="section"><a href="s1-oprofile-java-support.html#s1-oprofile-java-profiling">19.9.1. Profiling Java Code</a></span></dt></dl></dd><dt><span class="section"><a href="s1-oprofile-gui.html">19.10. Graphical Interface</a></span></dt><dt><span class="section"><a href="s1-oprofile-and-systemtap.html">
19.11. OProfile and SystemTap</a></span></dt><dt><span class="section"><a href="s1-oprofile_additional_resources.html">19.12. Additional Resources</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-PTP_useful-websites.html"><strong>Prev</strong>15.11.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-System_Monitoring_Tools.html"><strong>Next</strong>Chapter 16. System Monitoring Tools</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Package_Management.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Package_Management.html
index ed62d59..707cbb2 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Package_Management.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Package_Management.html
@@ -6,6 +6,6 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="s1-users-groups-additional-resources.html" title="4.4. Additional Resources" /><link rel="next" href="ch-yum.html" title="Chapter 5. Yum" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-groups-additional-resources.html"><strong>Prev</strong></a></li><li class="next"><a access
key="n" href="ch-yum.html"><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="idm225499107424"><div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="sect-Users_and_Groups-Resources.html" title="4.4. Additional Resources" /><link rel="next" href="ch-yum.html" title="Chapter 5. Yum" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Users_and_Groups-Resources.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" hr
ef="ch-yum.html"><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="idm261714671120"><div></div><div class="para">
All software on a Fedora system is divided into RPM packages, which can be installed, upgraded, or removed. This part describes how to manage packages on Fedora using <span class="application"><strong>Yum</strong></span>.
- </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="ch-yum.html">5. Yum</a></span></dt><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_and_Updating_Packages">5.1. Checking For and Updating Packages</a></span></dt><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_Updates">5.1.1. Checking For Updates</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Updating_Packages">5.1.2. Updating Packages</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Preserving_Configuration_File_Changes">5.1.3. Preserving Configuration File Changes</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html">5.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">5.2.1. Searching Packages</a></span></dt><dt><span class="section">
<a href="sec-Listing_Packages.html">5.2.2. Listing Packages</a></span></dt><dt><span class="section"><a href="sec-Displaying_Package_Information.html">5.2.3. Displaying Package Information</a></span></dt><dt><span class="section"><a href="sec-Installing.html">5.2.4. Installing Packages</a></span></dt><dt><span class="section"><a href="sec-Removing.html">5.2.5. Removing Packages</a></span></dt><dt><span class="section"><a href="sec-Yum-Transaction_History.html">5.2.6. Working with Transaction History</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html">5.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">5.3.1. Setting [main] Options</a></span></dt><dt><span class="section"><a href="sec-Setting_repository_Options.html">5.3.2. Setting [repository] Options</a></span></dt><dt><span class="section"><a href="se
c-Using_Yum_Variables.html">5.3.3. Using Yum Variables</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Current_Configuration.html">5.3.4. Viewing the Current Configuration</a></span></dt><dt><span class="section"><a href="sec-Managing_Yum_Repositories.html">5.3.5. Adding, Enabling, and Disabling a Yum Repository</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Yum_Repository.html">5.3.6. Creating a Yum Repository</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Yum_Plugins.html">5.4. Yum Plug-ins</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">5.4.1. Enabling, Configuring, and Disabling Yum Plug-ins</a></span></dt><dt><span class="section"><a href="sec-Installing_More_Yum_Plugins.html">5.4.2. Installing Additional Yum Plug-ins</a></span></dt><dt><span class="section"><a href="sec-Plugin_Descriptions.html">5.4.3. Plug-in Descriptions</a></span></
dt></dl></dd><dt><span class="section"><a href="sec-Additional_Resources.html">5.5. 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>4.4. 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 5. Yum</a></li></ul></body></html>
\ No newline at end of file
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="ch-yum.html">5. Yum</a></span></dt><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_and_Updating_Packages">5.1. Checking For and Updating Packages</a></span></dt><dd><dl><dt><span class="section"><a href="ch-yum.html#sec-Checking_For_Updates">5.1.1. Checking For Updates</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Updating_Packages">5.1.2. Updating Packages</a></span></dt><dt><span class="section"><a href="ch-yum.html#sec-Preserving_Configuration_File_Changes">5.1.3. Preserving Configuration File Changes</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Packages_and_Package_Groups.html">5.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">5.2.1. Searching Packages</a></span></dt><dt><span class="section">
<a href="sec-Listing_Packages.html">5.2.2. Listing Packages</a></span></dt><dt><span class="section"><a href="sec-Displaying_Package_Information.html">5.2.3. Displaying Package Information</a></span></dt><dt><span class="section"><a href="sec-Installing.html">5.2.4. Installing Packages</a></span></dt><dt><span class="section"><a href="sec-Removing.html">5.2.5. Removing Packages</a></span></dt><dt><span class="section"><a href="sec-Yum-Transaction_History.html">5.2.6. Working with Transaction History</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Configuring_Yum_and_Yum_Repositories.html">5.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">5.3.1. Setting [main] Options</a></span></dt><dt><span class="section"><a href="sec-Setting_repository_Options.html">5.3.2. Setting [repository] Options</a></span></dt><dt><span class="section"><a href="se
c-Using_Yum_Variables.html">5.3.3. Using Yum Variables</a></span></dt><dt><span class="section"><a href="sec-Viewing_the_Current_Configuration.html">5.3.4. Viewing the Current Configuration</a></span></dt><dt><span class="section"><a href="sec-Managing_Yum_Repositories.html">5.3.5. Adding, Enabling, and Disabling a Yum Repository</a></span></dt><dt><span class="section"><a href="sec-Creating_a_Yum_Repository.html">5.3.6. Creating a Yum Repository</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Yum_Plugins.html">5.4. Yum Plug-ins</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Yum_Plugins.html#sec-Enabling_Configuring_and_Disabling_Yum_Plugins">5.4.1. Enabling, Configuring, and Disabling Yum Plug-ins</a></span></dt><dt><span class="section"><a href="sec-Installing_More_Yum_Plugins.html">5.4.2. Installing Additional Yum Plug-ins</a></span></dt><dt><span class="section"><a href="sec-Plugin_Descriptions.html">5.4.3. Plug-in Descriptions</a></span></
dt></dl></dd><dt><span class="section"><a href="sec-Additional_Resources.html">5.5. Additional Resources</a></span></dt></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-Users_and_Groups-Resources.html"><strong>Prev</strong>4.4. 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 5. Yum</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Servers.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Servers.html
index 4c5ac43..04217b3 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Servers.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/part-Servers.html
@@ -6,6 +6,6 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="s9-additional-sources.html" title="8.3. Additional Resources" /><link rel="next" href="ch-Web_Servers.html" title="Chapter 9. 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="s9-additional-sources.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="part" id="part-Servers"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part IV. Servers</h1></div></div></div><div class="partintro" id="idm225458493280"><div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="s9-additional-sources.html" title="8.3. Additional Resources" /><link rel="next" href="ch-Web_Servers.html" title="Chapter 9. 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="s9-additional-sources.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="part" id="part-Servers"><div class="titlepage"><div><div text-align="center"><h1 class="title">Part IV. Servers</h1></div></div></div><div class="partintro" id="idm261732223712"><div></div><div class="para">
This part discusses various topics related to servers such as how to set up a web server or share files and directories over a network.
- </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="ch-Web_Servers.html">9. Web Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Web_Servers.html#s1-The_Apache_HTTP_Server">9.1. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-changes">9.1.1. Notable Changes</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-version2-migrating">9.1.2. Updating the Configuration</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-running">9.1.3. Running the httpd Service</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-editing">9.1.4. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-dso">9.1.5. Working with Modules</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-virtu
alhosts">9.1.6. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-mod_ssl">9.1.7. Setting Up an SSL Server</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-resources">9.1.8. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Mail_Servers.html">10. Mail Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Mail_Servers.html#s1-email-protocols">10.1. Email Protocols</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Mail_Servers.html#s2-email-protocols-send">10.1.1. Mail Transport Protocols</a></span></dt><dt><span class="section"><a href="ch-Mail_Servers.html#s2-email-protocols-client">10.1.2. Mail Access Protocols</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-types.html">10.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-types.html#s2-email-types-mta
">10.2.1. Mail Transport Agent</a></span></dt><dt><span class="section"><a href="s2-email-types-mda.html">10.2.2. Mail Delivery Agent</a></span></dt><dt><span class="section"><a href="s2-email-types-mua.html">10.2.3. Mail User Agent</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mta.html">10.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mta.html#s2-email-mta-postfix">10.3.1. Postfix</a></span></dt><dt><span class="section"><a href="s2-email-mta-sendmail.html">10.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="s2-email-mta-fetchmail.html">10.3.3. Fetchmail</a></span></dt><dt><span class="section"><a href="s2-email-switchmail.html">10.3.4. Mail Transport Agent (MTA) Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mda.html">10.4. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mda.html#s2-email-procmail-configuration">10.
4.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="s2-email-procmail-recipes.html">10.4.2. Procmail Recipes</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mua.html">10.5. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mua.html#s2-email-security">10.5.1. Securing Communication</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-additional-resources.html">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-additional-resources.html#s2-email-installed-docs">10.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-email-useful-websites.html">10.6.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-email-related-books.html">10.6.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Directory_Servers.html">11. Directory Servers</a></span></dt><dd><dl><dt><
span class="section"><a href="ch-Directory_Servers.html#s1-OpenLDAP">11.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-introduction">11.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-installation">11.1.2. Installing the OpenLDAP Suite</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-configuration">11.1.3. Configuring an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-running">11.1.4. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-pam">11.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">11.1.6. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-File_and_Print_Servers
.html">12. File and Print Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s1-Samba">12.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="ch-File_and_Print_Servers.html#samba-rgs-overview">12.1.1. Introduction to Samba</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-daemons">12.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">12.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">12.1.4. Configuring a Samba Server</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-startstop">12.1.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-servers">12.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">12.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">12.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">12.1.9. Samba Network Browsing</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-cups">12.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">12.1.11. Samba Distribution Programs</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-resources">12.1.12. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="s1-FTP.html">12.2. FTP</a></span></dt><dd><dl><dt><span class="sec
tion"><a href="s1-FTP.html#s2-ftp-protocol">12.2.1. The File Transfer Protocol</a></span></dt><dt><span class="section"><a href="s2-ftp-servers.html">12.2.2. FTP Servers</a></span></dt><dt><span class="section"><a href="s3-ftp-vsftpd-conf.html">12.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-start.html">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf.html">12.2.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dt><span class="section"><a href="s2-ftp-resources.html">12.2.6. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Printer_Configuration.html">12.3. Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">12.3.1. Starting the Printer Configuration Tool</a></
span></dt><dt><span class="section"><a href="sec-Setting_Printer.html">12.3.2. Starting Printer Setup</a></span></dt><dt><span class="section"><a href="sec-Adding_Other_Printer.html">12.3.3. Adding a Local Printer</a></span></dt><dt><span class="section"><a href="s1-printing-jetdirect-printer.html">12.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="s1-printing-ipp-printer.html">12.3.5. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="sec-printing-LPDLPR-printer.html">12.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="s1-printing-smb-printer.html">12.3.7. Adding a Samba (SMB) printer</a></span></dt><dt><span class="section"><a href="s1-printing-select-model.html">12.3.8. Selecting the Printer Model and Finishing</a></span></dt><dt><span class="section"><a href="s1-printing-test-page.html">12.3.9. Printing a Test Page</a></span></dt><dt><span class="section"><a href=
"s1-printing-edit.html">12.3.10. Modifying Existing Printers</a></span></dt><dt><span class="section"><a href="s1-printing-additional-resources.html">12.3.11. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configuring_NTP_Using_the_chrony_Suite.html">13. Configuring NTP Using the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-Introduction_to_the_chrony_Suite">13.1. Introduction to the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-differences_between_ntpd_and_chronyd">13.1.1. Differences Between ntpd and chronyd</a></span></dt><dt><span class="section"><a href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-Choosing_between_NTP_daemon">13.1.2. Choosing Between NTP Daemons</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Understanding_chrony_and-its_configurat
ion.html">13.2. Understanding chrony and Its Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Understanding_chrony_and-its_configuration.html#sect-Understanding_chronyd">13.2.1. Understanding chronyd</a></span></dt><dt><span class="section"><a href="sect-Understanding_chronyc.html">13.2.2. Understanding chronyc</a></span></dt><dt><span class="section"><a href="sect-Understanding_the_chrony_configuration_commands.html">13.2.3. Understanding the chrony Configuration Commands</a></span></dt><dt><span class="section"><a href="sect-Security_with_chronyc.html">13.2.4. Security with chronyc</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Using_chrony.html">13.3. Using chrony</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Using_chrony.html#sect-Installing_chrony">13.3.1. Installing chrony</a></span></dt><dt><span class="section"><a href="sect-Checking_the_Status_of_chronyd.html">13.3.2. Checking the Status of chronyd</a></
span></dt><dt><span class="section"><a href="sect-Starting_chronyd.html">13.3.3. Starting chronyd</a></span></dt><dt><span class="section"><a href="sect-Stopping_chronyd.html">13.3.4. Stopping chronyd</a></span></dt><dt><span class="section"><a href="sect-Checking_if_chrony_is_synchronized.html">13.3.5. Checking if chrony is Synchronized</a></span></dt><dt><span class="section"><a href="sect-Manually_Adjusting-the-System_Clock.html">13.3.6. Manually Adjusting the System Clock</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Setting_up_chrony_for_different_environments.html">13.4. Setting Up chrony for Different Environments</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Setting_up_chrony_for_different_environments.html#sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">13.4.1. Setting Up chrony for a System Which is Infrequently Connected</a></span></dt><dt><span class="section"><a href="sect-Setting_up_chrony_for_a_system_in
_an_isolated_network.html">13.4.2. Setting Up chrony for a System in an Isolated Network</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Using_chronyc.html">13.5. Using chronyc</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Using_chronyc.html#sect-Using_chronyc_chronyc_to_control_chronyd">13.5.1. Using chronyc to Control chronyd</a></span></dt><dt><span class="section"><a href="sect-Using_chronyc_for_remote_administration.html">13.5.2. Using chronyc for Remote Administration</a></span></dt></dl></dd><dt><span class="section"><a href="sect-additional_resources.html">13.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sect-additional_resources.html#s2-chrony-docs-inst">13.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-chrony_Online_Documentation.html">13.6.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configuring_NTP_Using_ntpd
.html">14. Configuring NTP Using ntpd</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_NTP_Using_ntpd.html#s1-Introduction_to_NTP">14.1. Introduction to NTP</a></span></dt><dt><span class="section"><a href="s1-NTP_Strata.html">14.2. NTP Strata</a></span></dt><dt><span class="section"><a href="s1-Understanding_NTP.html">14.3. Understanding NTP</a></span></dt><dt><span class="section"><a href="s1-Understanding_the_Drift_File.html">14.4. Understanding the Drift File</a></span></dt><dt><span class="section"><a href="s1-UTC_timezones_and_DST.html">14.5. UTC, Timezones, and DST</a></span></dt><dt><span class="section"><a href="s1-Authentication_Options_for_NTP.html">14.6. Authentication Options for NTP</a></span></dt><dt><span class="section"><a href="s1-Managing_the_Time_on_Virtual_Machines.html">14.7. Managing the Time on Virtual Machines</a></span></dt><dt><span class="section"><a href="s1-Understanding_Leap_Seconds.html">14.8. Understanding Leap Seconds
</a></span></dt><dt><span class="section"><a href="s1-Understanding_the_ntpd_Configuration_File.html">14.9. Understanding the ntpd Configuration File</a></span></dt><dt><span class="section"><a href="s1-Understanding_the_ntpd_Sysconfig_File.html">14.10. Understanding the ntpd Sysconfig File</a></span></dt><dt><span class="section"><a href="s1-Disabling_chrony.html">14.11. Disabling chrony</a></span></dt><dt><span class="section"><a href="s1-Checking_if_the_NTP_Daemon_is_Installed.html">14.12. Checking if the NTP Daemon is Installed</a></span></dt><dt><span class="section"><a href="s1-Installing_the_NTP_Daemon_ntpd.html">14.13. Installing the NTP Daemon (ntpd)</a></span></dt><dt><span class="section"><a href="s1-Checking_the_status_of_NTP.html">14.14. Checking the Status of NTP</a></span></dt><dt><span class="section"><a href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html">14.15. Configure the Firewall to Allow Incoming NTP Packets</a></span></dt><dd><dl><dt><s
pan class="section"><a href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html#s2-Change_the_firewall_settings">14.15.1. Change the Firewall Settings</a></span></dt><dt><span class="section"><a href="s2-Open_Ports_in_the_firewall_for_ntp_packets.html">14.15.2. Open Ports in the Firewall for NTP Packets</a></span></dt></dl></dd><dt><span class="section"><a href="s1-Configure_ntpdate_Servers.html">14.16. Configure ntpdate Servers</a></span></dt><dt><span class="section"><a href="s1-Configure_NTP.html">14.17. Configure NTP</a></span></dt><dd><dl><dt><span class="section"><a href="s1-Configure_NTP.html#s2-Configure_Access_Control_to_an_NTP_service">14.17.1. Configure Access Control to an NTP Service</a></span></dt><dt><span class="section"><a href="s2_Configure_Rate_Limiting_Access_to_an_NTP_Service.html">14.17.2. Configure Rate Limiting Access to an NTP Service</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Peer_Address.html">14.17.3. Adding a Peer Add
ress</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Server_Address.html">14.17.4. Adding a Server Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Broadcast_or_Mutlticast_Server_Address.html">14.17.5. Adding a Broadcast or Multicast Server Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Manycast_Client_Address.html">14.17.6. Adding a Manycast Client Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Broadcastclient_Address.html">14.17.7. Adding a Broadcast Client Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_manycastserver_Address.html">14.17.8. Adding a Manycast Server Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_multicastclient_Address.html">14.17.9. Adding a Multicast Client Address</a></span></dt><dt><span class="section"><a href="s2_Configuring_the_burst_option.html">14.17.10. Configuring the Burst Option</a></span></dt><dt><span class="section">
<a href="s2_Configuring_the_iburst_Option.html">14.17.11. Configuring the iburst Option</a></span></dt><dt><span class="section"><a href="s2_Configuring_Symmetric_Authentication_Using_a_Key.html">14.17.12. Configuring Symmetric Authentication Using a Key</a></span></dt><dt><span class="section"><a href="s2_Configuring_the_Poll_Interval.html">14.17.13. Configuring the Poll Interval</a></span></dt><dt><span class="section"><a href="s2_Configuring_Server_Preference.html">14.17.14. Configuring Server Preference</a></span></dt><dt><span class="section"><a href="s2_Configuring_the_Time-To-Live_for_NTP_Packets.html">14.17.15. Configuring the Time-to-Live for NTP Packets</a></span></dt><dt><span class="section"><a href="s2_Configuring_The_Version_of_NTP_to_use.html">14.17.16. Configuring the NTP Version to Use</a></span></dt></dl></dd><dt><span class="section"><a href="s1-Configuring_the_Hardware_Clock_update.html">14.18. Configuring the Hardware Clock Update</a></span></dt><dt><spa
n class="section"><a href="s1-Configuring_Clock_Sources.html">14.19. Configuring Clock Sources</a></span></dt><dt><span class="section"><a href="s1-ntpd_additional-resources.html">14.20. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ntpd_additional-resources.html#s2-ntpd-docs-inst">14.20.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-ntpd_useful-websites.html">14.20.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configuring_PTP_Using_ptp4l.html">15. Configuring PTP Using ptp4l</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Introduction_to_PTP">15.1. Introduction to PTP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Understanding_PTP">15.1.1. Understanding PTP</a></span></dt><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Advantages_of_P
TP">15.1.2. Advantages of PTP</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_PTP.html">15.2. Using PTP</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_PTP.html#sec-Checking_for_Driver_and_Hardware_Support">15.2.1. Checking for Driver and Hardware Support</a></span></dt><dt><span class="section"><a href="sec-Installing_PTP.html">15.2.2. Installing PTP</a></span></dt><dt><span class="section"><a href="sec-Starting_ptp4l.html">15.2.3. Starting ptp4l</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Specifying_a_Configuration_File.html">15.3. Specifying a Configuration File</a></span></dt><dt><span class="section"><a href="sec-Using_the_PTP_Management_Client.html">15.4. Using the PTP Management Client</a></span></dt><dt><span class="section"><a href="sec-Synchronizing_the_Clocks.html">15.5. Synchronizing the Clocks</a></span></dt><dt><span class="section"><a href="sec-Verifying_Time_Synchronization.html">15.6. Verifying Ti
me Synchronization</a></span></dt><dt><span class="section"><a href="sec-Serving_PTP_Time_with_NTP.html">15.7. Serving PTP Time with NTP</a></span></dt><dt><span class="section"><a href="sec-Serving_NTP_Time_with_PTP.html">15.8. Serving NTP Time with PTP</a></span></dt><dt><span class="section"><a href="sec-Improving_Accuracy.html">15.9. Improving Accuracy</a></span></dt><dt><span class="section"><a href="sec-PTP_additional_resources.html">15.10. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-PTP_additional_resources.html#sec-PTP-docs-inst">15.10.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-PTP_useful-websites.html">15.10.2. Useful Websites</a></span></dt></dl></dd></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s9-additional-sources.html"><strong>Prev</strong>8.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-Web_Servers.html"><strong>Next</strong>Chapter 9. Web Servers</a></li></ul></body></html>
\ No newline at end of file
+ </div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="chapter"><a href="ch-Web_Servers.html">9. Web Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Web_Servers.html#s1-The_Apache_HTTP_Server">9.1. The Apache HTTP Server</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-changes">9.1.1. Notable Changes</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-version2-migrating">9.1.2. Updating the Configuration</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-running">9.1.3. Running the httpd Service</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-editing">9.1.4. Editing the Configuration Files</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-dso">9.1.5. Working with Modules</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-virtu
alhosts">9.1.6. Setting Up Virtual Hosts</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-mod_ssl">9.1.7. Setting Up an SSL Server</a></span></dt><dt><span class="section"><a href="ch-Web_Servers.html#s2-apache-resources">9.1.8. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Mail_Servers.html">10. Mail Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Mail_Servers.html#s1-email-protocols">10.1. Email Protocols</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Mail_Servers.html#s2-email-protocols-send">10.1.1. Mail Transport Protocols</a></span></dt><dt><span class="section"><a href="ch-Mail_Servers.html#s2-email-protocols-client">10.1.2. Mail Access Protocols</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-types.html">10.2. Email Program Classifications</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-types.html#s2-email-types-mta
">10.2.1. Mail Transport Agent</a></span></dt><dt><span class="section"><a href="s2-email-types-mda.html">10.2.2. Mail Delivery Agent</a></span></dt><dt><span class="section"><a href="s2-email-types-mua.html">10.2.3. Mail User Agent</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mta.html">10.3. Mail Transport Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mta.html#s2-email-mta-postfix">10.3.1. Postfix</a></span></dt><dt><span class="section"><a href="s2-email-mta-sendmail.html">10.3.2. Sendmail</a></span></dt><dt><span class="section"><a href="s2-email-mta-fetchmail.html">10.3.3. Fetchmail</a></span></dt><dt><span class="section"><a href="s2-email-switchmail.html">10.3.4. Mail Transport Agent (MTA) Configuration</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mda.html">10.4. Mail Delivery Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mda.html#s2-email-procmail-configuration">10.
4.1. Procmail Configuration</a></span></dt><dt><span class="section"><a href="s2-email-procmail-recipes.html">10.4.2. Procmail Recipes</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-mua.html">10.5. Mail User Agents</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-mua.html#s2-email-security">10.5.1. Securing Communication</a></span></dt></dl></dd><dt><span class="section"><a href="s1-email-additional-resources.html">10.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-email-additional-resources.html#s2-email-installed-docs">10.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-email-useful-websites.html">10.6.2. Useful Websites</a></span></dt><dt><span class="section"><a href="s2-email-related-books.html">10.6.3. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Directory_Servers.html">11. Directory Servers</a></span></dt><dd><dl><dt><
span class="section"><a href="ch-Directory_Servers.html#s1-OpenLDAP">11.1. OpenLDAP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-introduction">11.1.1. Introduction to LDAP</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-installation">11.1.2. Installing the OpenLDAP Suite</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-configuration">11.1.3. Configuring an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-selinux-openldap">11.1.4. SELinux Policy for Applications Using LDAP</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-running">11.1.5. Running an OpenLDAP Server</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s2-ldap-pam">11.1.6. Configuring a System to Authenticate Using OpenLDAP</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.
html#s2-ldap-resources">11.1.7. Additional Resources</a></span></dt><dt><span class="section"><a href="ch-Directory_Servers.html#s3-ldap-related-books">11.1.8. Related Books</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-File_and_Print_Servers.html">12. File and Print Servers</a></span></dt><dd><dl><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s1-Samba">12.1. Samba</a></span></dt><dd><dl><dt><span class="section"><a href="ch-File_and_Print_Servers.html#samba-rgs-overview">12.1.1. Introduction to Samba</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-daemons">12.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">12.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">12.1.4. Configuring a Samba Server</a></span></dt>
<dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-startstop">12.1.5. Starting and Stopping Samba</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-servers">12.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">12.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">12.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">12.1.9. Samba Network Browsing</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-cups">12.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">12.1.11. Samba Distributi
on Programs</a></span></dt><dt><span class="section"><a href="ch-File_and_Print_Servers.html#s2-samba-resources">12.1.12. Additional Resources</a></span></dt></dl></dd><dt><span class="section"><a href="s1-FTP.html">12.2. FTP</a></span></dt><dd><dl><dt><span class="section"><a href="s1-FTP.html#s2-ftp-protocol">12.2.1. The File Transfer Protocol</a></span></dt><dt><span class="section"><a href="s2-ftp-servers.html">12.2.2. FTP Servers</a></span></dt><dt><span class="section"><a href="s3-ftp-vsftpd-conf.html">12.2.3. Files Installed with <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-start.html">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </a></span></dt><dt><span class="section"><a href="s2-ftp-vsftpd-conf.html">12.2.5. <code class="command">vsftpd</code> Configuration Options</a></span></dt><dt><span class="section"><a href="s2-ftp-resources.html">12.2.6. Additional Resources</a></span></dt></dl></
dd><dt><span class="section"><a href="sec-Printer_Configuration.html">12.3. Printer Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">12.3.1. Starting the Printers Configuration Tool</a></span></dt><dt><span class="section"><a href="sec-Setting_Printer.html">12.3.2. Starting Printer Setup</a></span></dt><dt><span class="section"><a href="sec-Adding_Other_Printer.html">12.3.3. Adding a Local Printer</a></span></dt><dt><span class="section"><a href="s1-printing-jetdirect-printer.html">12.3.4. Adding an AppSocket/HP JetDirect printer</a></span></dt><dt><span class="section"><a href="s1-printing-ipp-printer.html">12.3.5. Adding an IPP Printer</a></span></dt><dt><span class="section"><a href="sec-printing-LPDLPR-printer.html">12.3.6. Adding an LPD/LPR Host or Printer</a></span></dt><dt><span class="section"><a href="s1-printing-smb-printer.html">12.3.7. Adding a Samba (SMB) printer</a></span></dt><d
t><span class="section"><a href="s1-printing-select-model.html">12.3.8. Selecting the Printer Model and Finishing</a></span></dt><dt><span class="section"><a href="s1-printing-test-page.html">12.3.9. Printing a Test Page</a></span></dt><dt><span class="section"><a href="s1-printing-edit.html">12.3.10. Modifying Existing Printers</a></span></dt><dt><span class="section"><a href="s1-printing-additional-resources.html">12.3.11. Additional Resources</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configuring_NTP_Using_the_chrony_Suite.html">13. Configuring NTP Using the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-Introduction_to_the_chrony_Suite">13.1. Introduction to the chrony Suite</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-differences_between_ntpd_and_chronyd">13.1.1. Differences Between ntpd and chronyd</a
></span></dt><dt><span class="section"><a href="ch-Configuring_NTP_Using_the_chrony_Suite.html#sect-Choosing_between_NTP_daemon">13.1.2. Choosing Between NTP Daemons</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Understanding_chrony_and-its_configuration.html">13.2. Understanding chrony and Its Configuration</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Understanding_chrony_and-its_configuration.html#sect-Understanding_chronyd">13.2.1. Understanding chronyd</a></span></dt><dt><span class="section"><a href="sect-Understanding_chronyc.html">13.2.2. Understanding chronyc</a></span></dt><dt><span class="section"><a href="sect-Understanding_the_chrony_configuration_commands.html">13.2.3. Understanding the chrony Configuration Commands</a></span></dt><dt><span class="section"><a href="sect-Security_with_chronyc.html">13.2.4. Security with chronyc</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Using_chrony.html">13.3. Using chro
ny</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Using_chrony.html#sect-Installing_chrony">13.3.1. Installing chrony</a></span></dt><dt><span class="section"><a href="sect-Checking_the_Status_of_chronyd.html">13.3.2. Checking the Status of chronyd</a></span></dt><dt><span class="section"><a href="sect-Starting_chronyd.html">13.3.3. Starting chronyd</a></span></dt><dt><span class="section"><a href="sect-Stopping_chronyd.html">13.3.4. Stopping chronyd</a></span></dt><dt><span class="section"><a href="sect-Checking_if_chrony_is_synchronized.html">13.3.5. Checking if chrony is Synchronized</a></span></dt><dt><span class="section"><a href="sect-Manually_Adjusting-the-System_Clock.html">13.3.6. Manually Adjusting the System Clock</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Setting_up_chrony_for_different_environments.html">13.4. Setting Up chrony for Different Environments</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Setting_
up_chrony_for_different_environments.html#sect-Setting_up_chrony_for_a_system_which_is_infrequently_connected">13.4.1. Setting Up chrony for a System Which is Infrequently Connected</a></span></dt><dt><span class="section"><a href="sect-Setting_up_chrony_for_a_system_in_an_isolated_network.html">13.4.2. Setting Up chrony for a System in an Isolated Network</a></span></dt></dl></dd><dt><span class="section"><a href="sect-Using_chronyc.html">13.5. Using chronyc</a></span></dt><dd><dl><dt><span class="section"><a href="sect-Using_chronyc.html#sect-Using_chronyc_chronyc_to_control_chronyd">13.5.1. Using chronyc to Control chronyd</a></span></dt><dt><span class="section"><a href="sect-Using_chronyc_for_remote_administration.html">13.5.2. Using chronyc for Remote Administration</a></span></dt></dl></dd><dt><span class="section"><a href="sect-additional_resources.html">13.6. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sect-additional_resources.htm
l#s2-chrony-docs-inst">13.6.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-chrony_Online_Documentation.html">13.6.2. Online Documentation</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configuring_NTP_Using_ntpd.html">14. Configuring NTP Using ntpd</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_NTP_Using_ntpd.html#s1-Introduction_to_NTP">14.1. Introduction to NTP</a></span></dt><dt><span class="section"><a href="s1-NTP_Strata.html">14.2. NTP Strata</a></span></dt><dt><span class="section"><a href="s1-Understanding_NTP.html">14.3. Understanding NTP</a></span></dt><dt><span class="section"><a href="s1-Understanding_the_Drift_File.html">14.4. Understanding the Drift File</a></span></dt><dt><span class="section"><a href="s1-UTC_timezones_and_DST.html">14.5. UTC, Timezones, and DST</a></span></dt><dt><span class="section"><a href="s1-Authentication_Options_for_NTP.html">14.6. Authentication Optio
ns for NTP</a></span></dt><dt><span class="section"><a href="s1-Managing_the_Time_on_Virtual_Machines.html">14.7. Managing the Time on Virtual Machines</a></span></dt><dt><span class="section"><a href="s1-Understanding_Leap_Seconds.html">14.8. Understanding Leap Seconds</a></span></dt><dt><span class="section"><a href="s1-Understanding_the_ntpd_Configuration_File.html">14.9. Understanding the ntpd Configuration File</a></span></dt><dt><span class="section"><a href="s1-Understanding_the_ntpd_Sysconfig_File.html">14.10. Understanding the ntpd Sysconfig File</a></span></dt><dt><span class="section"><a href="s1-Disabling_chrony.html">14.11. Disabling chrony</a></span></dt><dt><span class="section"><a href="s1-Checking_if_the_NTP_Daemon_is_Installed.html">14.12. Checking if the NTP Daemon is Installed</a></span></dt><dt><span class="section"><a href="s1-Installing_the_NTP_Daemon_ntpd.html">14.13. Installing the NTP Daemon (ntpd)</a></span></dt><dt><span class="section"><a href="s
1-Checking_the_status_of_NTP.html">14.14. Checking the Status of NTP</a></span></dt><dt><span class="section"><a href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html">14.15. Configure the Firewall to Allow Incoming NTP Packets</a></span></dt><dd><dl><dt><span class="section"><a href="s1-Configure_the_Firewall_to_Allow_Incoming_NTP_Packets.html#s2-Change_the_firewall_settings">14.15.1. Change the Firewall Settings</a></span></dt><dt><span class="section"><a href="s2-Open_Ports_in_the_firewall_for_ntp_packets.html">14.15.2. Open Ports in the Firewall for NTP Packets</a></span></dt></dl></dd><dt><span class="section"><a href="s1-Configure_ntpdate_Servers.html">14.16. Configure ntpdate Servers</a></span></dt><dt><span class="section"><a href="s1-Configure_NTP.html">14.17. Configure NTP</a></span></dt><dd><dl><dt><span class="section"><a href="s1-Configure_NTP.html#s2-Configure_Access_Control_to_an_NTP_service">14.17.1. Configure Access Control to an NTP Service</a>
</span></dt><dt><span class="section"><a href="s2_Configure_Rate_Limiting_Access_to_an_NTP_Service.html">14.17.2. Configure Rate Limiting Access to an NTP Service</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Peer_Address.html">14.17.3. Adding a Peer Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Server_Address.html">14.17.4. Adding a Server Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Broadcast_or_Mutlticast_Server_Address.html">14.17.5. Adding a Broadcast or Multicast Server Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Manycast_Client_Address.html">14.17.6. Adding a Manycast Client Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_Broadcastclient_Address.html">14.17.7. Adding a Broadcast Client Address</a></span></dt><dt><span class="section"><a href="s2_Adding_a_manycastserver_Address.html">14.17.8. Adding a Manycast Server Address</a></span></dt><dt><span class="s
ection"><a href="s2_Adding_a_multicastclient_Address.html">14.17.9. Adding a Multicast Client Address</a></span></dt><dt><span class="section"><a href="s2_Configuring_the_burst_option.html">14.17.10. Configuring the Burst Option</a></span></dt><dt><span class="section"><a href="s2_Configuring_the_iburst_Option.html">14.17.11. Configuring the iburst Option</a></span></dt><dt><span class="section"><a href="s2_Configuring_Symmetric_Authentication_Using_a_Key.html">14.17.12. Configuring Symmetric Authentication Using a Key</a></span></dt><dt><span class="section"><a href="s2_Configuring_the_Poll_Interval.html">14.17.13. Configuring the Poll Interval</a></span></dt><dt><span class="section"><a href="s2_Configuring_Server_Preference.html">14.17.14. Configuring Server Preference</a></span></dt><dt><span class="section"><a href="s2_Configuring_the_Time-To-Live_for_NTP_Packets.html">14.17.15. Configuring the Time-to-Live for NTP Packets</a></span></dt><dt><span class="section"><a hre
f="s2_Configuring_The_Version_of_NTP_to_use.html">14.17.16. Configuring the NTP Version to Use</a></span></dt></dl></dd><dt><span class="section"><a href="s1-Configuring_the_Hardware_Clock_update.html">14.18. Configuring the Hardware Clock Update</a></span></dt><dt><span class="section"><a href="s1-Configuring_Clock_Sources.html">14.19. Configuring Clock Sources</a></span></dt><dt><span class="section"><a href="s1-ntpd_additional-resources.html">14.20. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="s1-ntpd_additional-resources.html#s2-ntpd-docs-inst">14.20.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="s2-ntpd_useful-websites.html">14.20.2. Useful Websites</a></span></dt></dl></dd></dl></dd><dt><span class="chapter"><a href="ch-Configuring_PTP_Using_ptp4l.html">15. Configuring PTP Using ptp4l</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Introduction_to_PTP">15.1
. Introduction to PTP</a></span></dt><dd><dl><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Understanding_PTP">15.1.1. Understanding PTP</a></span></dt><dt><span class="section"><a href="ch-Configuring_PTP_Using_ptp4l.html#sec-Advantages_of_PTP">15.1.2. Advantages of PTP</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Using_PTP.html">15.2. Using PTP</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Using_PTP.html#sec-Checking_for_Driver_and_Hardware_Support">15.2.1. Checking for Driver and Hardware Support</a></span></dt><dt><span class="section"><a href="sec-Installing_PTP.html">15.2.2. Installing PTP</a></span></dt><dt><span class="section"><a href="sec-Starting_ptp4l.html">15.2.3. Starting ptp4l</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Specifying_a_Configuration_File.html">15.3. Specifying a Configuration File</a></span></dt><dt><span class="section"><a href="sec-Using_the_PTP_Management_Client
.html">15.4. Using the PTP Management Client</a></span></dt><dt><span class="section"><a href="sec-Synchronizing_the_Clocks.html">15.5. Synchronizing the Clocks</a></span></dt><dt><span class="section"><a href="sec-Verifying_Time_Synchronization.html">15.6. Verifying Time Synchronization</a></span></dt><dt><span class="section"><a href="sec-Serving_PTP_Time_with_NTP.html">15.7. Serving PTP Time with NTP</a></span></dt><dt><span class="section"><a href="sec-Serving_NTP_Time_with_PTP.html">15.8. Serving NTP Time with PTP</a></span></dt><dt><span class="section"><a href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html">15.9. Synchronize to PTP or NTP Time Using timemaster</a></span></dt><dd><dl><dt><span class="section"><a href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html#sec-Starting_timemaster_as_a_Service">15.9.1. Starting timemaster as a Service</a></span></dt><dt><span class="section"><a href="sec-Understanding_the_timemaster_Configuration_File.html">
15.9.2. Understanding the timemaster Configuration File</a></span></dt><dt><span class="section"><a href="sec-Configuring_timemaster_Options.html">15.9.3. Configuring timemaster Options</a></span></dt></dl></dd><dt><span class="section"><a href="sec-Improving_Accuracy.html">15.10. Improving Accuracy</a></span></dt><dt><span class="section"><a href="sec-PTP_additional_resources.html">15.11. Additional Resources</a></span></dt><dd><dl><dt><span class="section"><a href="sec-PTP_additional_resources.html#sec-PTP-docs-inst">15.11.1. Installed Documentation</a></span></dt><dt><span class="section"><a href="sec-PTP_useful-websites.html">15.11.2. Useful Websites</a></span></dt></dl></dd></dl></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s9-additional-sources.html"><strong>Prev</strong>8.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-Web_Servers.html"><strong>Next</strong>Chapter 9. Web Servers</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01.html
index b90306f..8a0cc0b 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="index.html" title="System Administrator's 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="idm225450683136" lang="en-US"><div class="titlepage"><div><div><h1 id="idm225450683136" class="title">Preface</h1></div></div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="index.html" title="System Administrator's Guide" /><link rel="prev" href="index.html" title="System Administrator's 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="idm261732560432" lang="en-US"><div class="titlepage"><div><div><h1 id="idm261732560432" class="title">Preface</h1></div></div></div><div class="para">
The <em class="citetitle">System Administrator's Guide</em> contains information on how to customize the Fedora 21 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:
@@ -17,5 +17,5 @@
</div></li><li class="listitem"><div class="para">
Working with kernel modules and upgrading the kernel
</div></li></ul></div><div class="section" id="sect-Preface-Target_Audience"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">1. Target Audience</h2></div></div></div><div class="para">
- The <em class="citetitle">System Administrator's Guide</em> assumes you have a basic understanding of the Fedora operating system. If you need help with the installation of this system, refer to the <a href="http://docs.fedoraproject.org/install-guide">Fedora 21 Installation Guide</a>.
+ The <em class="citetitle">System Administrator's Guide</em> assumes you have a basic understanding of the Fedora operating system. If you need help with the installation of this system, refer to the <a href="http://docs.fedoraproject.org/install-guide">Fedora Installation Guide</a>.
</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="index.html"><strong>Prev</strong>System Administrator's 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>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s03.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s03.html
index e90cd8b..838904d 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s03.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s03.html
@@ -6,11 +6,11 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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="pr01s
03s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="idm225480655296" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm225480655296">3. Document Conventions</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's 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="pr01s
03s02.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="idm261745107024" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm261745107024">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" id="idm225504134496"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225504134496">3.1. Typographic Conventions</h3></div></div></div><div class="para">
+ </div><div class="section" id="idm261755936352"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm261755936352">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>
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s03s02.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s03s02.html
index 52c1264..aad4354 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s03s02.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s03s02.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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</stron
g></a></li></ul><div class="section" id="idm225450097808"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225450097808">3.2. Pull-quote Conventions</h3></div></div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's 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</stron
g></a></li></ul><div class="section" id="idm261752729376"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm261752729376">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:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s03s03.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s03s03.html
index ebd043b..20684ad 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s03s03.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s03s03.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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="pr01s04.html" title="4. We Need Feedback!" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s03s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pr01s04.html"><strong>Next</stro
ng></a></li></ul><div class="section" id="idm225478720960"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm225478720960">3.3. Notes and Warnings</h3></div></div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's 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="pr01s04.html" title="4. We Need Feedback!" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="pr01s03s02.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="pr01s04.html"><strong>Next</stro
ng></a></li></ul><div class="section" id="idm261748224288"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title" id="idm261748224288">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.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s04.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s04.html
index dc94df5..cd605e0 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s04.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/pr01s04.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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</stro
ng></a></li></ul><div xml:lang="en-US" class="section" id="idm225435536800" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm225435536800">4. We Need Feedback!</h2></div></div></div><a id="idm225435535808" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's 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</stro
ng></a></li></ul><div xml:lang="en-US" class="section" id="idm261784091424" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title" id="idm261784091424">4. We Need Feedback!</h2></div></div></div><a id="idm261784090432" class="indexterm"></a><div class="para">
If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: <a href="https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora Documentation&component=system-administrator's-guide">https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora Documentation&component=system-administrator's-guide</a>
</div><div class="para">
If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-Changing_the_Keyboard_Layout.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-Changing_the_Keyboard_Layout.html
index 00e86cd..d56fc0d 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-Changing_the_Keyboard_Layout.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-Changing_the_Keyboard_Layout.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-System_Locale_and_Keyboard_Configuration.html" title="Chapter 2. System Locale and Keyboard Configuration" /><link rel="prev" href="ch-System_Locale_and_Keyboard_Configuration.html" title="Chapter 2. System Locale and Keyboard Configuration" /><link rel="next" href="s2-Listing_Available_Keymaps.html" title="2.2.2. Listing Available Keymaps" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li cla
ss="previous"><a accesskey="p" href="ch-System_Locale_and_Keyboard_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-Listing_Available_Keymaps.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-Changing_the_Keyboard_Layout"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Changing the Keyboard Layout</h2></div></div></div><a id="idm225464431920" class="indexterm"></a><a id="idm225464430320" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-System_Locale_and_Keyboard_Configuration.html" title="Chapter 2. System Locale and Keyboard Configuration" /><link rel="prev" href="ch-System_Locale_and_Keyboard_Configuration.html" title="Chapter 2. System Locale and Keyboard Configuration" /><link rel="next" href="s2-Listing_Available_Keymaps.html" title="2.2.2. Listing Available Keymaps" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li cla
ss="previous"><a accesskey="p" href="ch-System_Locale_and_Keyboard_Configuration.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-Listing_Available_Keymaps.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-Changing_the_Keyboard_Layout"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.2. Changing the Keyboard Layout</h2></div></div></div><a id="idm261733284112" class="indexterm"></a><a id="idm261733282512" class="indexterm"></a><div class="para">
The keyboard layout settings enable the user to control the layout used on the text console and graphical user interfaces.
</div><div class="section" id="s2-Displaying_the_Current_Settings"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">2.2.1. Displaying the Current Settings</h3></div></div></div><div class="para">
As mentioned before, you can check your current keyboard layout configuration with the following command:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-Configuring_the_Hardware_Clock_update.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-Configuring_the_Hardware_Clock_update.html
index 5fb91e5..db5cf60 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-Configuring_the_Hardware_Clock_update.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-Configuring_the_Hardware_Clock_update.html
@@ -15,5 +15,5 @@
<pre class="screen">~]# <code class="command">hwclock --systohc</code></pre>
</div><div class="para">
- When the system clock is being synchronized by <code class="systemitem">ntpd</code>, the kernel will in turn update the RTC every 11 minutes automatically.
+ When the system clock is being synchronized by <code class="systemitem">ntpd</code> or <code class="systemitem">chronyd</code>, the kernel will in turn update the RTC every 11 minutes automatically.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2_Configuring_The_Version_of_NTP_to_use.html"><strong>Prev</strong>14.17.16. Configuring the NTP Version to Use</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-Configuring_Clock_Sources.html"><strong>Next</strong>14.19. Configuring Clock Sources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-FTP.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-FTP.html
index d365e23..bbfe8fe 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-FTP.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-FTP.html
@@ -6,13 +6,13 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-File_and_Print_Servers.html" title="Chapter 12. File and Print Servers" /><link rel="prev" href="ch-File_and_Print_Servers.html" title="Chapter 12. File and Print Servers" /><link rel="next" href="s2-ftp-servers.html" title="12.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></l
i><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">12.2. FTP</h2></div></div></div><a id="idm225455350960" class="indexterm"></a><a id="idm225461768576" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-File_and_Print_Servers.html" title="Chapter 12. File and Print Servers" /><link rel="prev" href="ch-File_and_Print_Servers.html" title="Chapter 12. File and Print Servers" /><link rel="next" href="s2-ftp-servers.html" title="12.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></l
i><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">12.2. FTP</h2></div></div></div><a id="idm261739791840" class="indexterm"></a><a id="idm261723591952" 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">12.2.1. The File Transfer Protocol</h3></div></div></div><a id="idm225477696560" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-ftp-protocol"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.2.1. The File Transfer Protocol</h3></div></div></div><a id="idm261761203056" 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">12.2.1.1. Multiple Ports, Multiple Modes</h4></div></div></div><a id="idm225463196272" class="indexterm"></a><a id="idm225439180768" class="indexterm"></a><a id="idm225452594256" class="indexterm"></a><a id="idm225469006800" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-ftp-protocol-multiport"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.1.1. Multiple Ports, Multiple Modes</h4></div></div></div><a id="idm261734673136" class="indexterm"></a><a id="idm261751959760" class="indexterm"></a><a id="idm261751810304" class="indexterm"></a><a id="idm261744375936" 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:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-Using_the_Journal.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-Using_the_Journal.html
new file mode 100644
index 0000000..b1b30fc
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-Using_the_Journal.html
@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.8. Using the Journal</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's 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-debugging_rsyslog.html" title="17.7. Debugging Rsyslog" /><link rel="next" href="s2-Access_Control.html" title="17.8.2. Access Control" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-debugging_rsyslog.html"><strong>Prev</strong></a></l
i><li class="next"><a accesskey="n" href="s2-Access_Control.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-Using_the_Journal"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.8. Using the Journal</h2></div></div></div><div class="para">
+ The Journal is a component of <span class="application"><strong>systemd</strong></span> that is responsible for viewing and management of log files. It can be used in parallel, or in place of a traditional syslog daemon, such as <code class="systemitem">rsyslogd</code>. The Journal was developed to address problems connected with traditional logging. It is closely integrated with the rest of the system, supports various logging technologies and access management for the log files.
+ </div><div class="para">
+ Logging data is collected, stored, and processed by the Journal's <code class="systemitem">journald</code> service. It creates and maintains binary files called <span class="emphasis"><em>journals</em></span> based on logging information that is received from the kernel, from user processes, from standard output, and standard error output of system services or via its native API. These journals are structured and indexed, which provides relatively fast seek times. Journal entries can carry a unique identifier. The <code class="systemitem">journald</code> service collects numerous meta data fields for each log message. The actual journal files are secured, and therefore cannot be manually edited.
+ </div><div class="section" id="s2-Viewing_Log_Files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.8.1. Viewing Log Files</h3></div></div></div><div class="para">
+ To access the journal logs, use the <span class="application"><strong>journalctl</strong></span> tool. For a basic view of the logs type as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code class="command">journalctl</code></pre><div class="para">
+ An output of this command is a list of all log files generated on the system including messages generated by system components and by users. The structure of this output is similar to one used in <code class="filename">/var/log/messages/</code> but with certain improvements:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ the priority of entries is marked visually. Lines of error priority and higher are highlighted with red color and a bold font is used for lines with notice and warning priority
+ </div></li><li class="listitem"><div class="para">
+ the time stamps are converted for the local time zone of your system
+ </div></li><li class="listitem"><div class="para">
+ all logged data is shown, including rotated logs
+ </div></li><li class="listitem"><div class="para">
+ the beginning of a boot is tagged with a special line
+ </div></li></ul></div><div class="example" id="ex-Example_Output_of_journalctl"><h6>Example 17.15. Example Output of journalctl</h6><div class="example-contents"><div class="para">
+ The following is an example output provided by the <span class="application"><strong>journalctl</strong></span> tool. When called without parameters, the listed entries begin with a time stamp, then the host name and application that performed the operation is mentioned followed by the actual message. This example shows the first three entries in the journal log:
+ </div><pre class="screen">
+# <code class="command">journalctl</code>
+-- Logs begin at Thu 2013-08-01 15:42:12 CEST, end at Thu 2013-08-01 15:48:48 CEST. --
+Aug 01 15:42:12 localhost systemd-journal[54]: Allowing runtime journal files to grow to 49.7M.
+Aug 01 15:42:12 localhost kernel: Initializing cgroup subsys cpuset
+Aug 01 15:42:12 localhost kernel: Initializing cgroup subsys cpu
+
+[...]
+</pre></div></div><br class="example-break" /><div class="para">
+ In many cases, only the latest entries in the journal log are relevant. The simplest way to reduce <code class="command">journalctl</code> output is to use the <code class="option">-n</code> option that lists only the specified number of most recent log entries:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-n</code> <em class="replaceable"><code>Number</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>Number</code></em> with the number of lines to be shown. When no number is specified, <code class="command">journalctl</code> displays the ten most recent entries.
+ </div><div class="para">
+ The <code class="command">journalctl</code> command allows controlling the form of the output with the following syntax:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-o</code> <em class="replaceable"><code>form</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>form</code></em> with a keyword specifying a desired form of output. There are several options, such as <code class="option">verbose</code>, which returns full-structured entry items with all fields, <code class="option">export</code>, which creates a binary stream suitable for backups and network transfer, and <code class="option">json</code>, which formats entries as JSON data structures. For the full list of keywords, see the <code class="filename">journalctl(1)</code> manual page.
+ </div><div class="example" id="ex-verbose_journalctl_output"><h6>Example 17.16. Verbose journalctl Output</h6><div class="example-contents"><div class="para">
+ To view full meta data about all entries, type:
+ </div><pre class="screen">
+# <code class="command">journalctl</code> <code class="option">-o verbose</code>
+[...]
+
+Fri 2013-08-02 14:41:22 CEST [s=e1021ca1b81e4fc688fad6a3ea21d35b;i=55c;b=78c81449c920439da57da7bd5c56a770;m=27cc
+ _BOOT_ID=78c81449c920439da57da7bd5c56a770
+ PRIORITY=5
+ SYSLOG_FACILITY=3
+ _TRANSPORT=syslog
+ _MACHINE_ID=69d27b356a94476da859461d3a3bc6fd
+ _HOSTNAME=localhost.localdomain
+ _PID=562
+ _COMM=dbus-daemon
+ _EXE=/usr/bin/dbus-daemon
+ _CMDLINE=/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
+ _SYSTEMD_CGROUP=/system/dbus.service
+ _SYSTEMD_UNIT=dbus.service
+ SYSLOG_IDENTIFIER=dbus
+ SYSLOG_PID=562
+ _UID=81
+ _GID=81
+ _SELINUX_CONTEXT=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023
+ MESSAGE=[system] Successfully activated service 'net.reactivated.Fprint'
+ _SOURCE_REALTIME_TIMESTAMP=1375447282839181
+
+[...]
+</pre><div class="para">
+ This example lists fields that identify a single log entry. These meta data can be used for message filtering as shown in <a class="xref" href="s2-Filtering_Messages.html#advanced_filtering">the section called “Advanced Filtering”</a>. For a complete description of all possible fields see the <code class="filename">systemd.journal-fields(7)</code> manual page.
+ </div></div></div><br class="example-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-debugging_rsyslog.html"><strong>Prev</strong>17.7. Debugging Rsyslog</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-Access_Control.html"><strong>Next</strong>17.8.2. Access Control</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-autotasks-additional-resources.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-autotasks-additional-resources.html
index 66c41fd..28ce202 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-autotasks-additional-resources.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-autotasks-additional-resources.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Automating_System_Tasks.html" title="Chapter 18. Automating System Tasks" /><link rel="prev" href="s2-autotasks-at-batch-controlling-access.html" title="18.2.7. Controlling Access to At and Batch" /><link rel="next" href="ch-OProfile.html" title="Chapter 19. OProfile" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-autotasks-at-batch-controlling-acc
ess.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-OProfile.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">18.3. Additional Resources</h2></div></div></div><a id="idm225477240352" class="indexterm"></a><a id="idm225472242784" class="indexterm"></a><a id="idm225472241344" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Automating_System_Tasks.html" title="Chapter 18. Automating System Tasks" /><link rel="prev" href="s2-autotasks-at-batch-controlling-access.html" title="18.2.7. Controlling Access to At and Batch" /><link rel="next" href="ch-OProfile.html" title="Chapter 19. OProfile" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-autotasks-at-batch-controlling-acc
ess.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-OProfile.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">18.3. Additional Resources</h2></div></div></div><a id="idm261729418736" class="indexterm"></a><a id="idm261729417296" class="indexterm"></a><a id="idm261753795136" class="indexterm"></a><div class="para">
To learn more about configuring automated tasks, see the following installed documentation:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="filename">cron(8)</code> man page contains an overview of cron.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-autotasks-at-batch.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-autotasks-at-batch.html
index a19e183..263f9d1 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-autotasks-at-batch.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-autotasks-at-batch.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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="sect-Atd-Running.html" title="18.2.2. Running the At Service" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Automating_System_Tasks.html"><strong>Pr
ev</strong></a></li><li class="next"><a accesskey="n" href="sect-Atd-Running.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">18.2. At and Batch</h2></div></div></div><a id="idm225469950144" class="indexterm"></a><a id="idm225469948704" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's 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="sect-Atd-Running.html" title="18.2.2. Running the At Service" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Automating_System_Tasks.html"><strong>Pr
ev</strong></a></li><li class="next"><a accesskey="n" href="sect-Atd-Running.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">18.2. At and Batch</h2></div></div></div><a id="idm261783585504" class="indexterm"></a><a id="idm261783584064" class="indexterm"></a><div class="para">
While Cron is used to schedule recurring tasks, the <span class="application"><strong>At</strong></span> utility is used to schedule a one-time task at a specific time and the <span class="application"><strong>Batch</strong></span> utility is used to schedule a one-time task to be executed when the system load average drops below 0.8.
</div><div class="section" id="sect-At_and_Batch_Installation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">18.2.1. Installing At and Batch</h3></div></div></div><div class="para">
To determine if the <span class="package">at</span> package is already installed on your system, issue the following command:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-basic_configuration_of_rsyslog.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-basic_configuration_of_rsyslog.html
new file mode 100644
index 0000000..782c5d0
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-basic_configuration_of_rsyslog.html
@@ -0,0 +1,117 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2. Basic Configuration of Rsyslog</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's 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="s2-Actions.html" title="17.2.2. Actions" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Viewing_and_Managing_Log_Files.ht
ml"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-Actions.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-basic_configuration_of_rsyslog"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.2. Basic Configuration of Rsyslog</h2></div></div></div><div class="para">
+ The main configuration file for <span class="application"><strong>rsyslog</strong></span> is <code class="filename">/etc/rsyslog.conf</code>. Here, you can specify <em class="firstterm">global directives</em>, <em class="firstterm">modules</em>, and <em class="firstterm">rules</em> that consist of <em class="firstterm">filter</em> and <em class="firstterm">action</em> parts. Also, you can add comments in the form of text following a hash sign (<code class="literal">#</code>).
+ </div><div class="section" id="s2-Filters"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.1. Filters</h3></div></div></div><div class="para">
+ A rule is specified by a <span class="emphasis"><em>filter</em></span> part, which selects a subset of syslog messages, and an <span class="emphasis"><em>action</em></span> part, which specifies what to do with the selected messages. To define a rule in your <code class="filename">/etc/rsyslog.conf</code> configuration file, define both, a filter and an action, on one line and separate them with one or more spaces or tabs.
+ </div><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> offers various ways to filter syslog messages according to selected properties. The available filtering methods can be divided into <span class="emphasis"><em>Facility/Priority-based</em></span>, <span class="emphasis"><em>Property-based</em></span>, and <span class="emphasis"><em>Expression-based</em></span> filters.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">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> separated by a dot. To create a selector, use the following syntax:
+ </div><pre class="screen">
+<em class="replaceable"><code>FACILITY</code></em>.<em class="replaceable"><code>PRIORITY</code></em>
+</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="replaceable"><code>FACILITY</code></em> specifies the subsystem that produces a specific syslog message. For example, the <code class="command">mail</code> subsystem handles all mail-related syslog messages. <em class="replaceable"><code>FACILITY</code></em> can be represented by one of the following keywords (or by a numerical code): <code class="command">kern</code> (0), <code class="command">user</code> (1), <code class="command">mail</code> (2), <code class="command">daemon</code> (3), <code class="command">auth</code> (4), <code class="command">syslog</code> (5), <code class="command">lpr</code> (6), <code class="command">news</code> (7), <code class="command">uucp</code> (8), <code class="command">cron</code> (9), <code class="command">authpriv</code> (10), <code class="command">ftp</code> (11), <code class="command">ntp</code> (12), <code class="command">logaudit</code> (13), <code class="command">logalert</code> (14), <code class="command">clock</
code> (15), and <code class="command">local0</code> through <code class="command">local7</code> (16 - 23).
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code>PRIORITY</code></em> specifies a priority of a syslog message. <em class="replaceable"><code>PRIORITY</code></em> can be represented by one of the following keywords (or by a number): <code class="command">debug</code> (7), <code class="command">info</code> (6), <code class="command">notice</code> (5), <code class="command">warning</code> (4), <code class="command">err</code> (3), <code class="command">crit</code> (2), <code class="command">alert</code> (1), and <code class="command">emerg</code> (0).
+ </div><div class="para">
+ The aforementioned syntax selects syslog messages with the defined or <span class="emphasis"><em>higher</em></span> priority. By preceding any priority keyword with an equal sign (<code class="literal">=</code>), you specify that only syslog messages with the specified priority will be selected. All other priorities will be ignored. Conversely, preceding a priority keyword with an exclamation mark (<code class="literal">!</code>) selects all syslog messages except those with the defined priority.
+ </div></li></ul></div><div class="para">
+ In addition to the keywords specified above, you may also use an asterisk (<code class="literal">*</code>) to define all facilities or priorities (depending on where you place the asterisk, before or after the comma). Specifying the priority keyword <code class="literal">none</code> serves for facilities with no given priorities. Both facility and priority conditions are case-insensitive.
+ </div><div class="para">
+ To define multiple facilities and priorities, separate them with a comma (<code class="literal">,</code>). To define multiple selectors on one line, separate them with a semi-colon (<code class="literal">;</code>). Note that each selector in the selector field is capable of overwriting the preceding ones, which can exclude some priorities from the pattern.
+ </div><div class="example" id="ex-facility_priority-based_filters"><h6>Example 17.1. Facility/Priority-based Filters</h6><div class="example-contents"><div class="para">
+ The following are a few examples of simple facility/priority-based filters that can be specified in <code class="filename">/etc/rsyslog.conf</code>. To select all kernel syslog messages with any priority, add the following text into the configuration file:
+ </div><pre class="screen">
+kern.*
+</pre><div class="para">
+ To select all mail syslog messages with priority <code class="command">crit</code> and higher, use this form:
+ </div><pre class="screen">
+mail.crit
+</pre><div class="para">
+ To select all cron syslog messages except those with the <code class="command">info</code> or <code class="command">debug</code> priority, set the configuration in the following form:
+ </div><pre class="screen">
+cron.!info,!debug
+</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">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, see <a class="xref" href="s2-Templates.html#brid-properties">the section called “Properties”</a>. You can compare each of the specified properties to a particular value using one of the compare-operations listed in <a class="xref" href="s1-basic_configuration_of_rsyslog.html#table-compare-operations">Table 17.1, “Property-based compare-operations”</a>. Both property names and compare operations are case-sensitive.
+ </div><div class="para">
+ Property-based filter must start with a colon (<code class="literal">:</code>). To define the filter, use the following syntax:
+ </div><pre class="screen">:<em class="replaceable"><code>PROPERTY</code></em>, [!]<em class="replaceable"><code>COMPARE_OPERATION</code></em>, "<em class="replaceable"><code>STRING</code></em>"</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>PROPERTY</code></em> attribute specifies the desired property.
+ </div></li><li class="listitem"><div class="para">
+ The optional exclamation point (<code class="literal">!</code>) negates the output of the compare-operation. Other Boolean operators are currently not supported in property-based filters.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>COMPARE_OPERATION</code></em> attribute specifies one of the compare-operations listed in <a class="xref" href="s1-basic_configuration_of_rsyslog.html#table-compare-operations">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. This value must be enclosed in quotation marks. To escape certain character inside the string (for example a quotation mark (<code class="literal">"</code>)), use the backslash character (<code class="literal">\</code>).
+ </div></li></ul></div><div class="table" id="table-compare-operations"><h6>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 class="">
+ Compare-operation
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <em class="parameter"><code>contains</code></em>
+ </td><td class="">
+ Checks whether the provided string matches any part of the text provided by the property. To perform case-insensitive comparisons, use <em class="parameter"><code>contains_i</code></em>.
+ </td></tr><tr><td class="">
+ <em class="parameter"><code>isequal</code></em>
+ </td><td class="">
+ Compares the provided string against all of the text provided by the property. These two values must be exactly equal to match.
+ </td></tr><tr><td class="">
+ <em class="parameter"><code>startswith</code></em>
+ </td><td class="">
+ Checks whether the provided string is found exactly at the beginning of the text provided by the property. To perform case-insensitive comparisons, use <em class="parameter"><code>startswith_i</code></em>.
+ </td></tr><tr><td class="">
+ <em class="parameter"><code>regex</code></em>
+ </td><td class="">
+ Compares the provided POSIX BRE (Basic Regular Expression) against the text provided by the property.
+ </td></tr><tr><td class="">
+ <em class="parameter"><code>ereregex</code></em>
+ </td><td class="">
+ Compares the provided POSIX ERE (Extended Regular Expression) regular expression against the text provided by the property.
+ </td></tr><tr><td class="">
+ <em class="parameter"><code>isempty</code></em>
+ </td><td class="">
+ Checks if the property is empty. The value is discarded. This is especially useful when working with normalized data, where some fields may be populated based on normalization result.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="example" id="ex-property-based_filters"><h6>Example 17.2. Property-based Filters</h6><div class="example-contents"><div class="para">
+ The following are a few examples of property-based filters that can be specified in <code class="filename">/etc/rsyslog.conf</code>. To select syslog messages which contain the string <code class="literal">error</code> in their message text, use:
+ </div><pre class="screen">:msg, contains, "error"</pre><div class="para">
+ The following filter selects syslog messages received from the host name <code class="literal">host1</code>:
+ </div><pre class="screen">:hostname, isequal, "host1"</pre><div class="para">
+ To select syslog messages which do not contain any mention of the words <code class="literal">fatal</code> and <code class="literal">error</code> with any or no text between them (for example, <code class="literal">fatal lib error</code>), type:
+ </div><pre class="screen">:msg, !regex, "fatal .* error"</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">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 called <span class="emphasis"><em>RainerScript</em></span> to build complex filters. See <a class="xref" href="s1-log-files-additional-resources.html#brid-Log_Files-Resources-Online">the section called “Online Documentation”</a> for the syntax definition of this script along with examples of various expression-based filters. Also RainerScript is a basis for <span class="application"><strong>rsyslog</strong></span>'s new configuration format, see <a class="xref" href="s2-using_the_new_configuration_format.html">Section 17.2.6, “Using the New Configuration Format”</a>
+ </div><div class="para">
+ The basic syntax of expression-based filter looks as follows:
+ </div><pre class="screen">
+if <em class="replaceable"><code>EXPRESSION</code></em> then <em class="replaceable"><code>ACTION</code></em> else <em class="replaceable"><code>ACTION</code></em>
+</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>EXPRESSION</code></em> attribute represents an expression to be evaluated, for example: <code class="literal">$msg startswith 'DEVNAME'</code> or <code class="literal">$syslogfacility-text == 'local0'</code>. You can specify more than one expression in a single filter by using <code class="function">and</code> and <code class="function">or</code> operators.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>action</code></em> attribute represents an action to be performed if the expression returns the value <code class="literal">true</code>. this can be a single action, or an arbitrary complex script enclosed in curly braces.
+ </div></li><li class="listitem"><div class="para">
+ Expression-based filters are indicated by the keyword <span class="emphasis"><em>if</em></span> at the start of a new line. the <span class="emphasis"><em>then</em></span> keyword separates the <em class="replaceable"><code>expression</code></em> from the <em class="replaceable"><code>action</code></em>. optionally, you can employ the <span class="emphasis"><em>else</em></span> keyword to specify what action is to be performed in case the condition is not met.
+ </div></li></ul></div><div class="para">
+ With expression-based filters, you can nest the conditions by using a script enclosed in curly braces as in <a class="xref" href="s1-basic_configuration_of_rsyslog.html#ex-expression-based_filters">Example 17.3, “Expression-based Filters”</a>. the script allows you to use <span class="emphasis"><em>facility/priority-based</em></span> filters inside the expression. on the other hand, <span class="emphasis"><em>property-based</em></span> filters are not recommended here. RainerScript supports regular expressions with specialized functions <code class="function">re_match()</code> and <code class="function">re_extract()</code>.
+ </div><div class="example" id="ex-expression-based_filters"><h6>Example 17.3. Expression-based Filters</h6><div class="example-contents"><div class="para">
+ The following expression contains two nested conditions. The log files created by a program called <span class="emphasis"><em>prog1</em></span> are split into two files based on the presence of the "test" string in the message.
+ </div><pre class="screen">
+if $programname == 'prog1' then {
+ action(type="omfile" file="/var/log/prog1.log")
+ if $msg contains 'test' then
+ action(type="omfile" file="/var/log/prog1test.log")
+ else
+ action(type="omfile" file="/var/log/prog1notest.log")
+}
+</pre></div></div><br class="example-break" /></dd></dl></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Viewing_and_Managing_Log_Files.html"><strong>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="s2-Actions.html"><strong>Next</strong>17.2.2. Actions</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-check-rpm-sig.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-check-rpm-sig.html
index e4b84a2..0e02fdf 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-check-rpm-sig.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-check-rpm-sig.html
@@ -1,29 +1,25 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.3. 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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.3.2. Checking Package Signatures</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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-chec
king.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-check-rpm-sig"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.3. Checking a Package's Signature</h2></div></div></div><a id="idm225448621664" class="indexterm"></a><div class="para">
- To verify that a package has not been corrupted or tampered with, examine the checksum by typing the following command at a 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">
- If the message <code class="computeroutput"><em class="replaceable"><code><rpm_file></code></em>: sha1 md5 OK</code> (specifically the <code class="computeroutput">OK</code> part of it) is displayed, 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="idm225475254896" class="indexterm"></a><a id="idm225475253456" class="indexterm"></a><a id="idm225475252048" 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">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>
\ No newline at end of file
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-find-verify-rpm.html" title="A.3. Finding and Verifying RPM Packages" /><link rel="prev" href="s1-find-verify-rpm.html" title="A.3. Finding and Verifying RPM Packages" /><link rel="next" href="s1-rpm-usage-examples.html" title="A.4. Common Examples of RPM Usage" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-find-verify-rpm.html"><strong>Prev</strong
></a></li><li class="next"><a accesskey="n" href="s1-rpm-usage-examples.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-check-rpm-sig"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">A.3.2. Checking Package Signatures</h3></div></div></div><a id="idm261722159248" class="indexterm"></a><a id="idm261722157808" class="indexterm"></a><a id="idm261722156400" class="indexterm"></a><div class="para">
+ <span class="application"><strong>RPM</strong></span> packages can be signed using <span class="application"><strong>GNU Privacy Guard</strong></span> (or <span class="application"><strong>GPG</strong></span>), which helps you make certain that downloaded packages are trustworthy. <span class="application"><strong>GPG</strong></span> is a tool for secure communication. With <span class="application"><strong>GPG</strong></span>, you can authenticate the validity of documents and encrypt or decrypt data.
+ </div><div class="para">
+ To verify that a package has not been corrupted or tampered with, check its <span class="application"><strong>GPG</strong></span> signature by using the <code class="command">rpmkeys</code> command with the <code class="option">-K</code> (or <code class="option">--checksig</code>) option:
+ </div><pre class="synopsis"><code class="command">rpmkeys -K <em class="replaceable"><code>package.rpm</code></em></code></pre><div class="para">
+ Note that the <span class="application"><strong>Yum</strong></span> package manager performs automatic checking of <span class="application"><strong>GPG</strong></span> signatures during installations and upgrades.
+ </div><div class="para">
+ <span class="application"><strong>GPG</strong></span> is installed by default, as well as a set of Red Hat keys for verifying packages. To import additional keys for use with <span class="application"><strong>RPM</strong></span>, see <a class="xref" href="s1-check-rpm-sig.html#s2-keys-importing">Section A.3.2.1, “Importing GPG Keys”</a>.
+ </div><div class="section" id="s2-keys-importing"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">A.3.2.1. Importing GPG Keys</h4></div></div></div><div class="para">
+ To verify Red Hat packages, a Red Hat <span class="application"><strong>GPG</strong></span> key needs to be installed. A set of basic keys is installed by default. To view a list of installed keys, execute the following command at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">rpm -qa gpg-pubkey*</code></pre><div class="para">
+ To display details about a specific key, use <code class="command">rpm -qi</code> followed by the output from the previous command. For example:
+ </div><pre class="screen">~]$ <code class="command">rpm -qi gpg-pubkey-fd431d51-4ae0493b</code></pre><div class="para">
+ Use the <code class="command">rpmkeys</code> command with the <code class="option">--import</code> option to install a new key for use with <span class="application"><strong>RPM</strong></span>. The default location for storing <span class="application"><strong>RPM</strong></span> <acronym class="acronym">GPG</acronym> keys is the <code class="filename">/etc/pki/rpm-gpg/</code> directory. To import new keys, use a command like the following as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">rpmkeys --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release</code></pre><div class="para">
+ See the <a href="https://access.redhat.com/security/team/key/">Product Signing (GPG) Keys</a> article on the Red Hat Customer Portal for additional information about Red Hat package-signing practices.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-find-verify-rpm.html"><strong>Prev</strong>A.3. Finding and Verifying RPM 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-usage-examples.html"><strong>Next</strong>A.4. Common Examples of RPM Usage</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-debugging_rsyslog.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-debugging_rsyslog.html
new file mode 100644
index 0000000..af73b0f
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-debugging_rsyslog.html
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.7. Debugging Rsyslog</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Viewing_and_Managing_Log_Files.html" title="Chapter 17. Viewing and Managing Log Files" /><link rel="prev" href="s2-storing_messages_in_the_mongodb.html" title="17.6.4. Storing Messages in the MongoDB" /><link rel="next" href="s1-Using_the_Journal.html" title="17.8. Using the Journal" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-storing_messages_i
n_the_mongodb.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-Using_the_Journal.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-debugging_rsyslog"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.7. Debugging Rsyslog</h2></div></div></div><div class="para">
+ To run <code class="systemitem">rsyslogd</code> in debugging mode, use the following command:
+ </div><pre class="synopsis"><code class="systemitem">rsyslogd</code> <code class="option">-dn</code></pre><div class="para">
+ With this command, <code class="systemitem">rsyslogd</code> produces debugging information and prints it to the standard output. The <code class="option">-n</code> stands for "no fork". You can modify debugging with environmental variables, for example, you can store the debug output in a log file. Before starting <code class="systemitem">rsyslogd</code>, type the following on the command line:
+ </div><pre class="screen">
+export RSYSLOG_DEBUGLOG="<em class="replaceable"><code>path</code></em>"
+export RSYSLOG_DEBUG="Debug"
+</pre><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a desired location for the file where the debugging information will be logged. For a complete list of options available for the RSYSLOG_DEBUG variable, see the related section in the <code class="filename">rsyslogd(8)</code> manual page.
+ </div><div class="para">
+ To check if syntax used in the <code class="filename">etc/rsyslog.conf</code> file is valid use:
+ </div><pre class="synopsis"><code class="systemitem">rsyslogd</code> <code class="option">-N</code> <code class="literal">1</code></pre><div class="para">
+ Where <code class="literal">1</code> represents level of verbosity of the output message. This is a forward compatibility option because currently, only one level is provided. However, you must add this argument to run the validation.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-storing_messages_in_the_mongodb.html"><strong>Prev</strong>17.6.4. Storing Messages in the MongoDB</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-Using_the_Journal.html"><strong>Next</strong>17.8. Using the Journal</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-additional-resources.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-additional-resources.html
index f093398..bda2442 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-additional-resources.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-additional-resources.html
@@ -6,9 +6,9 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Mail_Servers.html" title="Chapter 10. Mail Servers" /><link rel="prev" href="s1-email-mua.html" title="10.5. Mail User Agents" /><link rel="next" href="s2-email-useful-websites.html" title="10.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">10.6. Additional Resources</h2></div></div></div><a id="idm225447473232" class="indexterm"></a><a id="idm225447471792" class="indexterm"></a><a id="idm225447470352" class="indexterm"></a><a id="idm225463359104" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Mail_Servers.html" title="Chapter 10. Mail Servers" /><link rel="prev" href="s1-email-mua.html" title="10.5. Mail User Agents" /><link rel="next" href="s2-email-useful-websites.html" title="10.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">10.6. Additional Resources</h2></div></div></div><a id="idm261741205088" class="indexterm"></a><a id="idm261741203648" class="indexterm"></a><a id="idm261741202208" class="indexterm"></a><a id="idm261741200768" 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">10.6.1. Installed Documentation</h3></div></div></div><a id="idm225463356048" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><div class="section" id="s2-email-installed-docs"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.6.1. Installed Documentation</h3></div></div></div><a id="idm261724274800" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
Information on configuring Sendmail is included with the <span class="package">sendmail</span> and <span class="package">sendmail-cf</span> packages.
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="filename">/usr/share/sendmail-cf/README</code> — Contains information on the <code class="command">m4</code> macro processor, file locations for Sendmail, supported mailers, how to access enhanced features, and more.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-mda.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-mda.html
index 246c8e3..3516d0a 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-mda.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-mda.html
@@ -10,7 +10,7 @@
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="idm225482190352" class="indexterm"></a><a id="idm225482188912" class="indexterm"></a><div class="para">
+ </div><a id="idm261722549200" class="indexterm"></a><a id="idm261718334528" 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.
@@ -20,7 +20,7 @@
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">10.4.1. Procmail Configuration</h3></div></div></div><a id="idm225447849440" class="indexterm"></a><a id="idm225447848000" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-email-procmail-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.4.1. Procmail Configuration</h3></div></div></div><a id="idm261779827024" class="indexterm"></a><a id="idm261717807712" 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:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-mta.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-mta.html
index aef8790..9d51856 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-mta.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-mta.html
@@ -14,7 +14,7 @@
Similarly, to disable the service, type the following at a shell prompt:
</div><pre class="screen">~]# <code class="command">systemctl disable <em class="replaceable"><code>service</code></em></code></pre><div class="para">
For more information on how to manage system services in Fedora 21, see <a class="xref" href="ch-Services_and_Daemons.html">Chapter 6, <em>Services and Daemons</em></a>.
- </div><div class="section" id="s2-email-mta-postfix"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.1. Postfix</h3></div></div></div><a id="idm225481308304" class="indexterm"></a><a id="idm225481306864" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-email-mta-postfix"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.3.1. Postfix</h3></div></div></div><a id="idm261756326768" class="indexterm"></a><a id="idm261724472048" 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 changed root environment to limit the effects of attacks.
@@ -22,7 +22,7 @@
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">10.3.1.1. The Default Postfix Installation</h4></div></div></div><a id="idm225448518928" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-email-mta-postfix-default"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.1.1. The Default Postfix Installation</h4></div></div></div><a id="idm261724466624" class="indexterm"></a><div class="para">
The Postfix executable is <code class="filename">postfix</code>. This daemon launches all related processes needed to handle mail delivery.
</div><div class="para">
Postfix stores its configuration files in the <code class="filename">/etc/postfix/</code> directory. The following is a list of the more commonly used files:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-mua.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-mua.html
index 50a95e5..6900dfa 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-mua.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-mua.html
@@ -12,28 +12,28 @@
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">10.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 <span class="application"><strong>Mutt</strong></span> offer SSL-encrypted email sessions.
- </div><a id="idm225474474576" class="indexterm"></a><div class="para">
+ </div><a id="idm261746538752" class="indexterm"></a><div class="para">
Like any other service that flows over a network unencrypted, important email information, such as user names, passwords, and entire messages, may be intercepted and viewed by users on the network. Additionally, since the standard <code class="systemitem">POP</code> and <code class="systemitem">IMAP</code> protocols pass authentication information unencrypted, it is possible for an attacker to gain access to user accounts by collecting user names and passwords as they are passed over the network.
- </div><div class="section" id="s3-email-security-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.5.1.1. Secure Email Clients</h4></div></div></div><a id="idm225474469616" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-email-security-clients"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.5.1.1. Secure Email Clients</h4></div></div></div><a id="idm261748673408" 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">10.5.1.2. Securing Email Client Communications</h4></div></div></div><a id="idm225463816112" class="indexterm"></a><a id="idm225455052400" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-security-servers"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.5.1.2. Securing Email Client Communications</h4></div></div></div><a id="idm261748666528" class="indexterm"></a><a id="idm261745832576" 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.
+ Self-signed certificates should be used for testing purposes only. Any server used in a production environment should use an SSL certificate signed by a CA.
</div></div></div><div class="para">
- To create a self-signed SSL certificate for <code class="systemitem">IMAP</code> or <code class="systemitem">POP</code>, change to the <code class="filename">/etc/pki/dovecot/</code> directory, edit the certificate parameters in the <code class="filename">/etc/pki/dovecot/dovecot-openssl.conf</code> configuration file as you prefer, and type the following commands, as <code class="systemitem">root</code>:
+ To create a self-signed SSL certificate for <code class="systemitem">IMAP</code> or <code class="systemitem">POP</code>, change to the <code class="filename">/etc/pki/dovecot/</code> directory, edit the certificate parameters in the <code class="filename">/etc/pki/dovecot/dovecot-openssl.cnf</code> configuration file as you prefer, and type the following commands, as <code class="systemitem">root</code>:
</div><pre class="screen">dovecot]# <code class="command">rm -f certs/dovecot.pem private/dovecot.pem</code>
dovecot]# <code class="command">/usr/libexec/dovecot/mkcert.sh</code></pre><div class="para">
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">
Issue the following command to restart the <code class="command">dovecot</code> daemon:
- </div><pre class="screen">~]# <code class="command">systemctl restart dovecot</code></pre><div class="para">
- Alternatively, the <code class="command">stunnel</code> command can be used as an SSL encryption wrapper around the standard, non-secure connections to <code class="systemitem">IMAP</code> or <code class="systemitem">POP</code> services.
+ </div><pre class="screen">~]# <code class="command">systemctl restart dovecot</code></pre><div class="para">
+ Alternatively, the <code class="command">stunnel</code> command can be used as an encryption wrapper around the standard, non-secure connections to <code class="systemitem">IMAP</code> or <code class="systemitem">POP</code> services.
</div><div class="para">
The <code class="command">stunnel</code> utility uses external OpenSSL libraries included with Fedora to provide strong cryptography and to protect the network connections. It is recommended to apply to a CA to obtain an SSL certificate, but it is also possible to create a self-signed certificate.
</div><div class="note"><div class="admonition_header"><h2>Installing the stunnel package</h2></div><div class="admonition"><div class="para">
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-types.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-types.html
index d1633d5..5bc9575 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-types.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-email-types.html
@@ -6,9 +6,9 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Mail_Servers.html" title="Chapter 10. Mail Servers" /><link rel="prev" href="ch-Mail_Servers.html" title="Chapter 10. Mail Servers" /><link rel="next" href="s2-email-types-mda.html" title="10.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" hr
ef="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">10.2. Email Program Classifications</h2></div></div></div><a id="idm225458082960" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Mail_Servers.html" title="Chapter 10. Mail Servers" /><link rel="prev" href="ch-Mail_Servers.html" title="Chapter 10. Mail Servers" /><link rel="next" href="s2-email-types-mda.html" title="10.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" hr
ef="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">10.2. Email Program Classifications</h2></div></div></div><a id="idm261746246704" 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">10.2.1. Mail Transport Agent</h3></div></div></div><a id="idm225458079520" class="indexterm"></a><a id="idm225479737264" class="indexterm"></a><a id="idm225479735824" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-email-types-mta"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">10.2.1. Mail Transport Agent</h3></div></div></div><a id="idm261746243264" class="indexterm"></a><a id="idm261746241344" class="indexterm"></a><a id="idm261786124912" 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.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-find-verify-rpm.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-find-verify-rpm.html
new file mode 100644
index 0000000..beb7c7d
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-find-verify-rpm.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.3. Finding and Verifying RPM Packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-RPM.html" title="Appendix A. RPM" /><link rel="prev" href="s2-rpm-verifying.html" title="A.2.5. Verifying Packages" /><link rel="next" href="s1-check-rpm-sig.html" title="A.3.2. Checking Package Signatures" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-verifying.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-chec
k-rpm-sig.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-find-verify-rpm"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.3. Finding and Verifying RPM Packages</h2></div></div></div><a id="idm261721202880" class="indexterm"></a><div class="para">
+ Before using any <span class="application"><strong>RPM</strong></span> packages, you must know where to find them and be able to verify if you can trust them.
+ </div><div class="section" id="s2-rpm-finding"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">A.3.1. Finding RPM Packages</h3></div></div></div><a id="idm261721199488" class="indexterm"></a><a id="idm261721198080" class="indexterm"></a><div class="para">
+ Although there are many <span class="application"><strong>RPM</strong></span> repositories on the Internet, for security and compatibility reasons, you should consider installing only official Fedora-provided RPM packages. The following is a list of sources for <span class="application"><strong>RPM</strong></span> packages:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a id="idm261721194128" class="indexterm"></a>
+ <a id="idm261721192720" class="indexterm"></a>
+ Official Fedora installation media.
+ </div></li><li class="listitem"><div class="para">
+ <a id="idm261722168224" class="indexterm"></a>
+ <a id="idm261722166816" class="indexterm"></a>
+ Official <span class="application"><strong>RPM</strong></span> repositories provided with the <span class="application"><strong>Yum</strong></span> package manager. See <a class="xref" href="ch-yum.html">Chapter 5, <em>Yum</em></a> for details on how to use the official Fedora package repositories.
+ </div></li><li class="listitem"><div class="para">
+ Unofficial, third-party repositories not affiliated with The Fedora Project also provide RPM packages.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When considering third-party repositories for use with your Fedora system, pay close attention to the repository's web site with regard to package compatibility before adding the repository as a package source. Alternate package repositories may offer different, incompatible versions of the same software, including packages already included in the Fedora repositories.
+ </div></div></div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-verifying.html"><strong>Prev</strong>A.2.5. Verifying 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-check-rpm-sig.html"><strong>Next</strong>A.3.2. Checking Package Signatures</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-interaction_of_rsyslog_and_journal.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-interaction_of_rsyslog_and_journal.html
new file mode 100644
index 0000000..beb336b
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-interaction_of_rsyslog_and_journal.html
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.5. Interaction of Rsyslog and Journal</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Viewing_and_Managing_Log_Files.html" title="Chapter 17. Viewing and Managing Log Files" /><link rel="prev" href="s2-using_RELP.html" title="17.4.4. Using RELP" /><link rel="next" href="s1-structured_logging_with_rsyslog.html" title="17.6. Structured Logging with Rsyslog" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-using_RELP.html"><strong>Prev</s
trong></a></li><li class="next"><a accesskey="n" href="s1-structured_logging_with_rsyslog.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-interaction_of_rsyslog_and_journal"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.5. Interaction of Rsyslog and Journal</h2></div></div></div><div class="para">
+ As mentioned above, <span class="application"><strong>Rsyslog</strong></span> and <span class="application"><strong>Journal</strong></span>, the two logging applications present on your system, have several distinctive features that make them suitable for specific use cases. In many situations it is useful to combine their capabilities, for example to create structured messages and store them in a file database (see <a class="xref" href="s1-structured_logging_with_rsyslog.html">Section 17.6, “Structured Logging with Rsyslog”</a>). A communication interface needed for this cooperation is provided by input and output modules on the side of <span class="application"><strong>Rsyslog</strong></span> and by the <span class="application"><strong>Journal</strong></span>'s communication socket.
+ </div><div class="para">
+ By default, <code class="systemitem">rsyslogd</code> uses the <code class="systemitem">imjournal</code> module as a default input mode for journal files. With this module, you import not only the messages but also the structured data provided by <code class="systemitem">journald</code>. Also, older data can be imported from <code class="systemitem">journald</code> (unless forbidden with the <code class="option">$ImjournalIgnorePreviousMessages</code> directive). See <a class="xref" href="s1-structured_logging_with_rsyslog.html#s2-importing_data_from_journal">Section 17.6.1, “Importing Data from Journal”</a> for basic configuration of <code class="systemitem">imjournal</code>.
+ </div><div class="para">
+ As an alternative, configure <code class="systemitem">rsyslogd</code> to read from the socket provided by <code class="systemitem">journal</code> as an output for syslog-based applications. The path to the socket is <code class="filename">/run/systemd/journal/syslog</code>. Use this option when you want to maintain plain rsyslog messages. Compared to <code class="systemitem">imjournal</code> the socket input currently offers more features, such as ruleset binding or filtering. To import <span class="application"><strong>Journal</strong></span> data trough the socket, use the following configuration in <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imuxsock
+$OmitLocalLogging off
+</pre><div class="para">
+ The above syntax loads the <code class="systemitem">imuxsock</code> module and turns off the <code class="option">$OmitLocalLogging</code> directive, which enables the import trough the system socket. The path to this socket is specified separately in <code class="filename">/etc/rsyslog.d/listen.conf</code> as follows:
+ </div><pre class="screen">
+$SystemLogSocketName /run/systemd/journal/syslog
+</pre><div class="para">
+ You can also output messages from <span class="application"><strong>Rsyslog</strong></span> to <span class="application"><strong>Journal</strong></span> with the <code class="systemitem">omjournal</code> module. Configure the output in <code class="filename">/etc/rsyslog.conf</code> as follows:
+ </div><pre class="screen">
+$ModLoad omjournal
+
+*.* :omjournal:
+</pre><div class="para">
+ For instance, the following configuration forwards all received messages on tcp port 10514 to the Journal:
+ </div><pre class="screen">
+$ModLoad imtcp
+$ModLoad omjournal
+
+$RuleSet remote
+*.* :omjournal:
+
+$InputTCPServerBindRuleset remote
+$InputTCPServerRun 10514
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-using_RELP.html"><strong>Prev</strong>17.4.4. Using RELP</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-structured_logging_with_rsyslog.html"><strong>Next</strong>17.6. Structured Logging with Rsyslog</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-boot-loader.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-boot-loader.html
index 282d59a..b861932 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-boot-loader.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-boot-loader.html
@@ -1,18 +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.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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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 access
key="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">20.6. Verifying the Boot Loader</h2></div></div></div><a id="idm225468297760" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 21. Manually Upgrading the Kernel" /><link rel="prev" href="sec-Verifying_the_Initial_RAM_Disk_Image.html" title="21.5. Verifying the Initial RAM Disk Image" /><link rel="next" href="s2-kernel-boot-loader-iseries.html" title="21.6.2. Configuring the OS/400 Boot Loader" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a access
key="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">21.6. Verifying the Boot Loader</h2></div></div></div><a id="idm261752592992" class="indexterm"></a><div class="para">
When you install a kernel using <code class="command">rpm</code>, the kernel package creates an entry in the boot loader configuration file for that new kernel. However, <code class="command">rpm</code> does <span class="emphasis"><em>not</em></span> configure the new kernel to boot as the default kernel. You must do this manually when installing a new kernel with <code class="command">rpm</code>.
</div><div class="para">
It is always recommended to double-check the boot loader configuration file after installing a new kernel with <code class="command">rpm</code> to ensure that the configuration is correct. Otherwise, the system might not be able to boot into Fedora properly. If this happens, boot the system with the boot media created earlier and re-configure the boot loader.
</div><div class="para">
In the following table, find your system's architecture to determine the boot loader it uses, and then click on the "See" link to jump to the correct instructions for your system.
- </div><div class="table" id="tb-grub-arch-loaders"><h6>Table 20.1. Boot loaders by architecture</h6><div class="table-contents"><table summary="Boot loaders by architecture" border="1"><colgroup><col width="25%" class="architecture" /><col width="25%" class="bootloader" /><col width="50%" class="refer-to" /></colgroup><thead><tr><th class="">
+ </div><div class="table" id="tb-grub-arch-loaders"><h6>Table 21.1. Boot loaders by architecture</h6><div class="table-contents"><table summary="Boot loaders by architecture" border="1"><colgroup><col width="25%" class="architecture" /><col width="25%" class="bootloader" /><col width="50%" class="refer-to" /></colgroup><thead><tr><th class="">
Architecture
</th><th class="">
Boot Loader
@@ -23,36 +23,36 @@
</td><td class="">
GRUB 2
</td><td class="">
- <a class="xref" href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">Section 20.6.1, “Configuring the GRUB 2 Boot Loader”</a>
+ <a class="xref" href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">Section 21.6.1, “Configuring the GRUB 2 Boot Loader”</a>
</td></tr><tr><td class="">
AMD AMD64 <span class="emphasis"><em>or</em></span> Intel 64
</td><td class="">
GRUB 2
</td><td class="">
- <a class="xref" href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">Section 20.6.1, “Configuring the GRUB 2 Boot Loader”</a>
+ <a class="xref" href="s1-kernel-boot-loader.html#s3-kernel-boot-loader-grub">Section 21.6.1, “Configuring the GRUB 2 Boot Loader”</a>
</td></tr><tr><td class="">
IBM eServer System i
</td><td class="">
OS/400
</td><td class="">
- <a class="xref" href="s2-kernel-boot-loader-iseries.html">Section 20.6.2, “Configuring the OS/400 Boot Loader”</a>
+ <a class="xref" href="s2-kernel-boot-loader-iseries.html">Section 21.6.2, “Configuring the OS/400 Boot Loader”</a>
</td></tr><tr><td class="">
IBM eServer System p
</td><td class="">
YABOOT
</td><td class="">
- <a class="xref" href="s2-kernel-boot-loader-pseries.html">Section 20.6.3, “Configuring the YABOOT Boot Loader”</a>
+ <a class="xref" href="s2-kernel-boot-loader-pseries.html">Section 21.6.3, “Configuring the YABOOT Boot Loader”</a>
</td></tr><tr><td class="">
IBM System z
</td><td class="">
z/IPL
</td><td class="">
—
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="s3-kernel-boot-loader-grub"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.6.1. Configuring the GRUB 2 Boot Loader</h3></div></div></div><a id="idm225481637600" class="indexterm"></a><a id="idm225481636160" class="indexterm"></a><div class="para">
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="s3-kernel-boot-loader-grub"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">21.6.1. Configuring the GRUB 2 Boot Loader</h3></div></div></div><a id="idm261734185344" class="indexterm"></a><a id="idm261734183904" class="indexterm"></a><div class="para">
Fedora 21 is distributed with GRUB 2, which reads its configuration from the <code class="filename">/boot/grub2/grub.cfg</code> file. This file is generated by the <span class="application"><strong>grub2-mkconfig</strong></span> utility based on Linux kernels located in the <code class="filename">/boot</code> directory, template files located in <code class="filename">/etc/grub.d/</code>, and custom settings in the <code class="filename">/etc/default/grub</code> file and is automatically updated each time you install a new kernel from an RPM package. To update this configuration file manually, type the following at a shell prompt as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">grub2-mkconfig</code> <code class="option">-o</code> <code class="option">/boot/grub2/grub.cfg</code></pre><div class="para">
- Among various code snippets and directives, the <code class="filename">/boot/grub2/grub.cfg</code> configuration file contains one or more <code class="literal">menuentry</code> blocks, each representing a single GRUB 2 boot menu entry. These blocks always start with the <code class="literal">menuentry</code> keyword followed by a title, list of options, and opening curly bracket, and end with a closing curly bracket. Anything between the opening and closing bracket should be indented. For example, the following is a sample <code class="literal">menuentry</code> block for Fedora 17 with Linux kernel 3.4.0-1.fc17.x86_64:
- </div><pre class="programlisting">menuentry 'Fedora (3.4.0-1.fc17.x86_64)' --class fedora --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-77ba9149-751a-48e0-974f-ad94911734b9' {
+ Among various code snippets and directives, the <code class="filename">/boot/grub2/grub.cfg</code> configuration file contains one or more <code class="literal">menuentry</code> blocks, each representing a single GRUB 2 boot menu entry. These blocks always start with the <code class="literal">menuentry</code> keyword followed by a title, list of options, and opening curly bracket, and end with a closing curly bracket. Anything between the opening and closing bracket should be indented. For example, the following is a sample <code class="literal">menuentry</code> block for Fedora 21 with Linux kernel 3.17.6-300.fc21.x86_64:
+ </div><pre class="programlisting">menuentry 'Fedora (3.17.6-300.fc21.x86_64) 21 (Twenty One)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-3.17.4-301.fc21.x86_64-advanced-effee860-8d55-4e4a-995e-b4c88f9ac9f0' {
load_video
set gfxpayload=keep
insmod gzio
@@ -60,24 +60,22 @@
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
- search --no-floppy --fs-uuid --set=root --hint='hd0,msdos1' 4ea24c68-ab10-47d4-8a6b-b8d3a002acba
+ search --no-floppy --fs-uuid --set=root --hint='hd0,msdos1' f19c92f4-9ead-4207-b46a-723b7a2c51c8
else
- search --no-floppy --fs-uuid --set=root 4ea24c68-ab10-47d4-8a6b-b8d3a002acba
+ search --no-floppy --fs-uuid --set=root f19c92f4-9ead-4207-b46a-723b7a2c51c8
fi
- echo 'Loading Fedora (3.4.0-1.fc17.x86_64)'
- linux /vmlinuz-3.4.0-1.fc17.x86_64 root=/dev/mapper/vg_fedora-lv_root ro rd.md=0 rd.dm=0 SYSFONT=True rd.lvm.lv=vg_fedora/lv_swap KEYTABLE=us rd.lvm.lv=vg_fedora/lv_root rd.luks=0 LANG=en_US.UTF-8 rhgb quiet
- echo 'Loading initial ramdisk ...'
- initrd /initramfs-3.4.0-1.fc17.x86_64.img
+ linux16 /vmlinuz-3.17.6-300.fc21.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8
+ initrd16 /initramfs-3.17.6-300.fc21.x86_64.img
}</pre><div class="para">
- Each <code class="literal">menuentry</code> block that represents an installed Linux kernel contains <code class="literal">linux</code> and <code class="literal">initrd</code> directives followed by the path to the kernel and the <code class="systemitem">initramfs</code> image respectively. If a separate <code class="filename">/boot</code> partition was created, the paths to the kernel and the <code class="systemitem">initramfs</code> image are relative to <code class="filename">/boot</code>. In the example above, the <code class="literal">initrd /initramfs-3.4.0-1.fc17.x86_64.img</code> line means that the <code class="systemitem">initramfs</code> image is actually located at <code class="filename">/boot/initramfs-3.4.0-1.fc17.x86_64.img</code> when the root file system is mounted, and likewise for the kernel path.
+ Each <code class="literal">menuentry</code> block that represents an installed Linux kernel contains <code class="literal">linux</code> and <code class="literal">initrd</code> directives followed by the path to the kernel and the <code class="systemitem">initramfs</code> image respectively. If a separate <code class="filename">/boot</code> partition was created, the paths to the kernel and the <code class="systemitem">initramfs</code> image are relative to <code class="filename">/boot</code>. In the example above, the <code class="literal">initrd16 /initramfs-3.17.6-300.fc21.x86_64.img</code> line means that the <code class="systemitem">initramfs</code> image is actually located at <code class="filename">/boot/initramfs-3.17.6-300.fc21.x86_64.img</code> when the root file system is mounted, and likewise for the kernel path.
</div><div class="para">
- The kernel version number as given on the <code class="literal">linux /vmlinuz-<em class="replaceable"><code>kernel_version</code></em></code> line must match the version number of the <code class="systemitem">initramfs</code> image given on the <code class="literal">initrd /initramfs-<em class="replaceable"><code>kernel_version</code></em>.img</code> line of each <code class="literal">menuentry</code> block. For more information on how to verify the initial RAM disk image, refer to <a class="xref" href="sec-Verifying_the_Initial_RAM_Disk_Image.html#procedure-Verifying_the_Initial_RAM_Disk_Image">Procedure 20.1, “Verifying the Initial RAM Disk Image”</a>.
+ The kernel version number as given on the <code class="literal">linux /vmlinuz-<em class="replaceable"><code>kernel_version</code></em></code> line must match the version number of the <code class="systemitem">initramfs</code> image given on the <code class="literal">initrd /initramfs-<em class="replaceable"><code>kernel_version</code></em>.img</code> line of each <code class="literal">menuentry</code> block. For more information on how to verify the initial RAM disk image, refer to <a class="xref" href="sec-Verifying_the_Initial_RAM_Disk_Image.html#procedure-Verifying_the_Initial_RAM_Disk_Image">Procedure 21.1, “Verifying the Initial RAM Disk Image”</a>.
</div><div class="note" id="note-The_initrd_directive_in_grub.cfg_refers_to_an_initramfs_image"><div class="admonition_header"><h2>The initrd directive in grub.cfg refers to an initramfs image</h2></div><div class="admonition"><div class="para">
In <code class="literal">menuentry</code> blocks, the <code class="computeroutput">initrd</code> directive must point to the location (relative to the <code class="filename">/boot</code> directory if it is on a separate partition) of the <code class="filename">initramfs</code> file corresponding to the same kernel version. This directive is called <code class="literal">initrd</code> because the previous tool which created initial RAM disk images, <code class="command">mkinitrd</code>, created what were known as <code class="systemitem">initrd</code> files. The <code class="filename">grub.cfg</code> directive remains <code class="systemitem">initrd</code> to maintain compatibility with other tools. The file-naming convention of systems using the <code class="command">dracut</code> utility to create the initial RAM disk image is <code class="filename">initramfs-<em class="replaceable"><code>kernel_version</code></em>.img</code>.
</div><div class="para">
- For information on using <span class="application"><strong>Dracut</strong></span>, refer to <a class="xref" href="sec-Verifying_the_Initial_RAM_Disk_Image.html">Section 20.5, “Verifying the Initial RAM Disk Image”</a>.
+ 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 21.5, “Verifying the Initial RAM Disk Image”</a>.
</div></div></div><div class="para">
After installing a new kernel with <code class="command">rpm</code>, verify that <code class="filename">/boot/grub2/grub.cfg</code> is correct and reboot the computer into the new kernel. Ensure your hardware is detected by watching the boot process output. If GRUB 2 presents an error and is unable to boot into the new kernel, it is often easiest to try to boot into an alternative or older kernel so that you can fix the problem. Alternatively, use the boot media you created earlier to boot the system.
</div><div class="important"><div class="admonition_header"><h2>Causing the GRUB 2 boot menu to display</h2></div><div class="admonition"><div class="para">
If you set the <code class="option">GRUB_TIMEOUT</code> option in the <code class="filename">/etc/default/grub</code> file to <code class="constant">0</code>, GRUB 2 will not display its list of bootable kernels when the system starts up. In order to display this list when booting, press and hold any alphanumeric key while and immediately after BIOS information is displayed, and GRUB 2 will present you with the GRUB menu.
- </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Verifying_the_Initial_RAM_Disk_Image.html"><strong>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>
\ No newline at end of file
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Verifying_the_Initial_RAM_Disk_Image.html"><strong>Prev</strong>21.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>21.6.2. Configuring the OS/400 Boot Loader</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-download.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-download.html
index c5b3cff..3ffadf7 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-download.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-download.html
@@ -1,17 +1,17 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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</s
trong></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">20.3. Downloading the Upgraded Kernel</h2></div></div></div><a id="idm225474594400" class="indexterm"></a><a id="idm225449507376" class="indexterm"></a><a id="idm225449505968" class="indexterm"></a><a id="idm225449504112" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 21. Manually Upgrading the Kernel" /><link rel="prev" href="s1-kernel-preparing.html" title="21.2. Preparing to Upgrade" /><link rel="next" href="s1-kernel-perform-upgrade.html" title="21.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</s
trong></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">21.3. Downloading the Upgraded Kernel</h2></div></div></div><a id="idm261746282384" class="indexterm"></a><a id="idm261746280944" class="indexterm"></a><a id="idm261746279536" class="indexterm"></a><a id="idm261746277680" 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 — See <a href="http://fedoraproject.org/wiki/FSA">http://fedoraproject.org/wiki/FSA</a> for information on Security Advisories, including kernel upgrades that fix security issues.
</div></li><li class="listitem"><div class="para">
Via Fedora Update System — Download and install the kernel RPM packages. For more information, refer to <a href="http://admin.fedoraproject.org/updates/">http://admin.fedoraproject.org/updates/</a>.
</div></li></ul></div><div class="para">
- To install the kernel manually, continue to <a class="xref" href="s1-kernel-perform-upgrade.html">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>
\ No newline at end of file
+ To install the kernel manually, continue to <a class="xref" href="s1-kernel-perform-upgrade.html">Section 21.4, “Performing the Upgrade”</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-preparing.html"><strong>Prev</strong>21.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>21.4. Performing the Upgrade</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-modules-additional-resources.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-modules-additional-resources.html
index 3278627..c842dbd 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-modules-additional-resources.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-modules-additional-resources.html
@@ -1,12 +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.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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.8. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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="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="sec-Persistent_Module_Loading.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="s1-kernel-modules-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.7. Additional Resources</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="prev" href="sect-loading-signed-kernel-module.html" title="22.7.6. Loading Signed Kernel Module" /><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="sect-loading-signed-kernel-module.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="s1-kernel-modules-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">22.8. Additional Resources</h2></div></div></div><div class="para">
For more information on kernel modules and their utilities, see the following resources.
</div><h3 id="bh-Manual_Page_Documentation">Manual Page Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="filename">lsmod(8)</code> — The manual page for the <code class="command">lsmod</code> command.
@@ -22,4 +22,4 @@
<code class="filename">mii-tool(8)</code> — The manual page for the <code class="command">mii-tool</code> command.
</div></li></ul></div><h3 id="bh-Installable_and_External_Documentation">Installable and External Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://tldp.org/HOWTO/Module-HOWTO/">Linux Loadable Kernel Module HOWTO</a> — The <em class="citetitle">Linux Loadable Kernel Module HOWTO</em> from the Linux Documentation Project contains further information on working with kernel modules.
- </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="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="ch-RPM.html"><strong>Next</strong>Appendix A. RPM</a></li></ul></body></html>
\ No newline at end of file
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-loading-signed-kernel-module.html"><strong>Prev</strong>22.7.6. Loading Signed Kernel 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="ch-RPM.html"><strong>Next</strong>Appendix A. RPM</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-perform-upgrade.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-perform-upgrade.html
index e877d89..abfdc5d 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-perform-upgrade.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-perform-upgrade.html
@@ -1,17 +1,17 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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-download.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">20.4. Performing the Upgrade</h2></div></div></div><a id="idm225446646752" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 21. Manually Upgrading the Kernel" /><link rel="prev" href="s1-kernel-download.html" title="21.3. Downloading the Upgraded Kernel" /><link rel="next" href="sec-Verifying_the_Initial_RAM_Disk_Image.html" title="21.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-download.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">21.4. Performing the Upgrade</h2></div></div></div><a id="idm261740460656" class="indexterm"></a><div class="para">
After retrieving all of the necessary packages, it is time to upgrade the existing kernel.
</div><div class="important"><div class="admonition_header"><h2>Keep the old kernel when performing the upgrade</h2></div><div class="admonition"><div class="para">
It is strongly recommended that you keep the old kernel in case there are problems with the new kernel.
</div></div></div><div class="para">
At a shell prompt, change to the directory that contains the kernel RPM packages. Use <code class="option">-i</code> argument with the <code class="command">rpm</code> command to keep the old kernel. Do <span class="emphasis"><em>not</em></span> use the <code class="option">-U</code> option, since it overwrites the currently installed kernel, which creates boot loader problems. For example:
</div><pre class="screen">~]# <code class="command">rpm -ivh kernel-<em class="replaceable"><code>kernel_version</code></em>.<em class="replaceable"><code>arch</code></em>.rpm </code></pre><div class="para">
- The next step is to verify that the initial RAM disk image has been created. See <a class="xref" href="sec-Verifying_the_Initial_RAM_Disk_Image.html">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>
\ No newline at end of file
+ The next step is to verify that the initial RAM disk image has been created. See <a class="xref" href="sec-Verifying_the_Initial_RAM_Disk_Image.html">Section 21.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>21.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>21.5. Verifying the Initial RAM Disk Image</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-preparing.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-preparing.html
index 66ab16d..b1b46f3 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-preparing.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-kernel-preparing.html
@@ -1,12 +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>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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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-Manuall
y_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">20.2. Preparing to Upgrade</h2></div></div></div><a id="idm225471483248" class="indexterm"></a><a id="idm225471482288" class="indexterm"></a><a id="idm225471480368" class="indexterm"></a><a id="idm225471478928" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 21. Manually Upgrading the Kernel" /><link rel="prev" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 21. Manually Upgrading the Kernel" /><link rel="next" href="s1-kernel-download.html" title="21.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-Manuall
y_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">21.2. Preparing to Upgrade</h2></div></div></div><a id="idm261746481808" class="indexterm"></a><a id="idm261746480848" class="indexterm"></a><a id="idm261746478928" class="indexterm"></a><a id="idm261753029424" class="indexterm"></a><div class="para">
Before upgrading the kernel, it is recommended that you take some precautionary steps.
</div><div class="para">
First, ensure that working boot media exists for the system in case a problem occurs. If the boot loader is not configured properly to boot the new kernel, you can use this media to boot into Fedora.
@@ -41,14 +41,16 @@
</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 might differ:
</div><pre class="screen">~]# <code class="command">yum list installed "kernel-*"</code>
-Loaded plugins: langpacks, refresh-packagekit
+Loaded plugins: langpacks
Installed Packages
-kernel.x86_64 3.16.7-200.fc20 @updates
-kernel.x86_64 3.17.2-200.fc20 @updates
-kernel.x86_64 3.17.3-200.fc20 @updates
-kernel-doc.noarch 3.17.3-200.fc20 @updates
-kernel-modules-extra.x86_64 3.16.7-200.fc20 @updates
-kernel-modules-extra.x86_64 3.17.2-200.fc20 @updates
-kernel-modules-extra.x86_64 3.17.3-200.fc20 @updates</pre><div class="para">
- From the output, determine which packages need to be downloaded for the kernel upgrade. For a single processor system, the only required package is the <span class="package">kernel</span> package. See <a class="xref" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">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>
\ No newline at end of file
+kernel.x86_64 3.17.4-302.fc21 @updates
+kernel.x86_64 3.17.6-300.fc21 @updates
+kernel.x86_64 3.17.7-300.fc21 @updates
+kernel-core.x86_64 3.17.4-302.fc21 @updates
+kernel-core.x86_64 3.17.6-300.fc21 @updates
+kernel-core.x86_64 3.17.7-300.fc21 @updates
+kernel-modules.x86_64 3.17.4-302.fc21 @updates
+kernel-modules.x86_64 3.17.6-300.fc21 @updates
+kernel-modules.x86_64 3.17.7-300.fc21 @updates</pre><div class="para">
+ From the output, determine which packages need to be downloaded for the kernel upgrade. For a single processor system, the only required package is the <span class="package">kernel</span> package. See <a class="xref" href="ch-Manually_Upgrading_the_Kernel.html#s1-kernel-packages">Section 21.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 21. 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>21.3. Downloading the Upgraded Kernel</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-log-files-additional-resources.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-log-files-additional-resources.html
index 44bfbe8..2074be4 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-log-files-additional-resources.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-log-files-additional-resources.html
@@ -1,19 +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>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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.10. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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>Pre
v</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">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">17.6.1. Installed Documentation</h3></div></div></div><a id="idm225438573968" 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/ </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>
\ No newline at end of file
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Viewing_and_Managing_Log_Files.html" title="Chapter 17. Viewing and Managing Log Files" /><link rel="prev" href="s2-logfiles-examining.html" title="17.9.3. Monitoring Log Files" /><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="s2-logfiles-examining.html
"><strong>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="s1-log-files-additional-resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.10. Additional Resources</h2></div></div></div><div class="para">
+ For more information on how to configure the <code class="systemitem">rsyslog</code> daemon and how to locate, view, and monitor log files, see the resources listed below.
+ </div><h3 id="brid-Log_Files-Resources-Installed">Installed Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">rsyslogd</code>(8) — The manual page for the <code class="systemitem">rsyslogd</code> daemon documents its usage.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">rsyslog.conf</code>(5) — The manual page named <code class="systemitem">rsyslog.conf</code> documents available configuration options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">logrotate</code>(8) — The manual page for the <span class="application"><strong>logrotate</strong></span> utility explains in greater detail how to configure and use it.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">journalctl</code>(1) — The manual page for the <code class="command">journalctl</code> daemon documents its usage.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">journald.conf</code>(5) — This manual page documents available configuration options.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">systemd.journal-fields</code>(7) — This manual page lists special <span class="application"><strong>Journal</strong></span> fields.
+ </div></li></ul></div><h3 id="brid-Log_Files-Resources-Online">Online Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://www.rsyslog.com/">rsyslog Home Page</a> — The <span class="application"><strong>rsyslog</strong></span> home page offers a thorough technical breakdown of its features, documentation, configuration examples, and video tutorials.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.rsyslog.com/doc/rainerscript.html"><span class="emphasis"><em>RainerScript</em></span> documentation on the rsyslog Home Page</a> — Commented summary of data types, expressions, and functions available in <span class="emphasis"><em>RainerScript</em></span>.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://www.rsyslog.com/doc/queues.html">Description of <span class="emphasis"><em>queues</em></span> on the rsyslog Home Page</a> — General information on various types of message queues and their usage.
+ </div></li><li class="listitem"><div class="para">
+ <a href="http://wiki.rsyslog.com/index.php/Main_Page">rsyslog Wiki</a> — <em class="citetitle">The rsyslog Wiki</em> contains useful configuration examples.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-logfiles-examining.html"><strong>Prev</strong>17.9.3. 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="ch-Automating_System_Tasks.html"><strong>Next</strong>Chapter 18. Automating System Tasks</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-managing_log_files_in_a_graphical_environment.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-managing_log_files_in_a_graphical_environment.html
new file mode 100644
index 0000000..19bbe24
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-managing_log_files_in_a_graphical_environment.html
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.9. Managing Log Files in a Graphical Environment</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Viewing_and_Managing_Log_Files.html" title="Chapter 17. Viewing and Managing Log Files" /><link rel="prev" href="s2-Enabling_Persistent_Storage.html" title="17.8.5. Enabling Persistent Storage" /><link rel="next" href="s2-logfiles-adding.html" title="17.9.2. 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="s2-Enabling_Persistent_Storag
e.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-logfiles-adding.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-managing_log_files_in_a_graphical_environment"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.9. Managing Log Files in a Graphical Environment</h2></div></div></div><div class="para">
+ As an alternative to the aforementioned command-line utilities, Red Hat Enterprise Linux 7 provides an accessible GUI for managing log messages.
+ </div><div class="section" id="s2-logfiles-viewing"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.9.1. Viewing Log Files</h3></div></div></div><a id="idm261726812688" class="indexterm"></a><div class="para">
+ Most log files are stored in plain text format. You can view them with any text editor such as <code class="command">Vi</code> or <span class="application"><strong>Emacs</strong></span>. Some log files are readable by all users on the system; however, root privileges are required to read most log files.
+ </div><a id="idm261726809616" class="indexterm"></a><div class="para">
+ To view system log files in an interactive, real-time application, use the <span class="application"><strong>System Log</strong></span>.
+ </div><div class="note"><div class="admonition_header"><h2>Installing the gnome-system-log package</h2></div><div class="admonition"><div class="para">
+ In order to use the <span class="application"><strong>System Log</strong></span>, first ensure the <span class="package">gnome-system-log</span> package is installed on your system by running, as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">yum install gnome-system-log</code>
+</pre><div class="para">
+ For more information on installing packages with Yum, see <a class="xref" href="sec-Installing.html">Section 5.2.4, “Installing Packages”</a>.
+ </div></div></div><div class="para">
+ After you have installed the <span class="package">gnome-system-log</span> package, open the <span class="application"><strong>System Log</strong></span> by clicking <span class="guimenu"><strong>Applications</strong></span> → <span class="guimenuitem"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Log</strong></span>, or type the following command at a shell prompt:
+ </div><pre class="screen">~]$ <code class="command">gnome-system-log</code>
+</pre><div class="para">
+ The application only displays log files that exist; thus, the list might differ from the one shown in <a class="xref" href="s1-managing_log_files_in_a_graphical_environment.html#fig-redhat-logviewer">Figure 17.2, “System Log”</a>.
+ </div><a id="idm261786593504" class="indexterm"></a><a id="idm261786591904" class="indexterm"></a><div class="figure" id="fig-redhat-logviewer"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer.png" width="444" alt="System Log" /><div class="longdesc"><div class="para">
+ System Log
+ </div></div></div></div><h6>Figure 17.2. System Log</h6></div><br class="figure-break" /><a id="idm261724828784" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>System Log</strong></span> application lets you filter any existing log file. Click on the button marked with the gear symbol to view the menu, select <span class="guimenuitem"><strong>Filters</strong></span> → <span class="guimenuitem"><strong>Manage Filters</strong></span> to define or edit the desired filter.
+ </div><div class="figure" id="fig-redhat-filters"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-filters.png" alt="System Log - Filters" /><div class="longdesc"><div class="para">
+ System Log - Filters
+ </div></div></div></div><h6>Figure 17.3. System Log - 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-managing_log_files_in_a_graphical_environment.html#fig-redhat-filter-sample">Figure 17.4, “System Log - defining a filter”</a>.
+ </div><div class="figure" id="fig-redhat-filter-sample"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-filter-sample.png" alt="System Log - defining a filter" /><div class="longdesc"><div class="para">
+ System Log - Defining a Filter
+ </div></div></div></div><h6>Figure 17.4. System Log - defining a filter</h6></div><br class="figure-break" /><div class="para">
+ When defining a filter, the following parameters can be edited:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="guilabel"><strong>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, it can be selected from the <span class="guilabel"><strong>Filters</strong></span> menu and it will automatically search for the strings you have defined in the filter and highlight or hide every successful match in the log file you are currently viewing.
+ </div><div class="figure" id="fig-redhat-filter-enable"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-filter-enable.png" width="444" alt="System Log - enabled filter" /><div class="longdesc"><div class="para">
+ System Log - Enabling a Filter
+ </div></div></div></div><h6>Figure 17.5. System Log - enabled filter</h6></div><br class="figure-break" /><div class="para">
+ When you select the <span class="guilabel"><strong>Show matches only</strong></span> option, only the matched strings will be shown in the log file you are currently viewing.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-Enabling_Persistent_Storage.html"><strong>Prev</strong>17.8.5. Enabling Persistent Storage</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-logfiles-adding.html"><strong>Next</strong>17.9.2. Adding a Log File</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-openssh-additional-resources.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-openssh-additional-resources.html
index 59fd019..18a9a96 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-openssh-additional-resources.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-openssh-additional-resources.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OpenSSH.html" title="Chapter 7. OpenSSH" /><link rel="prev" href="s2-ssh-beyondshell-tcpip.html" title="7.4.2. Port Forwarding" /><link rel="next" href="ch-TigerVNC.html" title="Chapter 8. TigerVNC" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-beyondshell-tcpip.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Tig
erVNC.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">7.5. Additional Resources</h2></div></div></div><a id="idm225477233120" class="indexterm"></a><a id="idm225477231680" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OpenSSH.html" title="Chapter 7. OpenSSH" /><link rel="prev" href="s2-ssh-beyondshell-tcpip.html" title="7.4.2. Port Forwarding" /><link rel="next" href="ch-TigerVNC.html" title="Chapter 8. TigerVNC" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-beyondshell-tcpip.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Tig
erVNC.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">7.5. Additional Resources</h2></div></div></div><a id="idm261759762224" class="indexterm"></a><a id="idm261756953952" class="indexterm"></a><div class="para">
For more information on how to configure or connect to an OpenSSH server on Fedora, see the resources listed below.
</div><h3 id="bh-OpenSSH-Resources-Installed">Installed Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="systemitem">sshd</code>(8) — The manual page for the <code class="systemitem">sshd</code> daemon documents available command line options and provides a complete list of supported configuration files and directories.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-analyzing-data.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-analyzing-data.html
index 31fa744..7625620 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-analyzing-data.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-analyzing-data.html
@@ -1,13 +1,17 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.5. Analyzing the Data</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Analyzing the Data</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s1-oprofile-saving-data.html" title="19.4. Saving Data" /><link rel="next" href="s2-oprofile-reading-opreport-single.html" title="19.5.2. Using opreport on a Single Executable" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-saving-data.html"><strong>Prev</strong></a></li><
li class="next"><a accesskey="n" href="s2-oprofile-reading-opreport-single.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-analyzing-data"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.5. Analyzing the Data</h2></div></div></div><a id="idm225470190768" class="indexterm"></a><div class="para">
- Periodically, the OProfile daemon, <code class="command">oprofiled</code>, collects the samples and writes them to the <code class="filename">/var/lib/oprofile/samples/</code> directory. Before reading the data, make sure all data has been written to this directory by executing the following command as root:
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s1-oprofile-saving-data.html" title="19.5. Saving Data in Legacy Mode" /><link rel="next" href="s2-oprofile-reading-opreport-single.html" title="19.6.2. Using opreport on a Single Executable" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-saving-data.html"><strong>Prev</st
rong></a></li><li class="next"><a accesskey="n" href="s2-oprofile-reading-opreport-single.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-analyzing-data"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.6. Analyzing the Data</h2></div></div></div><a id="idm261758126928" class="indexterm"></a><div class="para">
+ The same OProfile post-processing tools are used whether you collect your profile with <code class="command">operf</code> or <code class="command">opcontrol</code> in legacy mode.
+ </div><div class="para">
+ By default, <code class="command">operf</code> stores the profiling data in the <code class="filename"><em class="replaceable"><code>current_dir</code></em>/oprofile_data/</code> directory. You can change to a different location with the <code class="option">--session-dir</code> option. The usual post-profiling analysis tools such as <code class="command">opreport</code> and <code class="command">opannotate</code> can be used to generate profile reports. These tools search for samples in <code class="filename"><em class="replaceable"><code>current_dir</code></em>/oprofile_data/</code> first. If this directory does not exist, the analysis tools use the standard session directory of <code class="filename">/var/lib/oprofile/</code>. Statistics, such as total samples received and lost samples, are written to the <code class="filename"><em class="replaceable"><code>session_dir</code></em>/samples/operf.log</code> file.
+ </div><div class="para">
+ When using legacy mode, the OProfile daemon, <code class="command">oprofiled</code>, periodically collects the samples and writes them to the <code class="filename">/var/lib/oprofile/samples/</code> directory. Before reading the data, make sure all data has been written to this directory by executing the following command as root:
</div><pre class="screen">~]# <code class="command">opcontrol --dump</code></pre><div class="para">
Each sample file name is based on the name of the executable. For example, the samples for the default event on a Pentium III processor for <code class="command">/bin/bash</code> becomes:
</div><pre class="screen">\{root\}/bin/bash/\{dep\}/\{root\}/bin/bash/CPU_CLK_UNHALTED.100000</pre><div class="para">
@@ -19,14 +23,13 @@
</div></li></ul></div><div class="para">
Use these tools, along with the binaries profiled, to generate reports that can be further analyzed.
</div><div class="warning"><div class="admonition_header"><h2>Back up the executable and the sample files</h2></div><div class="admonition"><div class="para">
- The executable being profiled must be used with these tools to analyze the data. If it must change after the data is collected, back up the executable used to create the samples as well as the sample files. Please note that the sample file and the binary have to agree. Making a backup is not going to work if they do not match. <code class="command">oparchive</code> can be used to address this problem.
+ The executable being profiled must be used with these tools to analyze the data. If it must change after the data is collected, back up the executable used to create the samples as well as the sample files. Note that the names of the sample file and the binary have to agree. You cannot make a backup if these names do not match. As an alternative, <code class="command">oparchive</code> can be used to address this problem.
</div></div></div><div class="para">
- Samples for each executable are written to a single sample file. Samples from each dynamically linked library are also written to a single sample file. While OProfile is running, if the executable being monitored changes and a sample file for the executable exists, the existing sample file is automatically deleted. Thus, if the existing sample file is needed, it must be backed up, along with the executable used to create it before replacing the executable with a new version. The OProfile analysis tools use the executable file that created the samples during analysis. If the executable changes the analysis tools will be unable to analyze the associated samples. See <a class="xref" href="s1-oprofile-saving-data.html">Section 19.4, “Saving Data”</a> for details on how to back up the sample file.
- </div><div class="section" id="s2-oprofile-reading-opreport"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.5.1. Using <code class="command">opreport</code> </h3></div></div></div><a id="idm225475177008" class="indexterm"></a><a id="idm225475174784" class="indexterm"></a><div class="para">
- The <code class="command">opreport</code> tool provides an overview of all the executables being profiled.
- </div><div class="para">
- The following is part of a sample output:
- </div><pre class="screen">Profiling through timer interrupt
+ Samples for each executable are written to a single sample file. Samples from each dynamically linked library are also written to a single sample file. While OProfile is running, if the executable being monitored changes and a sample file for the executable exists, the existing sample file is automatically deleted. Thus, if the existing sample file is needed, it must be backed up, along with the executable used to create it before replacing the executable with a new version. The OProfile analysis tools use the executable file that created the samples during analysis. If the executable changes, the analysis tools will be unable to analyze the associated samples. See <a class="xref" href="s1-oprofile-saving-data.html">Section 19.5, “Saving Data in Legacy Mode”</a> for details on how to back up the sample file.
+ </div><div class="section" id="s2-oprofile-reading-opreport"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.6.1. Using <code class="command">opreport</code></h3></div></div></div><a id="idm261746008112" class="indexterm"></a><a id="idm261747015728" class="indexterm"></a><div class="para">
+ The <code class="command">opreport</code> tool provides an overview of all the executables being profiled. The following is part of a sample output from the <code class="command">opreport</code> command:
+ </div><pre class="screen">~]$ <code class="command">opreport</code>
+Profiling through timer interrupt
TIMER:0|
samples| %|
------------------
@@ -54,5 +57,5 @@ samples| %|
1 0.0038 libwnck-1.so.4.9.0</pre><div class="para">
Each executable is listed on its own line. The first column is the number of samples recorded for the executable. The second column is the percentage of samples relative to the total number of samples. The third column is the name of the executable.
</div><div class="para">
- See the <code class="command">opreport</code> man page for a list of available command line options, such as the <code class="option">-r</code> option used to sort the output from the executable with the smallest number of samples to the one with the largest number of samples.
- </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-saving-data.html"><strong>Prev</strong>19.4. Saving Data</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-oprofile-reading-opreport-single.html"><strong>Next</strong>19.5.2. Using opreport on a Single Executable</a></li></ul></body></html>
\ No newline at end of file
+ See the <code class="systemitem">opreport(1)</code> manual page for a list of available command-line options, such as the <code class="option">-r</code> option used to sort the output from the executable with the smallest number of samples to the one with the largest number of samples. You can also use the <code class="option">-t</code> or <code class="option">--threshold</code> option to trim the output of <code class="command">opcontrol</code>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-saving-data.html"><strong>Prev</strong>19.5. Saving Data in Legacy Mode</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-oprofile-reading-opreport-single.html"><strong>Next</strong>19.6.2. Using opreport on a Single Executable</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-and-systemtap.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-and-systemtap.html
index dec7163..686cafe 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-and-systemtap.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-and-systemtap.html
@@ -1,17 +1,17 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.10. OProfile and SystemTap</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.11. OProfile and SystemTap</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s1-oprofile-gui.html" title="19.9. Graphical Interface" /><link rel="next" href="s1-oprofile-additional-resources.html" title="19.11. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-gui.html"><strong>Prev</strong></a></li><li class="next"><a accesskey=
"n" href="s1-oprofile-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-and-systemtap"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.10. OProfile and SystemTap</h2></div></div></div><a id="idm225447242928" class="indexterm"></a><div class="para">
- SystemTap is a tracing and probing tool that allows users to study and monitor the activities of the operating system in fine detail. It provides information similar to the output of tools like <code class="command">netstat</code>, <code class="command">ps</code>, <code class="command">top</code>, and <code class="command">iostat</code>; however, SystemTap is designed to provide more filtering and analysis options for collected information.
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s1-oprofile-gui.html" title="19.10. Graphical Interface" /><link rel="next" href="s1-oprofile_additional_resources.html" title="19.12. 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-oprofile-gui.html"><strong>Prev</strong></a></li><li class="next"><a accesskey
="n" href="s1-oprofile_additional_resources.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-and-systemtap"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.11. OProfile and SystemTap</h2></div></div></div><a id="idm261726512176" class="indexterm"></a><div class="para">
+ SystemTap is a tracing and probing tool that allows users to study and monitor the activities of the operating system in fine detail. It provides information similar to the output of tools like <code class="command">netstat</code>, <code class="command">ps</code>, <code class="command">top</code>, and <code class="command">iostat</code>; however, SystemTap is designed to provide more filtering and analysis options for the collected information.
</div><div class="para">
While using OProfile is suggested in cases of collecting data on where and why the processor spends time in a particular area of code, it is less usable when finding out why the processor stays idle.
</div><div class="para">
- You might want to use SystemTap when instrumenting specific places in code. Because SystemTap allows you to run the code instrumentation without having to stop and restart the instrumentation, it is particularly useful for instrumenting the kernel and daemons.
+ You might want to use SystemTap when instrumenting specific places in code. Because SystemTap allows you to run the code instrumentation without having to stop and restart the instrumented code, it is particularly useful for instrumenting the kernel and daemons.
</div><div class="para">
- For more information on SystemTap, refer to <a class="xref" href="s2-oprofile-useful-websites.html">Section 19.11.2, “Useful Websites”</a> for the relevant SystemTap documentation.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-gui.html"><strong>Prev</strong>19.9. Graphical 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="s1-oprofile-additional-resources.html"><strong>Next</strong>19.11. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
+ For more information on SystemTap, see <a class="xref" href="s1-oprofile_additional_resources.html#br-oprofile_online_documentation">the section called “Online Documentation”</a> for the relevant SystemTap documentation.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-gui.html"><strong>Prev</strong>19.10. Graphical 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="s1-oprofile_additional_resources.html"><strong>Next</strong>19.12. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-configuring.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-configuring.html
index 150e851..0a2aaf9 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-configuring.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-configuring.html
@@ -1,23 +1,23 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2. Configuring OProfile</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Configuring OProfile Using Legacy Mode</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="next" href="s2-oprofile-events.html" title="19.2.2. Setting Events to Monitor" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-OProfile.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-oprofil
e-events.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.2. Configuring OProfile</h2></div></div></div><a id="idm225459924928" class="indexterm"></a><a id="idm225452105408" class="indexterm"></a><a id="idm225452103296" class="indexterm"></a><div class="para">
- Before OProfile can be run, it must be configured. At a minimum, selecting to monitor the kernel (or selecting not to monitor the kernel) is required. The following sections describe how to use the <code class="command">opcontrol</code> utility to configure OProfile. As the <code class="command">opcontrol</code> commands are executed, the setup options are saved to the <code class="filename">/root/.oprofile/daemonrc</code> file.
- </div><div class="section" id="s2-oprofile-kernel"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.1. Specifying the Kernel</h3></div></div></div><a id="idm225435823440" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s2-operf-categorization.html" title="19.2.3. Categorization of Samples" /><link rel="next" href="s2-oprofile-events.html" title="19.3.2. Setting Events to Monitor" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-operf-categorization.html"><strong>Prev</strong></a></li><li class="nex
t"><a accesskey="n" href="s2-oprofile-events.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-configuring"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.3. Configuring OProfile Using Legacy Mode</h2></div></div></div><a id="idm261724965472" class="indexterm"></a><a id="idm261755329504" class="indexterm"></a><a id="idm261755327904" class="indexterm"></a><div class="para">
+ Before OProfile can be run in legacy mode, it must be configured. At a minimum, selecting to monitor the kernel (or selecting not to monitor the kernel) is required. The following sections describe how to use the <code class="command">opcontrol</code> utility to configure OProfile. As the <code class="command">opcontrol</code> commands are executed, the setup options are saved to the <code class="filename">/root/.oprofile/daemonrc</code> file.
+ </div><div class="section" id="s2-oprofile-kernel"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.3.1. Specifying the Kernel</h3></div></div></div><a id="idm261755323136" class="indexterm"></a><div class="para">
First, configure whether OProfile should monitor the kernel. This is the only configuration option that is required before starting OProfile. All others are optional.
</div><div class="para">
- To monitor the kernel, execute the following command as root:
- </div><a id="idm225435820720" class="indexterm"></a><pre class="screen">~]# <code class="command">opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux</code></pre><div class="note"><div class="admonition_header"><h2>Install the debuginfo package</h2></div><div class="admonition"><div class="para">
- The <span class="package">debuginfo</span> package for the kernel must be installed (which contains the uncompressed kernel) in order to monitor the kernel.
+ To monitor the kernel, execute the following command as <code class="systemitem">root</code>:
+ </div><a id="idm261721831680" class="indexterm"></a><pre class="screen">~]# <code class="command">opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux</code></pre><div class="important"><div class="admonition_header"><h2>Install the debuginfo package</h2></div><div class="admonition"><div class="para">
+ In order to monitor the kernel, the <span class="package">debuginfo</span> package which contains the uncompressed kernel must be installed.
</div></div></div><div class="para">
- To configure OProfile not to monitor the kernel, execute the following command as root:
- </div><a id="idm225439118768" class="indexterm"></a><pre class="screen">~]# <code class="command">opcontrol --setup --no-vmlinux</code></pre><div class="para">
- This command also loads the <code class="computeroutput">oprofile</code> kernel module, if it is not already loaded, and creates the <code class="filename">/dev/oprofile/</code> directory, if it does not already exist. See <a class="xref" href="s1-oprofile-dev-oprofile.html">Section 19.6, “Understanding <code class="filename">/dev/oprofile/</code> ”</a> for details about this directory.
+ To configure OProfile not to monitor the kernel, execute the following command as <code class="systemitem">root</code>:
+ </div><a id="idm261754219728" class="indexterm"></a><pre class="screen">~]# <code class="command">opcontrol --setup --no-vmlinux</code></pre><div class="para">
+ This command also loads the <code class="computeroutput">oprofile</code> kernel module, if it is not already loaded, and creates the <code class="filename">/dev/oprofile/</code> directory, if it does not already exist. See <a class="xref" href="s1-oprofile-dev-oprofile.html">Section 19.7, “Understanding the /dev/oprofile/ directory ”</a> for details about this directory.
</div><div class="para">
- Setting whether samples should be collected within the kernel only changes what data is collected, not how or where the collected data is stored. To generate different sample files for the kernel and application libraries, refer to <a class="xref" href="s2-oprofile-starting-separate.html">Section 19.2.3, “Separating Kernel and User-space Profiles”</a>.
- </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-OProfile.html"><strong>Prev</strong>Chapter 19. OProfile</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-oprofile-events.html"><strong>Next</strong>19.2.2. Setting Events to Monitor</a></li></ul></body></html>
\ No newline at end of file
+ Setting whether samples should be collected within the kernel only changes what data is collected, not how or where the collected data is stored. To generate different sample files for the kernel and application libraries, see <a class="xref" href="s2-oprofile-starting-separate.html">Section 19.3.3, “Separating Kernel and User-space Profiles”</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-operf-categorization.html"><strong>Prev</strong>19.2.3. Categorization of Samples</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-oprofile-events.html"><strong>Next</strong>19.3.2. Setting Events to Monitor</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-dev-oprofile.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-dev-oprofile.html
index ddaab97..5a950a7 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-dev-oprofile.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-dev-oprofile.html
@@ -1,15 +1,15 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.6. Understanding /dev/oprofile/</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Understanding the /dev/oprofile/ directory</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s2-oprofile-reading-opannotate.html" title="19.5.4. Using opannotate" /><link rel="next" href="s1-oprofile-example-usage.html" title="19.7. Example 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="s2-oprofile-reading-opannotate.html"><strong>Prev</strong></a></li><li class="next"
><a accesskey="n" href="s1-oprofile-example-usage.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-dev-oprofile"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.6. Understanding <code class="filename">/dev/oprofile/</code> </h2></div></div></div><a id="idm225502007328" class="indexterm"></a><a id="idm225480853296" class="indexterm"></a><div class="para">
- The <code class="filename">/dev/oprofile/</code> directory contains the file system for OProfile. Use the <code class="command">cat</code> command to display the values of the virtual files in this file system. For example, the following command displays the type of processor OProfile detected:
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s2-oprofile-reading-opannotate.html" title="19.6.4. Using opannotate" /><link rel="next" href="s1-oprofile-example-usage.html" title="19.8. Example 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="s2-oprofile-reading-opannotate.html"><strong>Prev</strong></a></li><li class="next"
><a accesskey="n" href="s1-oprofile-example-usage.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-dev-oprofile"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.7. Understanding the /dev/oprofile/ directory </h2></div></div></div><a id="idm261737104464" class="indexterm"></a><a id="idm261737102560" class="indexterm"></a><div class="para">
+ When using OProfile in legacy mode, the <code class="filename">/dev/oprofile/</code> directory is used to store the file system for OProfile. On the other hand, <code class="command">operf</code> does not require <code class="filename">/dev/oprofile/</code>. Use the <code class="command">cat</code> command to display the values of the virtual files in this file system. For example, the following command displays the type of processor OProfile detected:
</div><pre class="screen">~]# <code class="command">cat /dev/oprofile/cpu_type</code></pre><div class="para">
- A directory exists in <code class="filename">/dev/oprofile/</code> for each counter. For example, if there are 2 counters, the directories <code class="filename">/dev/oprofile/0/</code> and <code class="filename">dev/oprofile/1/</code> exist.
+ A directory exists in <code class="filename">/dev/oprofile/</code> for each counter. For example, if there are 2 counters, the directories <code class="filename">/dev/oprofile/0/</code> and <code class="filename">/dev/oprofile/1/</code> exist.
</div><div class="para">
Each directory for a counter contains the following files:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
@@ -28,4 +28,4 @@
<code class="filename">user</code> — If 0, samples are not collected for the counter event when the processor is in user-space; if 1, samples are collected even if the processor is in user-space.
</div></li></ul></div><div class="para">
The values of these files can be retrieved with the <code class="command">cat</code> command. For example:
- </div><pre class="screen">~]# <code class="command">cat /dev/oprofile/0/count</code></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-reading-opannotate.html"><strong>Prev</strong>19.5.4. Using opannotate </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-oprofile-example-usage.html"><strong>Next</strong>19.7. Example Usage</a></li></ul></body></html>
\ No newline at end of file
+ </div><pre class="screen">~]# <code class="command">cat /dev/oprofile/0/count</code></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-reading-opannotate.html"><strong>Prev</strong>19.6.4. Using opannotate</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-oprofile-example-usage.html"><strong>Next</strong>19.8. Example Usage</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-example-usage.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-example-usage.html
index 889ab88..f35ccc5 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-example-usage.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-example-usage.html
@@ -1,15 +1,15 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.7. Example Usage</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Example Usage</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s1-oprofile-dev-oprofile.html" title="19.6. Understanding /dev/oprofile/" /><link rel="next" href="s1-oprofile-java-support.html" title="19.8. OProfile Support for Java" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-dev-oprofile.html"><strong>Prev</strong></a></li><li cla
ss="next"><a accesskey="n" href="s1-oprofile-java-support.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-example-usage"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.7. Example Usage</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s1-oprofile-dev-oprofile.html" title="19.7. Understanding the /dev/oprofile/ directory" /><link rel="next" href="s1-oprofile-java-support.html" title="19.9. OProfile Support for Java" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-dev-oprofile.html"><strong>Prev</strong></
a></li><li class="next"><a accesskey="n" href="s1-oprofile-java-support.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-example-usage"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.8. Example Usage</h2></div></div></div><div class="para">
While OProfile can be used by developers to analyze application performance, it can also be used by system administrators to perform system analysis. For example:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <span class="emphasis"><em>Determine which applications and services are used the most on a system</em></span> — <code class="command">opreport</code> can be used to determine how much processor time an application or service uses. If the system is used for multiple services but is under performing, the services consuming the most processor time can be moved to dedicated systems.
+ <span class="emphasis"><em>Determine which applications and services are used the most on a system</em></span> — <code class="command">opreport</code> can be used to determine how much processor time an application or service uses. If the system is used for multiple services but is underperforming, the services consuming the most processor time can be moved to dedicated systems.
</div></li><li class="listitem"><div class="para">
<span class="emphasis"><em>Determine processor usage</em></span> — The <code class="computeroutput">CPU_CLK_UNHALTED</code> event can be monitored to determine the processor load over a given period of time. This data can then be used to determine if additional processors or a faster processor might improve system performance.
- </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-dev-oprofile.html"><strong>Prev</strong>19.6. Understanding /dev/oprofile/ </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-oprofile-java-support.html"><strong>Next</strong>19.8. OProfile Support for Java</a></li></ul></body></html>
\ No newline at end of file
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-dev-oprofile.html"><strong>Prev</strong>19.7. Understanding the /dev/oprofile/ 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-oprofile-java-support.html"><strong>Next</strong>19.9. OProfile Support for Java</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-gui.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-gui.html
index 7c1b979..fd91afa 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-gui.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-gui.html
@@ -1,37 +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>19.9. Graphical Interface</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.10. Graphical Interface</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s1-oprofile-java-support.html" title="19.8. OProfile Support for Java" /><link rel="next" href="s1-oprofile-and-systemtap.html" title="19.10. OProfile and SystemTap" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-java-support.html"><strong>Prev</strong></a></li><li class="
next"><a accesskey="n" href="s1-oprofile-and-systemtap.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.9. Graphical Interface</h2></div></div></div><a id="idm225468550128" class="indexterm"></a><div class="para">
- Some OProfile preferences can be set with a graphical interface. To start it, execute the <code class="command">oprof_start</code> command as root at a shell prompt. To use the graphical interface, you will need to have the <code class="filename">oprofile-gui</code> package installed.
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s1-oprofile-java-support.html" title="19.9. OProfile Support for Java" /><link rel="next" href="s1-oprofile-and-systemtap.html" title="19.11. OProfile and SystemTap" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-java-support.html"><strong>Prev</strong></a></li><li class="
next"><a accesskey="n" href="s1-oprofile-and-systemtap.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-gui"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.10. Graphical Interface</h2></div></div></div><a id="idm261728874640" class="indexterm"></a><div class="para">
+ Some OProfile preferences can be set with a graphical interface. Make sure you have the <code class="filename">oprofile-gui</code> package that provides the OProfile GUI installed on your system. To start the interface, execute the <code class="command">oprof_start</code> command as root at a shell prompt.
</div><div class="para">
After changing any of the options, save them by clicking the <span class="guibutton"><strong>Save and quit</strong></span> button. The preferences are written to <code class="filename">/root/.oprofile/daemonrc</code>, and the application exits. Exiting the application does not stop OProfile from sampling.
</div><div class="para">
- On the <span class="guilabel"><strong>Setup</strong></span> tab, to set events for the processor counters as discussed in <a class="xref" href="s2-oprofile-events.html">Section 19.2.2, “Setting Events to Monitor”</a>, select the counter from the pulldown menu and select the event from the list. A brief description of the event appears in the text box below the list. Only events available for the specific counter and the specific architecture are displayed. The interface also displays whether the profiler is running and some brief statistics about it.
+ On the <span class="guilabel"><strong>Setup</strong></span> tab, to set events for the processor counters as discussed in <a class="xref" href="s2-oprofile-events.html">Section 19.3.2, “Setting Events to Monitor”</a>, select the counter from the pulldown menu and select the event from the list. A brief description of the event appears in the text box below the list. Only events available for the specific counter and the specific architecture are displayed. The interface also displays whether the profiler is running and some brief statistics about it.
</div><div class="figure" id="fig-oprofile-setup"><div class="figure-contents"><div class="mediaobject"><img src="images/oprof-start-setup.png" alt="OProfile Setup" /><div class="longdesc"><div class="para">
<code class="command">oprof_start</code> interface
</div></div></div></div><h6>Figure 19.1. OProfile Setup</h6></div><br class="figure-break" /><div class="para">
- On the right side of the tab, select the <span class="guilabel"><strong>Profile kernel</strong></span> option to count events in kernel mode for the currently selected event, as discussed in <a class="xref" href="s2-oprofile-starting-separate.html">Section 19.2.3, “Separating Kernel and User-space Profiles”</a>. If this option is unselected, no samples are collected for the kernel.
+ On the right side of the tab, select the <span class="guilabel"><strong>Profile kernel</strong></span> option to count events in kernel mode for the currently selected event, as discussed in <a class="xref" href="s2-oprofile-starting-separate.html">Section 19.3.3, “Separating Kernel and User-space Profiles”</a>. If this option is not selected, no samples are collected for the kernel.
</div><div class="para">
- Select the <span class="guilabel"><strong>Profile user binaries</strong></span> option to count events in user mode for the currently selected event, as discussed in <a class="xref" href="s2-oprofile-starting-separate.html">Section 19.2.3, “Separating Kernel and User-space Profiles”</a>. If this option is unselected, no samples are collected for user applications.
+ Select the <span class="guilabel"><strong>Profile user binaries</strong></span> option to count events in user mode for the currently selected event, as discussed in <a class="xref" href="s2-oprofile-starting-separate.html">Section 19.3.3, “Separating Kernel and User-space Profiles”</a>. If this option is not selected, no samples are collected for user applications.
</div><div class="para">
- Use the <span class="guilabel"><strong>Count</strong></span> text field to set the sampling rate for the currently selected event as discussed in <a class="xref" href="s2-oprofile-events.html#s3-oprofile-events-sampling">Section 19.2.2.1, “Sampling Rate”</a>.
+ Use the <span class="guilabel"><strong>Count</strong></span> text field to set the sampling rate for the currently selected event as discussed in <a class="xref" href="s2-oprofile-events.html#s3-oprofile-events-sampling">Section 19.3.2.1, “Sampling Rate”</a>.
</div><div class="para">
- If any unit masks are available for the currently selected event, as discussed in <a class="xref" href="s2-oprofile-events.html#s3-oprofile-events-unit-masks">Section 19.2.2.2, “Unit Masks”</a>, they are displayed in the <span class="guilabel"><strong>Unit Masks</strong></span> area on the right side of the <span class="guilabel"><strong>Setup</strong></span> tab. Select the checkbox beside the unit mask to enable it for the event.
+ If any unit masks are available for the currently selected event, as discussed in <a class="xref" href="s2-oprofile-events.html#s3-oprofile-events-unit-masks">Section 19.3.2.2, “Unit Masks”</a>, they are displayed in the <span class="guilabel"><strong>Unit Masks</strong></span> area on the right side of the <span class="guilabel"><strong>Setup</strong></span> tab. Select the check box beside the unit mask to enable it for the event.
</div><div class="para">
On the <span class="guilabel"><strong>Configuration</strong></span> tab, to profile the kernel, enter the name and location of the <code class="filename">vmlinux</code> file for the kernel to monitor in the <span class="guilabel"><strong>Kernel image file</strong></span> text field. To configure OProfile not to monitor the kernel, select <span class="guilabel"><strong>No kernel image</strong></span>.
</div><div class="figure" id="fig-oprofile-configuration"><div class="figure-contents"><div class="mediaobject"><img src="images/oprof-start-config.png" alt="OProfile Configuration" /><div class="longdesc"><div class="para">
OProfile Configuration
</div></div></div></div><h6>Figure 19.2. OProfile Configuration</h6></div><br class="figure-break" /><div class="para">
- If the <span class="guilabel"><strong>Verbose</strong></span> option is selected, the <code class="command">oprofiled</code> daemon log includes more information.
+ If the <span class="guilabel"><strong>Verbose</strong></span> option is selected, the <code class="command">oprofiled</code> daemon log includes more detailed information.
</div><div class="para">
- If <span class="guilabel"><strong>Per-application profiles</strong></span> is selected, OProfile generates per-application profiles for libraries. This is equivalent to the <code class="command">opcontrol --separate=library</code> command. If <span class="guilabel"><strong>Per-application profiles, including kernel</strong></span> is selected, OProfile generates per-application profiles for the kernel and kernel modules as discussed in <a class="xref" href="s2-oprofile-starting-separate.html">Section 19.2.3, “Separating Kernel and User-space Profiles”</a>. This is equivalent to the <code class="command">opcontrol --separate=kernel</code> command.
+ If <span class="guilabel"><strong>Per-application profiles</strong></span> is selected, OProfile generates per-application profiles for libraries. This is equivalent to the <code class="command">opcontrol --separate=library</code> command. If <span class="guilabel"><strong>Per-application profiles, including kernel</strong></span> is selected, OProfile generates per-application profiles for the kernel and kernel modules as discussed in <a class="xref" href="s2-oprofile-starting-separate.html">Section 19.3.3, “Separating Kernel and User-space Profiles”</a>. This is equivalent to the <code class="command">opcontrol --separate=kernel</code> command.
</div><div class="para">
- To force data to be written to samples files as discussed in <a class="xref" href="s1-oprofile-analyzing-data.html">Section 19.5, “Analyzing the Data”</a>, click the <span class="guibutton"><strong>Flush</strong></span> button. This is equivalent to the <code class="command">opcontrol --dump</code> command.
+ To force data to be written to samples files as discussed in <a class="xref" href="s1-oprofile-analyzing-data.html">Section 19.6, “Analyzing the Data”</a>, click the <span class="guibutton"><strong>Flush</strong></span> button. This is equivalent to the <code class="command">opcontrol --dump</code> command.
</div><div class="para">
To start OProfile from the graphical interface, click <span class="guibutton"><strong>Start</strong></span>. To stop the profiler, click <span class="guibutton"><strong>Stop</strong></span>. Exiting the application does not stop OProfile from sampling.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-java-support.html"><strong>Prev</strong>19.8. OProfile Support for Java</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-oprofile-and-systemtap.html"><strong>Next</strong>19.10. OProfile and SystemTap</a></li></ul></body></html>
\ No newline at end of file
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-java-support.html"><strong>Prev</strong>19.9. OProfile Support for Java</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-oprofile-and-systemtap.html"><strong>Next</strong>19.11. OProfile and SystemTap</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-java-support.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-java-support.html
index 84431df..59c71c8 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-java-support.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-java-support.html
@@ -1,17 +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>19.8. OProfile Support for Java</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.9. OProfile Support for Java</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s1-oprofile-example-usage.html" title="19.7. Example Usage" /><link rel="next" href="s1-oprofile-gui.html" title="19.9. Graphical Interface" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-example-usage.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" h
ref="s1-oprofile-gui.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-java-support"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.8. OProfile Support for Java</h2></div></div></div><a id="idm225447640816" class="indexterm"></a><div class="para">
- OProfile allows you to profile dynamically compiled code (also known as "just-in-time" or JIT code) of the Java Virtual Machine (JVM). OProfile in Fedora 21 includes build-in support for the JVM Tools Interface (JVMTI) agent library, which supports Java 1.5 and higher.
- </div><div class="section" id="s1-oprofile-java-profiling"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.8.1. Profiling Java Code</h3></div></div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s1-oprofile-example-usage.html" title="19.8. Example Usage" /><link rel="next" href="s1-oprofile-gui.html" title="19.10. Graphical Interface" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-example-usage.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n"
href="s1-oprofile-gui.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-java-support"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.9. OProfile Support for Java</h2></div></div></div><a id="idm261721039312" class="indexterm"></a><div class="para">
+ OProfile allows you to profile dynamically compiled code (also known as "just-in-time" or JIT code) of the Java Virtual Machine (JVM). OProfile in Fedora 21 includes built-in support for the JVM Tools Interface (JVMTI) agent library, which supports Java 1.5 and higher.
+ </div><div class="section" id="s1-oprofile-java-profiling"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.9.1. Profiling Java Code</h3></div></div></div><div class="para">
To profile JIT code from the Java Virtual Machine with the JVMTI agent, add the following to the JVM startup parameters:
- </div><pre class="screen"><code class="option">-agentlib:jvmti_oprofile</code></pre><div class="note"><div class="admonition_header"><h2>Install the oprofile-jit package</h2></div><div class="admonition"><div class="para">
- The <span class="package">oprofile-jit</span> package must be installed on the system in order to profile JIT code with OProfile.
+ </div><pre class="screen"><code class="option">-agentlib:</code><em class="replaceable"><code>jvmti_oprofile</code></em></pre><div class="para">
+ Where <em class="replaceable"><code>jvmti_oprofile</code></em> is a path to the OProfile agent. For 64-bit JVM, the path looks as follows:
+ </div><pre class="screen"><code class="option">-agentlib:/usr/lib64/oprofile/libjvmti_oprofile.so</code></pre><div class="para">
+ Currently, you can add one command-line option: <code class="option">--debug</code>, which enables debugging mode.
+ </div><div class="note"><div class="admonition_header"><h2>Install the oprofile-jit package</h2></div><div class="admonition"><div class="para">
+ The <span class="package">oprofile-jit</span> package must be installed on the system in order to profile JIT code with OProfile. With this package, you gain the capability to show method-level information.
</div></div></div><div class="para">
- To learn more about Java support in OProfile, refer to the OProfile Manual, which is linked from <a class="xref" href="s1-oprofile-additional-resources.html">Section 19.11, “Additional Resources”</a>.
- </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-example-usage.html"><strong>Prev</strong>19.7. Example 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-oprofile-gui.html"><strong>Next</strong>19.9. Graphical Interface</a></li></ul></body></html>
\ No newline at end of file
+ Depending on the JVM that you are using, you may have to install the <span class="emphasis"><em>debuginfo</em></span> package for the JVM. For OpenJDK, this package is required, there is no debuginfo package for Oracle JDK. To keep the debug information packages synchronized with their respective non-debug packages, you also need to install the <span class="emphasis"><em>yum-plugin-auto-update-debug-info</em></span> plug-in. This plug-in searches the debug information repository for corresponding updates.
+ </div><div class="para">
+ After successful setup, you can apply the standard profiling and analyzing tools described in previous sections
+ </div><div class="para">
+ To learn more about Java support in OProfile, see the OProfile Manual, which is linked from <a class="xref" href="s1-oprofile_additional_resources.html">Section 19.12, “Additional Resources”</a>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-example-usage.html"><strong>Prev</strong>19.8. Example 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-oprofile-gui.html"><strong>Next</strong>19.10. Graphical Interface</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-saving-data.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-saving-data.html
index 560e405..fb367df 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-saving-data.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-saving-data.html
@@ -1,15 +1,17 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.4. Saving Data</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Saving Data in Legacy Mode</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s1-oprofile-starting.html" title="19.3. Starting and Stopping OProfile" /><link rel="next" href="s1-oprofile-analyzing-data.html" title="19.5. Analyzing the Data" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-starting.html"><strong>Prev</strong></a></li><li class="next"><
a accesskey="n" href="s1-oprofile-analyzing-data.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-saving-data"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.4. Saving Data</h2></div></div></div><a id="idm225436934192" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s1-oprofile-starting.html" title="19.4. Starting and Stopping OProfile Using Legacy Mode" /><link rel="next" href="s1-oprofile-analyzing-data.html" title="19.6. Analyzing the Data" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-starting.html"><strong>Prev</strong></a></li>
<li class="next"><a accesskey="n" href="s1-oprofile-analyzing-data.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-saving-data"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.5. Saving Data in Legacy Mode</h2></div></div></div><a id="idm261731444256" class="indexterm"></a><div class="para">
Sometimes it is useful to save samples at a specific time. For example, when profiling an executable, it may be useful to gather different samples based on different input data sets. If the number of events to be monitored exceeds the number of counters available for the processor, multiple runs of OProfile can be used to collect data, saving the sample data to different files each time.
</div><div class="para">
- To save the current set of sample files, execute the following command, replacing <em class="replaceable"><code>name</code></em> with a unique descriptive name for the current session.
+ To save the current set of sample files, execute the following command, replacing <em class="replaceable"><code>name</code></em> with a unique descriptive name for the current session:
</div><pre class="screen">~]# <code class="command">opcontrol --save=<em class="replaceable"><code>name</code></em></code></pre><div class="para">
- The directory <code class="filename">/var/lib/oprofile/samples/<em class="replaceable"><code>name</code></em>/</code> is created and the current sample files are copied to it.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-starting.html"><strong>Prev</strong>19.3. Starting and Stopping OProfile</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-oprofile-analyzing-data.html"><strong>Next</strong>19.5. Analyzing the Data</a></li></ul></body></html>
\ No newline at end of file
+ The command creates the directory <code class="filename">/var/lib/oprofile/samples/<em class="replaceable"><code>name</code></em>/</code> and the current sample files are copied to it.
+ </div><div class="para">
+ To specify the session directory to hold the sample data, use the <code class="option">--session-dir</code> option. If not specified, the data is saved in the <code class="filename">oprofile_data/</code> directory on the current path.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-starting.html"><strong>Prev</strong>19.4. Starting and Stopping OProfile Using Legacy...</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-oprofile-analyzing-data.html"><strong>Next</strong>19.6. Analyzing the Data</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-starting.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-starting.html
index 478f73a..2691ba1 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-starting.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile-starting.html
@@ -1,25 +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>19.3. Starting and Stopping OProfile</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Starting and Stopping OProfile Using Legacy Mode</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s2-oprofile-starting-separate.html" title="19.2.3. Separating Kernel and User-space Profiles" /><link rel="next" href="s1-oprofile-saving-data.html" title="19.4. Saving Data" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-starting-separate.html"><strong>Prev</strong></a></
li><li class="next"><a accesskey="n" href="s1-oprofile-saving-data.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-starting"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.3. Starting and Stopping OProfile</h2></div></div></div><a id="idm225479368848" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s2-oprofile-starting-separate.html" title="19.3.3. Separating Kernel and User-space Profiles" /><link rel="next" href="s1-oprofile-saving-data.html" title="19.5. Saving Data in Legacy Mode" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-starting-separate.html"><strong>Prev
</strong></a></li><li class="next"><a accesskey="n" href="s1-oprofile-saving-data.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-oprofile-starting"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.4. Starting and Stopping OProfile Using Legacy Mode</h2></div></div></div><a id="idm261761609264" class="indexterm"></a><div class="para">
To start monitoring the system with OProfile, execute the following command as root:
- </div><a id="idm225479366544" class="indexterm"></a><pre class="screen">~]# <code class="command">opcontrol --start</code></pre><div class="para">
+ </div><a id="idm261761607264" class="indexterm"></a><pre class="screen">~]# <code class="command">opcontrol --start</code></pre><div class="para">
Output similar to the following is displayed:
</div><pre class="screen">Using log file /var/lib/oprofile/oprofiled.log Daemon started. Profiler running.</pre><div class="para">
The settings in <code class="filename">/root/.oprofile/daemonrc</code> are used.
- </div><a id="idm225478146096" class="indexterm"></a><a id="idm225478143872" class="indexterm"></a><a id="idm225478141648" class="indexterm"></a><div class="para">
+ </div><a id="idm261757709536" class="indexterm"></a><a id="idm261757707616" class="indexterm"></a><a id="idm261757706016" class="indexterm"></a><div class="para">
The OProfile daemon, <code class="command">oprofiled</code>, is started; it periodically writes the sample data to the <code class="filename">/var/lib/oprofile/samples/</code> directory. The log file for the daemon is located at <code class="filename">/var/lib/oprofile/oprofiled.log</code>.
</div><div class="important"><div class="admonition_header"><h2>Disable the nmi_watchdog registers</h2></div><div class="admonition"><div class="para">
On a Fedora 21 system, the <code class="computeroutput">nmi_watchdog</code> registers with the <code class="computeroutput">perf</code> subsystem. Due to this, the <code class="computeroutput">perf</code> subsystem grabs control of the performance counter registers at boot time, blocking OProfile from working.
</div><div class="para">
- To resolve this, either boot with the <code class="command">nmi_watchdog=0</code> kernel parameter set, or run the following command to disable <code class="computeroutput">nmi_watchdog</code> at run time:
+ To resolve this, either boot with the <code class="command">nmi_watchdog=0</code> kernel parameter set, or run the following command as <code class="systemitem">root</code> to disable <code class="computeroutput">nmi_watchdog</code> at run time:
</div><pre class="screen">~]# <code class="command">echo 0 > /proc/sys/kernel/nmi_watchdog</code></pre><div class="para">
- To re-enable <code class="computeroutput">nmi_watchdog</code>, use the following command:
+ To re-enable <code class="computeroutput">nmi_watchdog</code>, use the following command as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">echo 1 > /proc/sys/kernel/nmi_watchdog</code></pre></div></div><div class="para">
To stop the profiler, execute the following command as root:
- </div><pre class="screen">~]# <code class="command">opcontrol --shutdown</code></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-starting-separate.html"><strong>Prev</strong>19.2.3. Separating Kernel and User-space Profiles</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-oprofile-saving-data.html"><strong>Next</strong>19.4. Saving Data</a></li></ul></body></html>
\ No newline at end of file
+ </div><pre class="screen">~]# <code class="command">opcontrol --shutdown</code></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-starting-separate.html"><strong>Prev</strong>19.3.3. Separating Kernel and User-space Profiles</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-oprofile-saving-data.html"><strong>Next</strong>19.5. Saving Data in Legacy Mode</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile_additional_resources.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile_additional_resources.html
new file mode 100644
index 0000000..be45af0
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-oprofile_additional_resources.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.12. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="s1-oprofile-and-systemtap.html" title="19.11. OProfile and SystemTap" /><link rel="next" href="part-Kernel_Module_and_Driver_Configuration.html" title="Part VI. 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="s1-oprofile-and-systemtap.html"><st
rong>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="s1-oprofile_additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.12. Additional Resources</h2></div></div></div><a id="idm261747393376" class="indexterm"></a><div class="para">
+ To learn more about OProfile and how to configure it, see the following resources.
+ </div><h3 id="br-oprofile_installed_documentation">Installed Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/oprofile/oprofile.html</code> — <em class="citetitle">OProfile Manual</em>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">oprofile(1)</code> manual page — Discusses <code class="command">opcontrol</code>, <code class="command">opreport</code>, <code class="command">opannotate</code>, and <code class="command">ophelp</code>
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">operf(1)</code> manual page
+ </div></li></ul></div><h3 id="br-oprofile_online_documentation">Online Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://oprofile.sourceforge.net/">http://oprofile.sourceforge.net/</a> — Contains the latest upstream documentation, mailing lists, IRC channels, and more.
+ </div></li></ul></div><h3 id="br-oprofile_see_also">See Also</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/SystemTap_Beginners_Guide/index.html">SystemTap Beginners Guide</a> — Provides basic instructions on how to use SystemTap to monitor different subsystems of Fedora in finer detail.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-and-systemtap.html"><strong>Prev</strong>19.11. OProfile and SystemTap</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 VI. Kernel, Module and Driver Configuration</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-additional-resources.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-additional-resources.html
index 5246226..659ee22 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-additional-resources.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-additional-resources.html
@@ -11,9 +11,9 @@
</div><div class="section" id="s2-printing-additional-resources-installed"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.3.11.1. Installed Documentation</h4></div></div></div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><code class="command">man lp</code></span></dt><dd><div class="para">
The manual page for the <code class="command">lpr</code> command that allows you to print files from the command line.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">man cancel</code></span></dt><dd><div class="para">
- The manual page for the command line utility to remove print jobs from the print queue.
+ The manual page for the command-line utility to remove print jobs from the print queue.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">man mpage</code></span></dt><dd><div class="para">
- The manual page for the command line utility to print multiple pages on one sheet of paper.
+ The manual page for the command-line utility to print multiple pages on one sheet of paper.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">man cupsd</code></span></dt><dd><div class="para">
The manual page for the CUPS printer daemon.
</div></dd><dt class="varlistentry"><span class="term"><code class="command">man cupsd.conf</code></span></dt><dd><div class="para">
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-edit.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-edit.html
index 6497144..a1afe1e 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-edit.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-edit.html
@@ -10,19 +10,19 @@
To delete an existing printer, in the <span class="guilabel"><strong>Printer</strong></span> configuration window, select the printer and go to <span class="guimenu"><strong>Printer</strong></span> → <span class="guimenuitem"><strong>Delete</strong></span>. Confirm the printer deletion. Alternatively, press the <span class="keycap"><strong>Delete</strong></span> key.
</div><div class="para">
To set the default printer, right-click the printer in the printer list and click the <span class="guimenuitem"><strong>Set As Default</strong></span> button in the context menu.
- </div><div class="section" id="idm225476918928"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm225476918928">12.3.10.1. The Settings Page</h4></div></div></div><a id="idm225478290336" class="indexterm"></a><div class="para">
+ </div><div class="section" id="idm261784076384"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm261784076384">12.3.10.1. The Settings Page</h4></div></div></div><a id="idm261784075584" class="indexterm"></a><div class="para">
To change printer driver configuration, double-click the corresponding name in the <span class="guilabel"><strong>Printer</strong></span> list and click the <span class="guilabel"><strong>Settings</strong></span> label on the left to display the <span class="guilabel"><strong>Settings</strong></span> page.
</div><div class="para">
You can modify printer settings such as make and model, print a test page, change the device location (URI), and more.
</div><div class="figure" id="fig-printconf-config1"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-config1.png" alt="Settings page" /><div class="longdesc"><div class="para">
Settings Page
- </div></div></div></div><h6>Figure 12.11. Settings page</h6></div><br class="figure-break" /></div><div class="section" id="idm225463204864"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm225463204864">12.3.10.2. The Policies Page</h4></div></div></div><div class="para">
+ </div></div></div></div><h6>Figure 12.11. Settings page</h6></div><br class="figure-break" /></div><div class="section" id="idm261751867280"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title" id="idm261751867280">12.3.10.2. The Policies Page</h4></div></div></div><div class="para">
Click the <span class="guilabel"><strong>Policies</strong></span> button on the left to change settings in printer state and print output.
</div><div class="para">
You can select the printer states, configure the <span class="guilabel"><strong>Error Policy</strong></span> of the printer (you can decide to abort the print job, retry, or stop it if an error occurs).
</div><div class="para">
You can also create a <em class="firstterm">banner page</em> (a page that describes aspects of the print job such as the originating printer, the user name from the which the job originated, and the security status of the document being printed): click the <span class="guilabel"><strong>Starting Banner</strong></span> or <span class="guilabel"><strong>Ending Banner</strong></span> drop-down menu and choose the option that best describes the nature of the print jobs (for example, <span class="guilabel"><strong>confidential</strong></span>).
- </div><div class="section" id="sec-Sharing_Printers"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.3.10.2.1. Sharing Printers</h5></div></div></div><a id="idm225475805696" class="indexterm"></a><div class="para">
+ </div><div class="section" id="sec-Sharing_Printers"><div class="titlepage"><div><div keep-together.within-column="always"><h5 class="title">12.3.10.2.1. Sharing Printers</h5></div></div></div><a id="idm261759445216" class="indexterm"></a><div class="para">
On the <span class="guilabel"><strong>Policies</strong></span> page, you can mark a printer as shared: if a printer is shared, users published on the network can use it. To allow the sharing function for printers, go to <span class="guimenu"><strong>Server</strong></span> → <span class="guimenuitem"><strong>Settings</strong></span> and select <span class="guilabel"><strong>Publish shared printers connected to this system</strong></span>.
</div><div class="figure" id="fig-printconf-config2"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-config2.png" alt="Policies page" /><div class="longdesc"><div class="para">
Policies Page
@@ -60,7 +60,7 @@
The <span class="guilabel"><strong>Ink/Toner Levels</strong></span> page contains details on toner status if available and printer status messages. Click the <span class="guilabel"><strong>Ink/Toner Levels</strong></span> label on the left to display the page.
</div><div class="figure" id="mediaobj-printconf-config6"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-config6.png" alt="Ink/Toner Levels page" /><div class="longdesc"><div class="para">
Ink/Toner Levels Page
- </div></div></div></div><h6>Figure 12.16. Ink/Toner Levels page</h6></div><br class="figure-break" /></div></div><div class="section" id="s1-printing-managing"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.3.10.3. Managing Print Jobs</h4></div></div></div><a id="idm225435354592" class="indexterm"></a><div class="para">
+ </div></div></div></div><h6>Figure 12.16. Ink/Toner Levels page</h6></div><br class="figure-break" /></div></div><div class="section" id="s1-printing-managing"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.3.10.3. Managing Print Jobs</h4></div></div></div><a id="idm261754452592" class="indexterm"></a><div class="para">
When you send a print job to the printer daemon, such as printing a text file from <span class="application"><strong>Emacs</strong></span> or printing an image from <span class="application"><strong>GIMP</strong></span>, the print job is added to the print spool queue. The print spool queue is a list of print jobs that have been sent to the printer and information about each print request, such as the status of the request, the job number, and more.
</div><div class="para">
During the printing process, messages informing about the process appear in the notification area.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-ipp-printer.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-ipp-printer.html
index 266d5b0..82e5484 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-ipp-printer.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-ipp-printer.html
@@ -6,20 +6,20 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Printer_Configuration.html" title="12.3. Printer Configuration" /><link rel="prev" href="s1-printing-jetdirect-printer.html" title="12.3.4. Adding an AppSocket/HP JetDirect printer" /><link rel="next" href="sec-printing-LPDLPR-printer.html" title="12.3.6. Adding an LPD/LPR Host or Printer" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-printing-jetd
irect-printer.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-printing-LPDLPR-printer.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-printing-ipp-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.5. Adding an IPP Printer</h3></div></div></div><a id="idm225467498768" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Printer_Configuration.html" title="12.3. Printer Configuration" /><link rel="prev" href="s1-printing-jetdirect-printer.html" title="12.3.4. Adding an AppSocket/HP JetDirect printer" /><link rel="next" href="sec-printing-LPDLPR-printer.html" title="12.3.6. Adding an LPD/LPR Host or Printer" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-printing-jetd
irect-printer.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-printing-LPDLPR-printer.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-printing-ipp-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.5. Adding an IPP Printer</h3></div></div></div><a id="idm261753506960" class="indexterm"></a><div class="para">
An <code class="systemitem">IPP</code> printer is a printer attached to a different system on the same TCP/IP network. The system this printer is attached to may either be running CUPS or simply configured to use <code class="systemitem">IPP</code>.
</div><div class="para">
If a firewall is enabled on the printer server, then the firewall must be configured to allow incoming <code class="systemitem">TCP</code> connections on port <code class="literal">631</code>. Note that the CUPS browsing protocol allows client machines to discover shared CUPS queues automatically. To enable this, the firewall on the client machine must be configured to allow incoming <code class="systemitem">UDP</code> packets on port <code class="literal">631</code>.
</div><div class="procedure" id="proc-Adding_IPP_Printer"><div class="para">
Follow this procedure to add an <code class="systemitem">IPP</code> printer:
</div><ol class="1"><li class="step"><div class="para">
- Open the <code class="systemitem">New Printer</code> dialog (refer to <a class="xref" href="sec-Setting_Printer.html">Section 12.3.2, “Starting Printer Setup”</a>).
+ Open the <code class="systemitem">Printers</code> dialog (refer to <a class="xref" href="sec-Setting_Printer.html">Section 12.3.2, “Starting Printer Setup”</a>).
</div></li><li class="step"><div class="para">
In the list of devices on the left, select <span class="guimenu"><strong>Network Printer</strong></span> and <span class="guimenuitem"><strong>Internet Printing Protocol (ipp)</strong></span> or <span class="guimenuitem"><strong>Internet Printing Protocol (https)</strong></span>.
</div></li><li class="step"><div class="para">
On the right, enter the connection settings:
</div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><span class="guilabel"><strong>Host</strong></span></span></dt><dd><div class="para">
- The hostname of the <code class="systemitem">IPP</code> printer.
+ The host name of the <code class="systemitem">IPP</code> printer.
</div></dd><dt class="varlistentry"><span class="term"><span class="guilabel"><strong>Queue</strong></span></span></dt><dd><div class="para">
The queue name to be given to the new queue (if the box is left empty, a name based on the device node will be used).
</div></dd></dl></div><div class="figure" id="fig-printconf-ipp"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-ipp.png" alt="Adding an IPP printer" /><div class="longdesc"><div class="para">
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-jetdirect-printer.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-jetdirect-printer.html
index 780ae68..57ca230 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-jetdirect-printer.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-jetdirect-printer.html
@@ -9,7 +9,7 @@
</script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Printer_Configuration.html" title="12.3. Printer Configuration" /><link rel="prev" href="sec-Adding_Other_Printer.html" title="12.3.3. Adding a Local Printer" /><link rel="next" href="s1-printing-ipp-printer.html" title="12.3.5. Adding an IPP Printer" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Adding_Other_Printer.html"><strong>Prev</strong></a
></li><li class="next"><a accesskey="n" href="s1-printing-ipp-printer.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-printing-jetdirect-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.4. Adding an AppSocket/HP JetDirect printer</h3></div></div></div><div class="para">
Follow this procedure to add an AppSocket/HP JetDirect printer:
</div><div class="procedure" id="proc-Adding_JetDirect_Printer"><ol class="1"><li class="step"><div class="para">
- Open the <code class="systemitem">Add a New Printer</code> dialog (refer to <a class="xref" href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">Section 12.3.1, “Starting the Printer Configuration Tool”</a>).
+ Open the <code class="systemitem">Add a New Printer</code> dialog (refer to <a class="xref" href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">Section 12.3.1, “Starting the Printers Configuration Tool”</a>).
</div></li><li class="step"><div class="para">
In the list on the left, select <span class="guimenu"><strong>Network Printer</strong></span> → <span class="guimenuitem"><strong>AppSocket/HP JetDirect</strong></span>.
</div></li><li class="step"><div class="para">
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-smb-printer.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-smb-printer.html
index c03829f..045ce7f 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-smb-printer.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-printing-smb-printer.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Printer_Configuration.html" title="12.3. Printer Configuration" /><link rel="prev" href="sec-printing-LPDLPR-printer.html" title="12.3.6. Adding an LPD/LPR Host or Printer" /><link rel="next" href="s1-printing-select-model.html" title="12.3.8. Selecting the Printer Model and Finishing" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-printing-LPDLPR-
printer.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-printing-select-model.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-printing-smb-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.7. Adding a Samba (SMB) printer</h3></div></div></div><a id="idm225460277296" class="indexterm"></a><a id="idm225468883056" class="indexterm"></a><div class="procedure" id="proc-Adding_SMB_Printer"><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Printer_Configuration.html" title="12.3. Printer Configuration" /><link rel="prev" href="sec-printing-LPDLPR-printer.html" title="12.3.6. Adding an LPD/LPR Host or Printer" /><link rel="next" href="s1-printing-select-model.html" title="12.3.8. Selecting the Printer Model and Finishing" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-printing-LPDLPR-
printer.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-printing-select-model.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-printing-smb-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.7. Adding a Samba (SMB) printer</h3></div></div></div><a id="idm261746550160" class="indexterm"></a><a id="idm261746548720" class="indexterm"></a><div class="procedure" id="proc-Adding_SMB_Printer"><div class="para">
Follow this procedure to add a Samba printer:
</div><div class="note"><div class="admonition_header"><h2>Installing the samba-client package</h2></div><div class="admonition"><div class="para">
Note that in order to add a Samba printer, you need to have the <span class="package">samba-client</span> package installed. You can do so by running, as <code class="systemitem">root</code>:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-rpm-additional-resources.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-rpm-additional-resources.html
index 3f55a9b..adb617c 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-rpm-additional-resources.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-rpm-additional-resources.html
@@ -6,10 +6,16 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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="s2-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">A.5. Additional Resources</h2></div></div></div><a id="idm225464607824" class="indexterm"></a><div class="para">
- RPM is an extremely complex utility with many options and methods for querying, installing, upgrading, and removing packages. See 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">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>
\ No newline at end of file
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-RPM.html" title="Appendix A. RPM" /><link rel="prev" href="s1-rpm-usage-examples.html" title="A.4. Common Examples of RPM Usage" /><link rel="next" href="app-Revision_History.html" title="Appendix B. 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-rpm-usage-examples.html"><strong>Prev</strong></a></li><li class="next"><a accesskey=
"n" href="app-Revision_History.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">A.5. Additional Resources</h2></div></div></div><a id="idm261728000000" class="indexterm"></a><div class="para">
+ <span class="application"><strong>RPM</strong></span> is a complex utility with many options and methods for querying, installing, upgrading, and removing packages. See the following resources to learn more about <span class="application"><strong>RPM</strong></span>.
+ </div><h3 id="brid-rpm-resources-installed">Installed Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="command">rpm --help</code> — This command displays a quick reference of <span class="application"><strong>RPM</strong></span> parameters.
+ </div></li><li class="listitem"><div class="para">
+ <span class="citerefentry"><span class="refentrytitle">rpm</span>(8)</span> — The <span class="application"><strong>RPM</strong></span> manual page offers an overview of all available <span class="application"><strong>RPM</strong></span> parameters.
+ </div></li></ul></div><h3 id="brid-rpm-resources-online">Online Documentation</h3><div class="itemizedlist"><a id="idm261755873440" class="indexterm"></a><a id="idm261755872000" class="indexterm"></a><ul><li class="listitem"><div class="para">
+ The <span class="application"><strong>RPM</strong></span> website — <a href="http://www.rpm.org/">http://www.rpm.org/</a>
+ </div></li><li class="listitem"><div class="para">
+ The <span class="application"><strong>RPM</strong></span> mailing list — <a href="http://lists.rpm.org/mailman/listinfo/rpm-list">http://lists.rpm.org/mailman/listinfo/rpm-list</a>
+ </div></li></ul></div><h3 id="brid-rpm-resources-also">See Also</h3><div class="itemizedlist"><a id="idm261755864832" class="indexterm"></a><ul><li class="listitem"><div class="para">
+ <a class="xref" href="ch-yum.html">Chapter 5, <em>Yum</em></a> describes how to use the <span class="application"><strong>Yum</strong></span> package manager to search, install, update, and uninstall packages on the command line.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rpm-usage-examples.html"><strong>Prev</strong>A.4. 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="app-Revision_History.html"><strong>Next</strong>Appendix B. Revision History</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-rpm-usage-examples.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-rpm-usage-examples.html
new file mode 100644
index 0000000..eca6835
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-rpm-usage-examples.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.4. Common Examples of RPM Usage</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-RPM.html" title="Appendix A. RPM" /><link rel="prev" href="s1-check-rpm-sig.html" title="A.3.2. Checking Package Signatures" /><link rel="next" href="s1-rpm-additional-resources.html" title="A.5. 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-check-rpm-sig.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" hr
ef="s1-rpm-additional-resources.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-rpm-usage-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">A.4. Common Examples of RPM Usage</h2></div></div></div><a id="idm261714336224" class="indexterm"></a><a id="idm261714334784" class="indexterm"></a><div class="para">
+ <span class="application"><strong>RPM</strong></span> is a useful tool for both managing your system and diagnosing and fixing problems. See the following examples for an overview of some of the most-used options.
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ To verify your entire system and see what files are missing, issue the following command as <code class="systemitem">root</code>:
+ </div><a id="idm261714329776" class="indexterm"></a><a id="idm261714328368" class="indexterm"></a><pre class="synopsis"><code class="command">rpm -Va</code></pre><div class="para">
+ If some files are missing or appear corrupted, consider reinstalling relevant packages.
+ </div></li><li class="listitem"><div class="para">
+ To determine which package owns a file, enter:
+ </div><a id="idm261714324832" class="indexterm"></a><a id="idm261722133184" class="indexterm"></a><pre class="synopsis"><code class="command">rpm -qf <em class="replaceable"><code>file</code></em></code></pre></li><li class="listitem"><div class="para">
+ To verify the package that owns a particular file, enter as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code class="command">rpm -Vf <em class="replaceable"><code>file</code></em></code></pre></li><li class="listitem"><div class="para">
+ To locate documentation files that are a part of a package to which a file belongs, enter:
+ </div><a id="idm261722127104" class="indexterm"></a><a id="idm261722125664" class="indexterm"></a><a id="idm261722124256" class="indexterm"></a><pre class="synopsis"><code class="command">rpm -qdf <em class="replaceable"><code>file</code></em></code></pre></li><li class="listitem"><div class="para">
+ To find information about a (non-installed) package file, use the following command:
+ </div><a id="idm261722120816" class="indexterm"></a><a id="idm261722119408" class="indexterm"></a><pre class="synopsis"><code class="command">rpm -qip <em class="replaceable"><code>package.rpm</code></em></code></pre></li><li class="listitem"><div class="para">
+ To list files contained in a package, use:
+ </div><a id="idm261728006960" class="indexterm"></a><a id="idm261728005520" class="indexterm"></a><pre class="synopsis"><code class="command">rpm -qlp <em class="replaceable"><code>package.rpm</code></em></code></pre></li></ul></div><div class="para">
+ See the <span class="citerefentry"><span class="refentrytitle">rpm</span>(8)</span> manual page for more options.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-check-rpm-sig.html"><strong>Prev</strong>A.3.2. Checking Package Signatures</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>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-rpm-using.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-rpm-using.html
index 5f487b1..430fb68 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-rpm-using.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-rpm-using.html
@@ -6,26 +6,64 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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_Upgradin
g.html"><strong>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">A.2. Using RPM</h2></div></div></div><div class="para">
- RPM has five basic modes of operation
- <a id="idm225507385072" 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">A.2.1. Finding RPM Packages</h3></div></div></div><a id="idm225507380864" class="indexterm"></a><a id="idm225507379424" 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 Fedora RPM packages, they can be found at the following locations:
+ </script><link rel="home" href="index.html" title="System Administrator's 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="s2-rpm-uninstalling.html" title="A.2.2. Uninstalling Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-RPM.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-rpm-uninstalling.html"><strong>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">A.2. Using RPM</h2></div></div></div><div class="para">
+ <span class="application"><strong>RPM</strong></span> has five basic modes of operation
+ <a id="idm261725488160" class="indexterm"></a>
+ (not counting package building): installing, uninstalling, upgrading, querying, and verifying. This section contains an overview of each mode. For complete details and options, try <code class="command">rpm --help</code> or see <span class="citerefentry"><span class="refentrytitle">rpm</span>(8)</span>. Also, see <a class="xref" href="s1-rpm-additional-resources.html">Section A.5, “Additional Resources”</a> for more information on <span class="application"><strong>RPM</strong></span>.
+ </div><div class="section" id="sec-Installing_and_Upgrading"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">A.2.1. Installing and Upgrading Packages</h3></div></div></div><a id="idm261725482928" class="indexterm"></a><a id="idm261725481488" class="indexterm"></a><a id="idm261718913952" class="indexterm"></a><a id="idm261718912512" class="indexterm"></a><a id="idm261718911072" class="indexterm"></a><div class="para">
+ <span class="application"><strong>RPM</strong></span> packages typically have file names in the following form:
+ </div><pre class="synopsis">package_name-version-release-operating_system-CPU_architecture.rpm</pre><div class="para">
+ For example the <code class="filename">tree-1.7.0-3.fc21.x86_64.rpm</code> file name includes the package name (<code class="filename">tree</code>), version (<code class="filename">1.7.0</code>), release (<code class="filename">3</code>), operating system major version (<code class="filename">fc21</code>) and <acronym class="acronym">CPU</acronym> architecture (<code class="filename">x86_64</code>).
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ When installing a package, ensure it is compatible with your operating system and processor architecture. This can usually be determined by checking the package name. For example, the file name of an <span class="application"><strong>RPM</strong></span> package compiled for the AMD64/Intel 64 computer architectures ends with <code class="filename">x86_64.rpm</code>.
+ </div></div></div><div class="para">
+ The <code class="option">-U</code> (or <code class="option">--upgrade</code>) option has two functions, it can be used to:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- The Fedora installation media
- <a id="idm225447870944" class="indexterm"></a>
- <a id="idm225447869536" class="indexterm"></a>
- contain many installable RPMs.
+ upgrade an existing package on the system to a newer version, or
</div></li><li class="listitem"><div class="para">
- The initial RPM repositories provided with the YUM package manager
- <a id="idm225447867232" class="indexterm"></a>
- <a id="idm225447865824" class="indexterm"></a>
- . See <a class="xref" href="ch-yum.html">Chapter 5, <em>Yum</em></a> for details on how to use the official Fedora package repositories.
- </div></li><li class="listitem"><div class="para">
- The active Fedora mirrors contains many installable RPMs: <a href="http://mirrors.fedoraproject.org/publiclist/">http://mirrors.fedoraproject.org/publiclist/</a>.
- </div></li><li class="listitem"><div class="para">
- Unofficial, third-party repositories not affiliated with The Fedora Project also provide RPM packages.
- </div><div class="important"><div class="admonition_header"><h2>Third-party repositories and package compatibility</h2></div><div class="admonition"><div class="para">
- When considering third-party repositories for use with your Fedora system, pay close attention to the repository's web site with regard to package compatibility before adding the repository as a package source. Alternate package repositories may offer different, incompatible versions of the same software, including packages already included in the Fedora repositories.
- </div></div></div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-RPM.html"><strong>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>
\ No newline at end of file
+ install a package if an older version is not already installed.
+ </div></li></ul></div><div class="para">
+ The <code class="command">rpm -U <em class="replaceable"><code>package.rpm</code></em></code> command is therefore able to either <span class="emphasis"><em>upgrade</em></span> or <span class="emphasis"><em>install</em></span>, depending on the presence of an older version of <em class="replaceable"><code>package.rpm</code></em> on the system.
+ </div><div class="para">
+ Assuming the <code class="filename">tree-1.7.0-3.fc21.x86_64.rpm</code> package is in the current directory, log in as <code class="systemitem">root</code> and type the following command at a shell prompt to either upgrade or install the <span class="package">tree</span> package:
+ </div><pre class="screen">~]# <code class="command">rpm -Uvh tree-1.7.0-3.fc21.x86_64.rpm</code></pre><div class="note" id="note-Use_-Uvh_for_nicely-formatted_RPM_installs"><div class="admonition_header"><h2>Use -Uvh for nicely-formatted RPM installs</h2></div><div class="admonition"><div class="para">
+ The <code class="option">-v</code> and <code class="option">-h</code> options (which are combined with <code class="option">-U</code>) cause <span class="application"><strong>rpm</strong></span> to print more verbose output and display a progress meter using hash signs.
+ </div></div></div><div class="para">
+ If the upgrade or installation is successful, the following output is displayed:
+ </div><pre class="screen">Preparing... ########################################### [100%]
+ 1:tree ########################################### [100%]</pre><div class="warning" id="warning-Always_use_the_-i_install_option_to_install_new_kernel_packages"><div class="admonition_header"><h2>Always use the -i (install) option to install new kernel packages!</h2></div><div class="admonition"><div class="para">
+ <code class="command">rpm</code> provides two different options for installing packages: the aforementioned <code class="option">-U</code> option (which historically stands for <span class="emphasis"><em>upgrade</em></span>), and the <code class="option">-i</code> option (which historically stands for <span class="emphasis"><em>install</em></span>). Because the <code class="option">-U</code> option includes both install and upgrade functions, the use of <code class="command">rpm -Uvh</code> with all packages, <span class="emphasis"><em>except <span class="package">kernel</span> packages</em></span>, is recommended.
+ </div><div class="para">
+ You should always use the <code class="option">-i</code> option to <span class="emphasis"><em>install</em></span> a new kernel package instead of upgrading it. This is because using the <code class="option">-U</code> option to upgrade a kernel package removes the previous (older) kernel package, which could render the system unable to boot if there is a problem with the new kernel. Therefore, use the <code class="command">rpm -i <em class="replaceable"><code>kernel_package</code></em> </code> command to install a new kernel <span class="emphasis"><em>without replacing any older <span class="package">kernel</span> packages</em></span>. For more information on installing <span class="package">kernel</span> packages, see <a class="xref" href="ch-Manually_Upgrading_the_Kernel.html">Chapter 21, <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. If the verification of the signature fails, an error message is displayed.
+ </div><div class="para">
+ If you do not have the appropriate key installed to verify the signature, the message contains the word <code class="computeroutput">NOKEY</code>:
+ </div><pre class="screen">warning: tree-1.7.0-3.fc21.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 431d51: NOKEY</pre><div class="para">
+ See <a class="xref" href="s1-check-rpm-sig.html">Section A.3.2, “Checking Package Signatures”</a> for more information on checking package signatures.
+ </div><div class="section" id="s3-rpm-errors"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">A.2.1.1. Replacing Already-Installed Packages</h4></div></div></div><a id="idm261721457616" class="indexterm"></a><a id="idm261721456176" class="indexterm"></a><div class="para">
+ If a package of the same name and version is already installed, the following output is displayed:
+ </div><pre class="screen">Preparing... ########################################### [100%]
+ package tree-1.7.0-3.fc21.x86_64 is already installed</pre><div class="para">
+ To install the package anyway, use the <code class="option">--replacepkgs</code> option, which tells <span class="application"><strong>RPM</strong></span> to ignore the error:
+ </div><pre class="screen">~]# <code class="command">rpm -Uvh --replacepkgs tree-1.7.0-3.fc21.x86_64.rpm</code></pre><div class="para">
+ This option is helpful if files installed from the package were deleted or if you want the original configuration files to be installed.
+ </div><div class="para">
+ If you attempt an upgrade to an <span class="emphasis"><em>older</em></span> version of a package (that is, if a newer version of the package is already installed), <span class="application"><strong>RPM</strong></span> informs you that a newer version is already installed. To force <span class="application"><strong>RPM</strong></span> to perform the downgrade, use the <code class="command">--oldpackage</code> option:
+ </div><pre class="synopsis"><code class="command">rpm -Uvh --oldpackage <em class="replaceable"><code>older_package.rpm</code></em></code></pre></div><div class="section" id="s3-rpm-conflicting-files"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">A.2.1.2. Resolving File Conflicts</h4></div></div></div><a id="idm261721544576" class="indexterm"></a><a id="idm261721542656" class="indexterm"></a><a id="idm261721541216" class="indexterm"></a><div class="para">
+ If you attempt to install a package that contains a file that has already been installed by another package, a conflict message is displayed. To make <span class="application"><strong>RPM</strong></span> ignore this error, use the <code class="command">--replacefiles</code> option:
+ </div><pre class="synopsis"><code class="command">rpm -Uvh --replacefiles <em class="replaceable"><code>package.rpm</code></em></code></pre></div><div class="section" id="s3-rpm-unresolved-dependency"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">A.2.1.3. Satisfying Unresolved Dependencies</h4></div></div></div><a id="idm261721535728" class="indexterm"></a><a id="idm261721534288" class="indexterm"></a><a id="idm261742074720" class="indexterm"></a><a id="idm261742073280" class="indexterm"></a><div class="para">
+ <span class="application"><strong>RPM</strong></span> packages sometimes depend on other packages, which means that they require other packages to be installed to run properly. If you try to install a package that has an unresolved dependency, a message about a failed dependency is displayed.
+ </div><div class="para">
+ Find the suggested package(s) on the Fedora installation media or on one of the active Fedora mirrors and add it to the installation command. To determine which package contains the required file, use the <code class="option">--whatprovides</code> option:
+ </div><pre class="synopsis"><code class="command">rpm -q --whatprovides "<em class="replaceable"><code>required_file</code></em>"</code></pre><div class="para">
+ If the package that contains <em class="replaceable"><code>required_file</code></em> is in the <span class="application"><strong>RPM</strong></span> database, the name of the package is displayed.
+ </div><div class="warning" id="warning-Forcing_Package_Installation"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Although you can <span class="emphasis"><em>force</em></span> <code class="command">rpm</code> to install a package that has an unresolved dependency (using the <code class="option">--nodeps</code> option), this is <span class="emphasis"><em>not</em></span> recommended and will usually result in the installed software failing to run. Installing packages with <code class="option">--nodeps</code> can cause applications to misbehave or terminate unexpectedly. It can also cause serious package-management problems or system failure. For these reasons, heed the warnings about missing dependencies. The <span class="application"><strong>Yum</strong></span> package manager performs automatic dependency resolution and fetches dependencies from on-line repositories.
+ </div></div></div></div><div class="section" id="sec-Configuration_File_Changes"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">A.2.1.4. Preserving Changes in Configuration Files</h4></div></div></div><a id="idm261742060640" class="indexterm"></a><a id="idm261737782768" class="indexterm"></a><a id="idm261737780880" class="indexterm"></a><div class="para">
+ Because <span class="application"><strong>RPM</strong></span> performs intelligent upgrading of packages with configuration files, you may see the following message:
+ </div><pre class="screen">saving <em class="replaceable"><code>/etc/configuration_file.conf</code></em> as <em class="replaceable"><code>/etc/configuration_file.conf</code></em>.rpmsave</pre><div class="para">
+ This message means that the changes you made to the configuration file may not be <span class="emphasis"><em>forward-compatible</em></span> with the new configuration file in the package, so <span class="application"><strong>RPM</strong></span> saved your original file and installed a new one. You should investigate the differences between the two configuration files and resolve them as soon as possible to ensure that your system continues to function properly.
+ </div><div class="para">
+ Alternatively, <span class="application"><strong>RPM</strong></span> may save the package's <span class="emphasis"><em>new</em></span> configuration file as, for example, <code class="filename"><em class="replaceable"><code>configuration_file.conf</code></em>.rpmnew</code> and leave the configuration file you modified untouched. You should still resolve any conflicts between your modified configuration file and the new one, usually by merging changes from the old one to the new one, for example using the <code class="command">diff</code> program.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-RPM.html"><strong>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="s2-rpm-uninstalling.html"><strong>Next</strong>A.2.2. Uninstalling Packages</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-services-running.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-services-running.html
index a13bbc7..5316eb7 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-services-running.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-services-running.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Services_and_Daemons.html" title="Chapter 6. Services and Daemons" /><link rel="prev" href="ch-Services_and_Daemons.html" title="Chapter 6. Services and Daemons" /><link rel="next" href="s3-services-running-running.html" title="6.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><li 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">6.2. Running Services</h2></div></div></div><a id="idm225505953504" class="indexterm"></a><a id="idm225505951392" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Services_and_Daemons.html" title="Chapter 6. Services and Daemons" /><link rel="prev" href="ch-Services_and_Daemons.html" title="Chapter 6. Services and Daemons" /><link rel="next" href="s3-services-running-running.html" title="6.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><li 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">6.2. Running Services</h2></div></div></div><a id="idm261748804960" class="indexterm"></a><a id="idm261748802848" 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.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-ssh-beyondshell.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-ssh-beyondshell.html
index 9bcdae4..dec1b17 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-ssh-beyondshell.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-ssh-beyondshell.html
@@ -8,7 +8,7 @@
addID('Fedora.21.System_Administrators_Guide');
</script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OpenSSH.html" title="Chapter 7. OpenSSH" /><link rel="prev" href="s2-ssh-clients-sftp.html" title="7.3.3. Using the sftp Utility" /><link rel="next" href="s2-ssh-beyondshell-tcpip.html" title="7.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">7.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">7.4.1. X11 Forwarding</h3></div></div></div><a id="idm225468867472" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-ssh-beyondshell-x11"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.4.1. X11 Forwarding</h3></div></div></div><a id="idm261759578752" 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">USER</code> as a user name, type:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-ssh-clients.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-ssh-clients.html
index 240b680..bee625d 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-ssh-clients.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-ssh-clients.html
@@ -6,9 +6,9 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OpenSSH.html" title="Chapter 7. OpenSSH" /><link rel="prev" href="s2-ssh-configuration-keypairs.html" title="7.2.4. Using Key-based Authentication" /><link rel="next" href="s2-ssh-clients-scp.html" title="7.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 cl
ass="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">7.3. OpenSSH Clients</h2></div></div></div><a id="idm225458390720" 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">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OpenSSH.html" title="Chapter 7. OpenSSH" /><link rel="prev" href="s2-ssh-configuration-keypairs.html" title="7.2.4. Using Key-based Authentication" /><link rel="next" href="s2-ssh-clients-scp.html" title="7.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 cl
ass="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">7.3. OpenSSH Clients</h2></div></div></div><a id="idm261749216432" 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> package installed. See <a class="xref" href="sec-Installing.html">Section 5.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">7.3.1. Using the ssh Utility</h3></div></div></div><a id="idm225473475472" class="indexterm"></a><a id="idm225473473872" class="indexterm"></a><div class="para">
+ </div></div></div><div class="section" id="s2-ssh-clients-ssh"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">7.3.1. Using the ssh Utility</h3></div></div></div><a id="idm261749211328" class="indexterm"></a><a id="idm261760350240" class="indexterm"></a><div class="para">
The <code class="command">ssh</code> utility allows you to log in to a remote machine and execute commands there. It is a secure replacement for the <code class="command">rlogin</code>, <code class="command">rsh</code>, and <code class="command">telnet</code> programs.
</div><div class="para">
Similarly to the <code class="command">telnet</code> command, log in to a remote machine by using the following command:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-ssh-configuration.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-ssh-configuration.html
index 7685134..babae9a 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-ssh-configuration.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-ssh-configuration.html
@@ -8,9 +8,9 @@
addID('Fedora.21.System_Administrators_Guide');
</script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OpenSSH.html" title="Chapter 7. OpenSSH" /><link rel="prev" href="ch-OpenSSH.html" title="Chapter 7. OpenSSH" /><link rel="next" href="s2-ssh-configuration-sshd.html" title="7.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-con
figuration-sshd.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">7.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">7.2.1. Configuration Files</h3></div></div></div><a id="idm225480760288" class="indexterm"></a><div class="para">
+ </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">7.2.1. Configuration Files</h3></div></div></div><a id="idm261756249712" 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="idm225480756512" class="indexterm"></a><a id="idm225447421872" class="indexterm"></a><div class="para">
+ </div><a id="idm261756245936" class="indexterm"></a><a id="idm261761770080" class="indexterm"></a><div class="para">
System-wide SSH configuration information is stored in the <code class="filename">/etc/ssh/</code> directory as described in <a class="xref" href="s1-ssh-configuration.html#table-ssh-configuration-configs-system">Table 7.1, “System-wide configuration files”</a>. User-specific SSH configuration information is stored in <code class="filename">~/.ssh/</code> within the user's home directory as described in <a class="xref" href="s1-ssh-configuration.html#table-ssh-configuration-configs-user">Table 7.2, “User-specific configuration files”</a>.
</div><div class="table" id="table-ssh-configuration-configs-system"><h6>Table 7.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 class="">
File
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-structured_logging_with_rsyslog.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-structured_logging_with_rsyslog.html
new file mode 100644
index 0000000..c3f68e3
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-structured_logging_with_rsyslog.html
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.6. Structured Logging with Rsyslog</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's 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-interaction_of_rsyslog_and_journal.html" title="17.5. Interaction of Rsyslog and Journal" /><link rel="next" href="s2-filtering_structured_messages.html" title="17.6.2. Filtering Structured Messages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="
p" href="s1-interaction_of_rsyslog_and_journal.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-filtering_structured_messages.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-structured_logging_with_rsyslog"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.6. Structured Logging with Rsyslog</h2></div></div></div><div class="para">
+ On systems that produce large amounts of log data, it can be convenient to maintain log messages in a <span class="emphasis"><em>structured format</em></span>. With structured messages, it is easier to search for particular information, to produce statistics and to cope with changes and inconsistencies in message structure. <span class="application"><strong>Rsyslog</strong></span> uses the <span class="emphasis"><em>JSON</em></span> (JavaScript Object Notation) format to provide structure for log messages.
+ </div><div class="para">
+ Compare the following unstructured log message:
+ </div><pre class="synopsis">Oct 25 10:20:37 localhost anacron[1395]: Jobs will be executed sequentially</pre><div class="para">
+ with a structured one:
+ </div><pre class="synopsis">{"timestamp":"2013-10-25T10:20:37", "host":"localhost", "program":"anacron", "pid":"1395", "msg":"Jobs will be executed sequentially"}</pre><div class="para">
+ Searching structured data with use of key-value pairs is faster and more precise than searching text files with regular expressions. The structure also lets you to search for the same entry in messages produced by various applications. Also, JSON files can be stored in a document database such as <span class="database">MongoDB</span>, which provides additional performance and analysis capabilities. On the other hand, a structured message requires more disk space than the unstructured one.
+ </div><div class="para">
+ In <span class="application"><strong>rsyslog</strong></span>, log messages with meta data are pulled from <span class="application"><strong>Journal</strong></span> with use of the <code class="systemitem">imjournal</code> module. With the <code class="systemitem">mmjsonparse</code> module, you can parse data imported from <span class="application"><strong>Journal</strong></span> and from other sources and process them further, for example as a database output. For parsing to be successful, <code class="systemitem">mmjsonparse</code> requires input messages to be structured in a way that is defined by the <span class="bold bold"><strong>Lumberjack</strong></span> project.
+ </div><div class="para">
+ The <span class="bold bold"><strong>Lumberjack</strong></span> project aims to add structured logging to <span class="application"><strong>rsyslog</strong></span> in a backward-compatible way. To identify a structured message, <span class="bold bold"><strong>Lumberjack</strong></span> specifies the <span class="bold bold"><strong>@cee:</strong></span> string that prepends the actual JSON structure. Also, <span class="bold bold"><strong>Lumberjack</strong></span> defines the list of standard field names that should be used for entities in the JSON string. For more information on <span class="bold bold"><strong>Lumberjack</strong></span>, see <a class="xref" href="s1-log-files-additional-resources.html#brid-Log_Files-Resources-Online">the section called “Online Documentation”</a>.
+ </div><div class="para">
+ The following is an example of a lumberjack-formatted message:
+ </div><pre class="synopsis"> @cee: {"pid":17055, "uid":1000, "gid":1000, "appname":"logger", "msg":"Message text."} </pre><div class="para">
+ To build this structure inside <span class="application"><strong>Rsyslog</strong></span>, a template is used, see <a class="xref" href="s2-filtering_structured_messages.html">Section 17.6.2, “Filtering Structured Messages”</a>. Applications and servers can employ the <code class="systemitem">libumberlog</code> library to generate messages in the lumberjack-compliant form. For more information on <code class="systemitem">libumberlog</code>, see <a class="xref" href="s1-log-files-additional-resources.html#brid-Log_Files-Resources-Online">the section called “Online Documentation”</a>.
+ </div><div class="section" id="s2-importing_data_from_journal"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.6.1. Importing Data from Journal</h3></div></div></div><div class="para">
+ The <code class="command">imjournal</code> module is <span class="application"><strong>Rsyslog</strong></span>'s input module to natively read the journal files (see <a class="xref" href="s1-interaction_of_rsyslog_and_journal.html">Section 17.5, “Interaction of Rsyslog and Journal”</a>). Journal messages are then logged in text format as other rsyslog messages. However, with further processing, it is possible to translate meta data provided by <span class="application"><strong>Journal</strong></span> into a structured message.
+ </div><div class="para">
+ To import data from <span class="application"><strong>Journal</strong></span> to <span class="application"><strong>Rsyslog</strong></span>, use the following configuration in <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imjournal
+
+$imjournalPersistStateInterval <em class="replaceable"><code>number_of_messages</code></em>
+$imjournalStateFile <em class="replaceable"><code>path</code></em>
+$imjournalRatelimitInterval <em class="replaceable"><code>seconds</code></em>
+$imjournalRatelimitBurst <em class="replaceable"><code>burst_number</code></em>
+$ImjournalIgnorePreviousMessages <em class="replaceable"><code>off/on</code></em>
+</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ With <em class="replaceable"><code>number_of_messages</code></em>, you can specify how often the journal data must be saved. This will happen each time the specified number of messages is reached.
+ </div></li><li class="listitem"><div class="para">
+ Replace <em class="replaceable"><code>path</code></em> with a path to the state file. This file tracks the journal entry that was the last one processed.
+ </div></li><li class="listitem"><div class="para">
+ With <em class="replaceable"><code>seconds</code></em>, you set the length of the rate limit interval. The number of messages processed during this interval can not exceed the value specified in <em class="replaceable"><code>burst_number</code></em>. The default setting is 20,000 messages per 600 seconds. Rsyslog discards messages that come after the maximum burst within the time frame specified.
+ </div></li><li class="listitem"><div class="para">
+ With <code class="option">$ImjournalIgnorePreviousMessages</code> you can ignore messages that are currently in Journal and import only new messages, which is used when there is no state file specified. The default setting is <code class="literal">off</code>. Please note that if this setting is off and there is no state file, all messages in the Journal are processed, even if they were already processed in a previous rsyslog session.
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ You can use <code class="systemitem">imjournal</code> simultaneously with <code class="systemitem">imuxsock</code> module that is the traditional system log input. However, to avoid message duplication, you must prevent <code class="systemitem">imuxsock</code> from reading the Journal's system socket. To do so, use the <code class="option">$OmitLocalLogging</code> directive:
+ </div><pre class="screen">
+$ModLoad imuxsock
+$ModLoad imjournal
+
+$OmitLocalLogging on
+$AddUnixListenSocket /run/systemd/journal/syslog
+</pre></div></div><div class="para">
+ You can translate all data and meta data stored by <span class="application"><strong>Journal</strong></span> into structured messages. Some of these meta data entries are listed in <a class="xref" href="s1-Using_the_Journal.html#ex-verbose_journalctl_output">Example 17.16, “Verbose journalctl Output”</a>, for a complete list of journal fields see the <code class="filename">systemd.journal-fields(7)</code> manual page. For example, it is possible to focus on <span class="emphasis"><em>kernel journal fields</em></span>, that are used by messages originating in the kernel.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-interaction_of_rsyslog_and_journal.html"><strong>Prev</strong>17.5. Interaction of Rsyslog and Journal</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-filtering_structured_messages.html"><strong>Next</strong>17.6.2. Filtering Structured Messages</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-cpu.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-cpu.html
index 6be965e..7159eeb 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-cpu.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-cpu.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-System_Monitoring_Tools.html" title="Chapter 16. System Monitoring Tools" /><link rel="prev" href="s2-sysinfo-memory-usage-system_monitor.html" title="16.2.2. Using the System Monitor Tool" /><link rel="next" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo
-memory-usage-system_monitor.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-sysinfo-filesystems.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-sysinfo-cpu"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.3. Viewing CPU Usage</h2></div></div></div><a id="idm225479709280" class="indexterm"></a><a id="idm225479707840" class="indexterm"></a><div class="section" id="s2-sysinfo-cpu-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.3.1. Using the System Monitor Tool</h3></div></div></div><a id="idm225479705952" class="indexterm"></a><a id="idm225479704832" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-System_Monitoring_Tools.html" title="Chapter 16. System Monitoring Tools" /><link rel="prev" href="s2-sysinfo-memory-usage-system_monitor.html" title="16.2.2. Using the System Monitor Tool" /><link rel="next" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo
-memory-usage-system_monitor.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-sysinfo-filesystems.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-sysinfo-cpu"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">16.3. Viewing CPU Usage</h2></div></div></div><a id="idm261756812272" class="indexterm"></a><a id="idm261756810832" class="indexterm"></a><div class="section" id="s2-sysinfo-cpu-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.3.1. Using the System Monitor Tool</h3></div></div></div><a id="idm261746442624" class="indexterm"></a><a id="idm261746441504" class="indexterm"></a><div class="para">
The <span class="guilabel"><strong>Resources</strong></span> tab of the <span class="application"><strong>System Monitor</strong></span> tool allows you to view the current CPU usage on the system.
</div><div class="para">
To start the <span class="application"><strong>System Monitor</strong></span> tool, either select <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Monitor</strong></span> from the <span class="guimenu"><strong>Activities</strong></span> menu, or type <code class="command">gnome-system-monitor</code> at a shell prompt. Then click the <span class="guilabel"><strong>Resources</strong></span> tab to view the system's CPU usage.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-filesystems.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-filesystems.html
index 29106ff..2eda740 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-filesystems.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-filesystems.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-System_Monitoring_Tools.html" title="Chapter 16. System Monitoring Tools" /><link rel="prev" href="s1-sysinfo-cpu.html" title="16.3. Viewing CPU Usage" /><link rel="next" href="s2-sysinfo-filesystems-blkid.html" title="16.4.2. Using the blkid Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-cpu.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-sysinfo-filesystems-blkid.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">16.4. Viewing Block Devices and File Systems</h2></div></div></div><a id="idm225464795952" class="indexterm"></a><a id="idm225464794512" class="indexterm"></a><div class="section" id="s2-sysinfo-filesystems-lsblk"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.1. Using the lsblk Command</h3></div></div></div><a id="idm225464792592" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-System_Monitoring_Tools.html" title="Chapter 16. System Monitoring Tools" /><link rel="prev" href="s1-sysinfo-cpu.html" title="16.3. Viewing CPU Usage" /><link rel="next" href="s2-sysinfo-filesystems-blkid.html" title="16.4.2. Using the blkid Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-cpu.html"><strong>Prev</strong></a></li><li
class="next"><a accesskey="n" href="s2-sysinfo-filesystems-blkid.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">16.4. Viewing Block Devices and File Systems</h2></div></div></div><a id="idm261728976112" class="indexterm"></a><a id="idm261728974672" class="indexterm"></a><div class="section" id="s2-sysinfo-filesystems-lsblk"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.1. Using the lsblk Command</h3></div></div></div><a id="idm261732234368" class="indexterm"></a><div class="para">
The <code class="command">lsblk</code> command allows you to display a list of available block devices. To do so, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">lsblk</code></pre><div class="para">
For each listed block device, the <code class="command">lsblk</code> command displays the device name (<code class="computeroutput">NAME</code>), major and minor device number (<code class="computeroutput">MAJ:MIN</code>), if the device is removable (<code class="computeroutput">RM</code>), what is its size (<code class="computeroutput">SIZE</code>), if the device is read-only (<code class="computeroutput">RO</code>), what type is it (<code class="computeroutput">TYPE</code>), and where the device is mounted (<code class="computeroutput">MOUNTPOINT</code>). For example:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-hardware.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-hardware.html
index 7454d57..2323dc5 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-hardware.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-hardware.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-System_Monitoring_Tools.html" title="Chapter 16. System Monitoring Tools" /><link rel="prev" href="s2-sysinfo-filesystems-system_monitor.html" title="16.4.7. Using the System Monitor Tool" /><link rel="next" href="s2-sysinfo-hardware-lsusb.html" title="16.5.2. Using the lsusb Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-filesystem
s-system_monitor.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-hardware-lsusb.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">16.5. Viewing Hardware Information</h2></div></div></div><a id="idm225452612144" class="indexterm"></a><a id="idm225452610704" class="indexterm"></a><div class="section" id="s2-sysinfo-hardware-lspci"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.1. Using the lspci Command</h3></div></div></div><a id="idm225452608192" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-System_Monitoring_Tools.html" title="Chapter 16. System Monitoring Tools" /><link rel="prev" href="s2-sysinfo-filesystems-system_monitor.html" title="16.4.7. Using the System Monitor Tool" /><link rel="next" href="s2-sysinfo-hardware-lsusb.html" title="16.5.2. Using the lsusb Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-filesystem
s-system_monitor.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-hardware-lsusb.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">16.5. Viewing Hardware Information</h2></div></div></div><a id="idm261714237616" class="indexterm"></a><a id="idm261714236176" class="indexterm"></a><div class="section" id="s2-sysinfo-hardware-lspci"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.1. Using the lspci Command</h3></div></div></div><a id="idm261714233664" class="indexterm"></a><div class="para">
The <code class="command">lspci</code> command lists all PCI devices that are present in the system:
</div><pre class="synopsis"><code class="command">lspci</code></pre><div class="para">
For example:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-memory-usage.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-memory-usage.html
index c947f1b..f6281c2 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-memory-usage.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-sysinfo-memory-usage.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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="s2-sysinfo-memory-usage-system_monitor.html" title="16.2.2. Using the System Monitor Tool" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-System_Moni
toring_Tools.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-memory-usage-system_monitor.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">16.2. Viewing Memory Usage</h2></div></div></div><a id="idm225474446576" class="indexterm"></a><a id="idm225474445136" class="indexterm"></a><a id="idm225474444176" class="indexterm"></a><div class="section" id="s2-sysinfo-memory-usage-free"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.2.1. Using the free Command</h3></div></div></div><a id="idm225474442256" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's 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="s2-sysinfo-memory-usage-system_monitor.html" title="16.2.2. Using the System Monitor Tool" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-System_Moni
toring_Tools.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-memory-usage-system_monitor.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">16.2. Viewing Memory Usage</h2></div></div></div><a id="idm261718485600" class="indexterm"></a><a id="idm261718484160" class="indexterm"></a><a id="idm261718483200" class="indexterm"></a><div class="section" id="s2-sysinfo-memory-usage-free"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.2.1. Using the free Command</h3></div></div></div><a id="idm261754159488" class="indexterm"></a><div class="para">
The <code class="command">free</code> command allows you to display the amount of free and used memory on the system. To do so, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">free</code></pre><div class="para">
The <code class="command">free</code> command provides information about both the physical memory (<code class="computeroutput">Mem</code>) and swap space (<code class="computeroutput">Swap</code>). It displays the total amount of memory (<code class="computeroutput">total</code>), as well as the amount of memory that is in use (<code class="computeroutput">used</code>), free (<code class="computeroutput">free</code>), shared (<code class="computeroutput">shared</code>), in kernel buffers (<code class="computeroutput">buffers</code>), and cached (<code class="computeroutput">cached</code>). For example:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-users-configui.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-users-configui.html
index a9a1ced..01483ca 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-users-configui.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-users-configui.html
@@ -1,15 +1,19 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2. Using the 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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.2. Managing Users in a Graphical Environment</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Managing_Users_and_Groups.html" title="Chapter 4. Managing Users and Groups" /><link rel="prev" href="ch-Managing_Users_and_Groups.html" title="Chapter 4. Managing Users and Groups" /><link rel="next" href="s1-users-tools.html" title="4.3. Using Command Line 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="ch-Managing_Users_and_Groups.html"><stro
ng>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="s1-users-configui"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Using the User Manager Tool</h2></div></div></div><a id="idm225468890752" class="indexterm"></a><a id="idm225468889312" class="indexterm"></a><a id="idm225456667584" class="indexterm"></a><a id="idm225456666016" class="indexterm"></a><a id="idm225456664576" class="indexterm"></a><a id="idm225456663136" class="indexterm"></a><div class="para">
- The <span class="application"><strong>User</strong></span> utility allows you to view, modify, add, and delete local users in the graphical user interface.
- </div><div class="section" id="s2-redhat-config-users-list"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.2.1. Viewing Users and Groups</h3></div></div></div><div class="para">
- Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">Users</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Users</strong></span> utility appears. The <span class="keycap"><strong>Super</strong></span> key appears in a variety of guises, depending on the keyboard and other hardware, but often as either the Windows or Command key, and typically to the left of the Spacebar.
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Managing_Users_and_Groups.html" title="Chapter 4. Managing Users and Groups" /><link rel="prev" href="ch-Managing_Users_and_Groups.html" title="Chapter 4. Managing Users and Groups" /><link rel="next" href="s1-users-tools.html" title="4.3. Using Command Line 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="ch-Managing_Users_and_Groups.html"><stro
ng>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="s1-users-configui"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.2. Managing Users in a Graphical Environment</h2></div></div></div><a id="idm261714513520" class="indexterm"></a><a id="idm261738163808" class="indexterm"></a><a id="idm261738162368" class="indexterm"></a><a id="idm261738160928" class="indexterm"></a><a id="idm261738159488" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Users</strong></span> utility allows you to view, modify, add, and delete local users in the graphical user interface.
+ </div><div class="section" id="s2-redhat-config-users-list"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.2.1. Using the Users Settings Tool</h3></div></div></div><div class="para">
+ Press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">Users</code> and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Users</strong></span> settings tool appears. The <span class="keycap"><strong>Super</strong></span> key appears in a variety of guises, depending on the keyboard and other hardware, but often as either the Windows or Command key, and typically to the left of the Spacebar.
</div><div class="para">
- To make changes to the user accounts first select the <span class="guibutton"><strong>Unlock</strong></span> button and authenticate yourself as indicated by the dialog box that appears. Note that unless you have superuser privileges, the application will prompt you to authenticate as <code class="systemitem">root</code>. To add and remove users select the <span class="guibutton"><strong>+</strong></span> and <span class="guibutton"><strong>-</strong></span> button respectively. To edit a users language setting, select the language and a drop-down menu appears.
+ To make changes to the user accounts, first select the <span class="guibutton"><strong>Unlock</strong></span> button and authenticate yourself as indicated by the dialog box that appears. Note that unless you have superuser privileges, the application will prompt you to authenticate as <code class="systemitem">root</code>. To add and remove users, select the <span class="guibutton"><strong>+</strong></span> and <span class="guibutton"><strong>-</strong></span> button respectively. To add a user to the administrative group <code class="systemitem">wheel</code>, change the <span class="guimenu"><strong>Account Type</strong></span> from <code class="literal">Standard</code> to <code class="literal">Administrator</code>. To edit a user's language setting, select the language and a drop-down menu appears.
+ </div><div class="figure" id="fig-managing-users"><div class="figure-contents"><div class="mediaobject" id="mediaobj-managing-users"><img src="images/managing_users.png" alt="The Users Settings Tool" /><div class="longdesc"><div class="para">
+ The <span class="application"><strong>Users</strong></span> settings tool
+ </div></div></div></div><h6>Figure 4.1. The Users Settings Tool</h6></div><br class="figure-break" /><div class="para">
+ When a new user is created, the account is disabled until a password is set. The <span class="guimenu"><strong>Add User</strong></span> menu contains the options to set a password by the administrator immediately, or to allow the user to choose a password at the first login.
</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Managing_Users_and_Groups.html"><strong>Prev</strong>Chapter 4. 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="s1-users-tools.html"><strong>Next</strong>4.3. Using Command Line Tools</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-users-tools.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-users-tools.html
index 07f3416..4a37115 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-users-tools.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-users-tools.html
@@ -6,13 +6,17 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Managing_Users_and_Groups.html" title="Chapter 4. Managing Users and Groups" /><link rel="prev" href="s1-users-configui.html" title="4.2. Using the User Manager Tool" /><link rel="next" href="s2-users-tools-groups-add.html" title="4.3.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="s1-users-configui.html"><strong>Prev</strong></a>
</li><li class="next"><a accesskey="n" href="s2-users-tools-groups-add.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">4.3. Using Command Line Tools</h2></div></div></div><a id="idm225475588720" class="indexterm"></a><a id="idm225475586640" class="indexterm"></a><a id="idm225475584560" class="indexterm"></a><a id="idm225461844400" class="indexterm"></a><div class="para">
- The easiest way to manage users and groups on Fedora is to use the <span class="application"><strong>User Manager</strong></span> application as described in <a class="xref" href="s1-users-configui.html">Section 4.2, “Using the User Manager Tool”</a>. However, if you prefer command line tools or do not have the X Window System installed, you can use command line utilities that are listed in <a class="xref" href="s1-users-tools.html#table-users-tools">Table 4.1, “Command line utilities for managing users and groups”</a>.
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Managing_Users_and_Groups.html" title="Chapter 4. Managing Users and Groups" /><link rel="prev" href="s1-users-configui.html" title="4.2. Managing Users in a Graphical Environment" /><link rel="next" href="s2-users-tools-groups-add.html" title="4.3.2. 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="s1-users-configui.html"><strong>Pre
v</strong></a></li><li class="next"><a accesskey="n" href="s2-users-tools-groups-add.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">4.3. Using Command Line Tools</h2></div></div></div><a id="idm261758402592" class="indexterm"></a><a id="idm261758400512" class="indexterm"></a><a id="idm261755544704" class="indexterm"></a><div class="para">
+ Apart from the <span class="application"><strong>Users</strong></span> settings tool described in <a class="xref" href="s1-users-configui.html">Section 4.2, “Managing Users in a Graphical Environment”</a>, which is designed for basic managing of users, you can use command line tools for managing users and groups that are listed in <a class="xref" href="s1-users-tools.html#table-users-tools">Table 4.1, “Command line utilities for managing users and groups”</a>.
</div><div class="table" id="table-users-tools"><h6>Table 4.1. Command line utilities for managing users and groups</h6><div class="table-contents"><table summary="Command line utilities for managing users and groups" border="1"><colgroup><col width="35%" class="utilities" /><col width="65%" class="description" /></colgroup><thead><tr><th class="">
Utilities
</th><th class="">
Description
</th></tr></thead><tbody><tr><td class="">
+ <code class="command">id</code>
+ </td><td class="">
+ Displays user and group IDs.
+ </td></tr><tr><td class="">
<code class="command">useradd</code>, <code class="command">usermod</code>, <code class="command">userdel</code>
</td><td class="">
Standard utilities for adding, modifying, and deleting user accounts.
@@ -32,15 +36,19 @@
<code class="command">pwconv</code>, <code class="command">pwunconv</code>
</td><td class="">
Utilities that can be used for the conversion of passwords to shadow passwords, or back from shadow passwords to standard passwords.
- </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="s2-users-tools-users-add"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.1. Adding a New User</h3></div></div></div><a id="idm225468065600" class="indexterm"></a><a id="idm225468063872" class="indexterm"></a><a id="idm225468062432" class="indexterm"></a><div class="para">
- To add a new user to the system, typing the following at a shell prompt as <code class="systemitem">root</code>:
+ </td></tr><tr><td class="">
+ <code class="command">grpconv</code>, <code class="command">grpunconv</code>
+ </td><td class="">
+ Similar to the previous, these utilities can be used for conversion of shadowed information for group accounts.
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="section" id="s2-users-tools-users-add"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.1. Adding a New User</h3></div></div></div><a id="idm261734694656" class="indexterm"></a><a id="idm261734692928" class="indexterm"></a><a id="idm261734691488" class="indexterm"></a><div class="para">
+ To add a new user to the system, type the following at a shell prompt as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">useradd</code> [<span class="optional"><em class="replaceable"><code>options</code></em></span>] <em class="replaceable"><code>username</code></em></pre><div class="para">
- …where <em class="replaceable"><code>options</code></em> are command line options as described in <a class="xref" href="s1-users-tools.html#table-useradd-options">Table 4.2, “useradd command line options”</a>.
- </div><a id="idm225493085008" class="indexterm"></a><div class="para">
+ …where <em class="replaceable"><code>options</code></em> are command-line options as described in <a class="xref" href="s1-users-tools.html#table-useradd-options">Table 4.2, “Common useradd command-line options”</a>.
+ </div><a id="idm261751983600" class="indexterm"></a><div class="para">
By default, the <code class="command">useradd</code> command creates a locked user account. To unlock the account, run the following command as <code class="systemitem">root</code> to assign a password:
</div><pre class="synopsis"><code class="command">passwd</code> <em class="replaceable"><code>username</code></em></pre><div class="para">
- Optionally, you can set password aging policy. See <a class="xref" href="s2-users-tools-password-aging.html">Section 4.3.3, “Enabling Password Aging”</a> for information on how to enable password aging.
- </div><div class="table" id="table-useradd-options"><h6>Table 4.2. useradd command line options</h6><div class="table-contents"><table summary="useradd command line options" border="1"><colgroup><col width="30%" class="option" /><col width="70%" class="description" /></colgroup><thead><tr><th class="">
+ Optionally, you can set a password aging policy. See <a class="xref" href="s2-users-tools-password-aging.html">Section 4.3.3, “Enabling Password Aging”</a> for information on how to enable password aging.
+ </div><div class="table" id="table-useradd-options"><h6>Table 4.2. Common useradd command-line options</h6><div class="table-contents"><table summary="Common useradd command-line options" border="1"><colgroup><col width="30%" class="option" /><col width="70%" class="description" /></colgroup><thead><tr><th class="">
Option
</th><th class="">
Description
@@ -59,15 +67,15 @@
</td></tr><tr><td class="">
<code class="option">-f</code> <em class="replaceable"><code>days</code></em>
</td><td class="">
- Number of days after the password expires until the account is disabled. If <code class="literal">0</code> is specified, the account is disabled immediately after the password expires. If <code class="literal">-1</code> is specified, the account is not be disabled after the password expires.
+ Number of days after the password expires until the account is disabled. If <code class="literal">0</code> is specified, the account is disabled immediately after the password expires. If <code class="literal">-1</code> is specified, the account is not disabled after the password expires.
</td></tr><tr><td class="">
<code class="option">-g</code> <em class="replaceable"><code>group_name</code></em>
</td><td class="">
- Group name or group number for the user's default group. The group must exist prior to being specified here.
+ Group name or group number for the user's default (primary) group. The group must exist prior to being specified here.
</td></tr><tr><td class="">
<code class="option">-G</code> <em class="replaceable"><code>group_list</code></em>
</td><td class="">
- List of additional (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.
+ List of additional (supplementary, other than default) group names or group numbers, separated by commas, of which the user is a member. The groups must exist prior to being specified here.
</td></tr><tr><td class="">
<code class="option">-m</code>
</td><td class="">
@@ -96,7 +104,9 @@
<code class="option">-u</code> <em class="replaceable"><code>uid</code></em>
</td><td class="">
User ID for the user, which must be unique and greater than 999.
- </td></tr></tbody></table></div></div><br class="table-break" /><h4 id="bh-users-tools-users-add-explanation"> Explaining the Process </h4><div class="para">
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The command-line options associated with the <code class="command">usermod</code> command are essentially the same. Note that if you want to add a user to another supplementary group, you need to use the <code class="option">-a, --append</code> option with the <code class="option">-G</code> option. Otherwise the list of supplementary groups for the user will be overwritten by those specified with the <code class="command">usermod -G</code> command.
+ </div><h4 id="bh-users-tools-users-add-explanation"> Explaining the Process </h4><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>:
@@ -139,7 +149,7 @@
</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>.
+ The GID matches the one listed for <code class="systemitem">juan</code>'s primary group in <code class="filename">/etc/passwd</code>.
</div></li></ul></div></li><li class="step"><div class="para">
A new line for a group named <code class="systemitem">juan</code> is created in <code class="filename">/etc/gshadow</code>:
</div><pre class="programlisting">juan:!::</pre><div class="para">
@@ -152,20 +162,18 @@
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">
+ </div><pre class="screen">~]# <code class="command">ls -ld /home/juan</code>
+drwx------. 4 juan juan 4096 Mar 3 18:23 /home/juan</pre><div class="para">
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. The contents of <code class="filename">/etc/skel/</code> may vary depending on installed applications.
+ The files within the <code class="filename">/etc/skel/</code> directory (which contain default user settings) are copied into the new <code class="filename">/home/juan/</code> directory. The contents of <code class="filename">/etc/skel/</code> may vary depending on installed applications:
</div><pre class="screen">~]# <code class="command">ls -la /home/juan</code>
-total 28
+total 24
drwx------. 4 juan juan 4096 Mar 3 18:23 .
drwxr-xr-x. 5 root root 4096 Mar 3 18:23 ..
-rw-r--r--. 1 juan juan 18 Jul 09 08:43 .bash_logout
-rw-r--r--. 1 juan juan 176 Jul 09 08:43 .bash_profile
-rw-r--r--. 1 juan juan 124 Jul 09 08:43 .bashrc
-drwxr-xr-x. 4 juan juan 4096 Jul 09 08:43 .mozilla
--rw-r--r--. 1 juan juan 658 Jul 09 08:43 .zshrc</pre></li></ol></div><div class="para">
+drwxr-xr-x. 4 juan juan 4096 Jul 09 08:43 .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><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-configui.html"><strong>Prev</strong>4.2. Using the 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-users-tools-groups-add.html"><strong>Next</strong>4.3.2. Adding a New Group</a></li></ul></body></html>
\ No newline at end of file
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-users-configui.html"><strong>Prev</strong>4.2. Managing Users in a Graphical Environment</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-users-tools-groups-add.html"><strong>Next</strong>4.3.2. Adding a New Group</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-using-operf.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-using-operf.html
new file mode 100644
index 0000000..256e12a
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-using-operf.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2. Using operf</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="prev" href="ch-OProfile.html" title="Chapter 19. OProfile" /><link rel="next" href="s2-operf-events.html" title="19.2.2. Setting Events to Monitor" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-OProfile.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-operf-even
ts.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-using-operf"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">19.2. Using operf</h2></div></div></div><div class="para">
+ <code class="command">operf</code> is the recommended profiling mode that does not require initial setup before starting. All settings are specified as command-line options and there is no separate command to start the profiling process. To stop <code class="command">operf</code>, press Ctrl+C. The typical <code class="command">operf</code> command syntax looks as follows:
+ </div><pre class="synopsis"><code class="command">operf</code> <em class="replaceable"><code>options</code></em> <em class="replaceable"><code>range</code></em> <em class="replaceable"><code>command</code></em> <em class="replaceable"><code>args</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>options</code></em> with the desired command-line options to specify your profiling settings. Full set of options is described in <code class="systemitem">operf(1)</code> manual page. Replace <em class="replaceable"><code>range</code></em> with one of the following:
+ </div><div class="para">
+ <code class="option">--system-wide</code> - this setting allows for global profiling, see <a class="xref" href="s1-using-operf.html#using_operf_system-wide">Using <code class="command">operf</code> in System-wide Mode</a>
+ </div><div class="para">
+ <code class="option">--pid=<em class="replaceable"><code>PID</code></em></code> - this is to profile a running application, where <em class="replaceable"><code>PID</code></em> is the process ID of the process you want to profile.
+ </div><div class="para">
+ With <em class="replaceable"><code>command</code></em> and <em class="replaceable"><code>args</code></em>, you can define a specific command or application to be profiled, and also the input arguments that this command or application requires. Either <em class="replaceable"><code>command</code></em>, <code class="option">--pid</code> or <code class="option">--system-wide</code> is required, but these cannot be used simultaneously.
+ </div><div class="para">
+ When you invoke <code class="command">operf</code> on a command line without setting the <em class="replaceable"><code>range</code></em> option, data will be collected for the children processes.
+ </div><div class="note" id="using_operf_system-wide"><div class="admonition_header"><h2>Using <code class="command">operf</code> in System-wide Mode</h2></div><div class="admonition"><div class="para">
+ To run <code class="command">operf</code> <code class="option">--system-wide</code>, you need <code class="systemitem">root</code> authority. When finished profiling, you can stop <code class="command">operf</code> with <code class="literal">Ctrl+C</code>.
+ </div><div class="para">
+ If you run <code class="command">operf</code> <code class="option">--system-wide</code> as a background process (with <code class="literal">&</code>), stop it in a controlled manner in order to process the collected profile data. For this purpose, use:
+ </div><pre class="synopsis"><code class="command">kill -SIGINT operf-PID </code></pre><div class="para">
+ When running <code class="command">operf</code> <code class="option">--system-wide</code>, it is recommended that your current working directory is <code class="filename">/root</code> or a subdirectory of <code class="filename">/root</code> so that sample data files are not stored in locations accessible by regular users.
+ </div></div></div><div class="section" id="s2-operf-kernel"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.1. Specifying the Kernel</h3></div></div></div><div class="para">
+ To monitor the kernel, execute the following command:
+ </div><pre class="synopsis"><code class="command">operf</code> <code class="option">--vmlinux</code>=<em class="replaceable"><code>vmlinux_path</code></em></pre><div class="para">
+ With this option, you can specify a path to a vmlinux file that matches the running kernel. Kernel samples will be attributed to this binary, allowing post-processing tools to attribute samples to the appropriate kernel symbols. If this option is not specified, all kernel samples will be attributed to a pseudo binary named "no-vmlinux".
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-OProfile.html"><strong>Prev</strong>Chapter 19. OProfile</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-operf-events.html"><strong>Next</strong>19.2.2. Setting Events to Monitor</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-using_rsyslog_modules.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-using_rsyslog_modules.html
new file mode 100644
index 0000000..d1fc96e
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-using_rsyslog_modules.html
@@ -0,0 +1,77 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.4. Using Rsyslog Modules</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Viewing_and_Managing_Log_Files.html" title="Chapter 17. Viewing and Managing Log Files" /><link rel="prev" href="s2-managing_queues.html" title="17.3.2. Managing Queues" /><link rel="next" href="s2-exporting_messages_to_a_database.html" title="17.4.2. Exporting Messages to a Database" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-managing_queues.ht
ml"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-exporting_messages_to_a_database.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-using_rsyslog_modules"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.4. Using Rsyslog Modules</h2></div></div></div><div class="para">
+ Due to its modular design, <span class="application"><strong>rsyslog</strong></span> offers a variety of <em class="firstterm">modules</em> which provide additional functionality. Note that modules can be written by third parties. Most modules provide additional inputs (see <span class="emphasis"><em>Input Modules</em></span> below) or outputs (see <span class="emphasis"><em>Output Modules</em></span> below). Other modules provide special functionality specific to each module. The modules may provide additional configuration directives that become available after a module is loaded. To load a module, use the following syntax:
+ </div><pre class="screen">
+$ModLoad <em class="replaceable"><code>MODULE</code></em>
+</pre><div class="para">
+ where <code class="option">$ModLoad</code> is the global directive that loads the specified module and <em class="replaceable"><code>MODULE</code></em> represents your desired module. For example, if you want to load the Text File Input Module (<code class="command">imfile</code>) that enables <span class="application"><strong>rsyslog</strong></span> to convert any standard text files into syslog messages, specify the following line in the <code class="filename">/etc/rsyslog.conf</code> configuration file:
+ </div><pre class="screen">
+$ModLoad imfile
+</pre><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> offers a number of modules which are split into the following main categories:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Input Modules — Input modules gather messages from various sources. The name of an input module always starts with the <code class="literal">im</code> prefix, such as <code class="command">imfile</code>, <code class="command">imjournal</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Output Modules — Output modules provide a facility to issue message to various targets such as sending across a network, storing in a database, or encrypting. The name of an output module always starts with the <code class="literal">om</code> prefix, such as <code class="command">omsnmp</code>, <code class="command">omrelp</code>, etc.
+ </div></li><li class="listitem"><div class="para">
+ Parser Modules — These modules are useful in creating custom parsing rules or to parse malformed messages. With moderate knowledge of the C programming language, you can create your own message parser. The name of a parser module always starts with the <code class="literal">pm</code> prefix, such as <code class="command">pmrfc5424</code>, <code class="command">pmrfc3164</code>, and so on.
+ </div></li><li class="listitem"><div class="para">
+ Message Modification Modules — Message modification modules change content of syslog messages. Names of these modules start with the <code class="literal">mm</code> prefix. Message Modification Modules such as <code class="command">mmanon</code>, <code class="command">mmnormalize</code>, or <code class="command">mmjsonparse</code> are used for anonymization or normalization of messages.
+ </div></li><li class="listitem"><div class="para">
+ String Generator Modules — String generator modules generate strings based on the message content and strongly cooperate with the template feature provided by <span class="application"><strong>rsyslog</strong></span>. For more information on templates, see <a class="xref" href="s2-Templates.html">Section 17.2.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> or <code class="command">smtradfile</code>.
+ </div></li><li class="listitem"><div class="para">
+ Library Modules — Library modules provide functionality for other loadable modules. These modules are loaded automatically by <span class="application"><strong>rsyslog</strong></span> when needed and cannot be configured by the user.
+ </div></li></ul></div><div class="para">
+ A comprehensive list of all available modules and their detailed description can be found at <a href="http://www.rsyslog.com/doc/rsyslog_conf_modules.html/">http://www.rsyslog.com/doc/rsyslog_conf_modules.html</a>.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Note that when <span class="application"><strong>rsyslog</strong></span> loads any modules, it provides them with access to some of its functions and data. This poses a possible security threat. To minimize security risks, use trustworthy modules only.
+ </div></div></div><div class="section" id="s2-importing_text_files"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.4.1. Importing Text Files</h3></div></div></div><div class="para">
+ The Text File Input Module, abbreviated as <code class="command">imfile</code>, enables <span class="application"><strong>rsyslog</strong></span> to convert any text file into a stream of syslog messages. You can use <code class="command">imfile</code> to import log messages from applications that create their own text file logs. To load <code class="command">imfile</code>, add the following into <code class="filename">etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imfile
+$InputFilePollInterval <em class="replaceable"><code>int</code></em>
+</pre><div class="para">
+ It is sufficient to load <code class="command">imfile</code> once, even when importing multiple files. The <span class="emphasis"><em>$InputFilePollInterval</em></span> global directive specifies how often <span class="application"><strong>rsyslog</strong></span> checks for changes in connected text files. The default interval is 10 seconds, to change it, replace <em class="replaceable"><code>int</code></em> with a time interval specified in seconds.
+ </div><div class="para">
+ To identify the text files to import, use the following syntax in <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+# File 1
+$InputFileName <em class="replaceable"><code>path_to_file</code></em>
+$InputFileTag <em class="replaceable"><code>tag:</code></em>
+$InputFileStateFile <em class="replaceable"><code>state_file_name</code></em>
+$InputFileSeverity <em class="replaceable"><code>severity</code></em>
+$InputFileFacility <em class="replaceable"><code>facility</code></em>
+$InputRunFileMonitor
+
+# File 2
+$InputFileName <em class="replaceable"><code>path_to_file2</code></em>
+...
+</pre><div class="para">
+ Four settings are required to specify an input text file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ replace <em class="replaceable"><code>path_to_file</code></em> with a path to the text file.
+ </div></li><li class="listitem"><div class="para">
+ replace <em class="replaceable"><code>tag:</code></em> with a tag name for this message.
+ </div></li><li class="listitem"><div class="para">
+ replace <em class="replaceable"><code>state_file_name</code></em> with a unique name for the <span class="emphasis"><em>state file</em></span>. <span class="emphasis"><em>State files</em></span>, which are stored in the rsyslog working directory, keep cursors for the monitored files, marking what partition has already been processed. If you delete them, whole files will be read in again. Make sure that you specify a name that does not already exist.
+ </div></li><li class="listitem"><div class="para">
+ add the <span class="emphasis"><em>$InputRunFileMonitor</em></span> directive that enables the file monitoring. Without this setting, the text file will be ignored.
+ </div></li></ul></div><div class="para">
+ Apart from the required directives, there are several other settings that can be applied on the text input. Set the severity of imported messages by replacing <em class="replaceable"><code>severity</code></em> with an appropriate keyword. Replace <em class="replaceable"><code>facility</code></em> with a keyword to define the subsystem that produced the message. The keywords for severity and facility are the same as those used in facility/priority-based filters, see <a class="xref" href="s1-basic_configuration_of_rsyslog.html#s2-Filters">Section 17.2.1, “Filters”</a>.
+ </div><div class="example" id="ex-importing_text_files"><h6>Example 17.13. Importing Text Files</h6><div class="example-contents"><div class="para">
+ The Apache HTTP server creates log files in text format. To apply the processing capabilities of <span class="application"><strong>rsyslog</strong></span> to apache error messages, first use the <code class="command">imfile</code> module to import the messages. Add the following into <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad imfile
+
+$InputFileName /var/log/httpd/error_log
+$InputFileTag apache-error:
+$InputFileStateFile state-apache-error
+$InputRunFileMonitor
+</pre></div></div><br class="example-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-managing_queues.html"><strong>Prev</strong>17.3.2. Managing Queues</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-exporting_messages_to_a_database.html"><strong>Next</strong>17.4.2. Exporting Messages to a Database</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-using_ssh.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-using_ssh.html
index ea1a964..545e3f9 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-using_ssh.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-using_ssh.html
@@ -1,24 +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>8.2.3. Connecting to VNC Server using SSH</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Connecting to VNC Server Using SSH</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s5-vnc-viewer.html" title="8.2. VNC Viewer" /><link rel="prev" href="s6-connecting-vnc-viewer.html" title="8.2.2. Connecting to VNC Server" /><link rel="next" href="s9-additional-sources.html" title="8.3. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s6-connecting-vnc-viewer.html"><strong>Prev</strong></a></li><li class="next"><a acc
esskey="n" href="s9-additional-sources.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-using_ssh"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.2.3. Connecting to VNC Server using SSH</h3></div></div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s5-vnc-viewer.html" title="8.2. VNC Viewer" /><link rel="prev" href="s6-connecting-vnc-viewer.html" title="8.2.2. Connecting to VNC Server" /><link rel="next" href="s9-additional-sources.html" title="8.3. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s6-connecting-vnc-viewer.html"><strong>Prev</strong></a></li><li class="next"><a acc
esskey="n" href="s9-additional-sources.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-using_ssh"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.2.3. Connecting to VNC Server Using SSH</h3></div></div></div><div class="para">
<acronym class="acronym">VNC</acronym> is a clear text network protocol with no security against possible attacks on the communication. To make the communication secure, you can encrypt your server-client connection by using the <code class="option">-via</code> option. This will create an <code class="systemitem">SSH</code> tunnel between the VNC server and the client.
</div><div class="para">
- The format of the command to encrypt a VNC server-client connection looks as follows:
+ The format of the command to encrypt a VNC server-client connection is as follows:
</div><pre class="screen">
-<code class="command"><code class="computeroutput">~]$ </code><strong class="userinput"><code>vncviewer -via <em class="replaceable"><code>user</code></em>@<em class="replaceable"><code>host</code></em>:<em class="replaceable"><code>display_number</code></em></code></strong></code></pre><div class="example" id="using-via"><h6>Example 8.2. Using the -via option</h6><div class="example-contents"><div class="procedure"><ol class="1"><li class="step"><div class="para">
+<code class="command"><code class="computeroutput">~]$ </code><strong class="userinput"><code>vncviewer -via <em class="replaceable"><code>user</code></em>@<em class="replaceable"><code>host</code></em>:<em class="replaceable"><code>display_number</code></em></code></strong></code></pre><div class="example" id="using-via"><h6>Example 8.2. Using the -via Option</h6><div class="example-contents"><div class="procedure"><ol class="1"><li class="step"><div class="para">
To connect to a VNC server using <code class="systemitem">SSH</code>, enter a command as follows:
</div><pre class="programlisting">
<code class="command"><code class="computeroutput">~]$ </code><strong class="userinput"><code>vncviewer -via USER_2 at 192.168.2.101:3</code></strong></code></pre></li><li class="step"><div class="para">
When you are prompted to, type the password, and confirm by pressing <span class="keycap"><strong>Enter</strong></span>.
</div></li><li class="step"><div class="para">
A window with a remote desktop appears on your screen.
- </div></li></ol></div></div></div><br class="example-break" /><h4 id="bh-Restricting_VNC_access">Restricting VNC access</h4><div class="para">
+ </div></li></ol></div></div></div><br class="example-break" /><h4 id="bh-Restricting_VNC_access">Restricting VNC Access</h4><div class="para">
If you prefer only encrypted connections, you can prevent unencrypted connections altogether by using the <code class="option">-localhost</code> option in the <code class="systemitem">systemd.service</code> file, the ExecStart line:
</div><pre class="screen">ExecStart=/sbin/runuser -l <em class="replaceable"><code>user</code></em> -c "/usr/bin/vncserver -localhost %i"</pre><div class="para">
This will stop <code class="systemitem">vncserver</code> from accepting connections from anything but the local host and port-forwarded connections sent using <code class="systemitem">SSH</code> as a result of the <code class="option">-via</code> option.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-working_with_queues_in_rsyslog.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-working_with_queues_in_rsyslog.html
new file mode 100644
index 0000000..e70650e
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s1-working_with_queues_in_rsyslog.html
@@ -0,0 +1,113 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.3. Working with Queues in Rsyslog</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Viewing_and_Managing_Log_Files.html" title="Chapter 17. Viewing and Managing Log Files" /><link rel="prev" href="s2-compatibility_with_syslogd.html" title="17.2.8. Compatibility with syslogd" /><link rel="next" href="s2-managing_queues.html" title="17.3.2. Managing Queues" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-compatibility_with_syslogd.htm
l"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-managing_queues.html"><strong>Next</strong></a></li></ul><div class="section" id="s1-working_with_queues_in_rsyslog"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">17.3. Working with Queues in Rsyslog</h2></div></div></div><div class="para">
+ Queues are used to pass content, mostly syslog messages, between components of <span class="application"><strong>rsyslog</strong></span>. With queues, rsyslog is capable of processing multiple messages simultaneously and to apply several actions to a single message at once. The data flow inside <span class="application"><strong>rsyslog</strong></span> can be illustrated as follows:
+ </div><div class="figure" id="fig-message_flow_in_rsyslog"><div class="figure-contents"><div class="mediaobject"><img src="images/rsyslog_message_flow.png" width="444" alt="Message Flow in Rsyslog" /><div class="longdesc"><div class="para">
+ Message Flow in Rsyslog
+ </div></div></div></div><h6>Figure 17.1. Message Flow in Rsyslog</h6></div><br class="figure-break" /><div class="para">
+ Whenever <span class="application"><strong>rsyslog</strong></span> receives a message, it passes this message to the preprocessor and then places it into the <em class="firstterm">main message queue</em>. Messages wait there to be dequeued and passed to the <em class="firstterm">rule processor</em>.
+ </div><div class="para">
+ The <span class="emphasis"><em>rule processor</em></span> is a parsing and filtering engine. Here, the rules defined in <code class="filename">/etc/rsyslog.conf</code> are applied. Based on these rules, the rule processor evaluates which actions are to be performed. Each action has its own action queue. Messages are passed through this queue to the respective action processor which creates the final output. Note that at this point, several actions can run simultaneously on one message. For this purpose, a message is duplicated and passed to multiple action processors.
+ </div><div class="para">
+ Only one queue per action is possible. Depending on configuration, the messages can be sent right to the action processor without action queuing. This is the behavior of <span class="emphasis"><em>direct queues</em></span> (see below). In case the output action fails, the action processor notifies the action queue, which then takes an unprocessed element back and after some time interval, the action is attempted again.
+ </div><div class="para">
+ To sum up, there are two positions where queues stand in <span class="application"><strong>rsyslog</strong></span>: either in front of the rule processor as a single <span class="emphasis"><em>main message queue</em></span> or in front of various types of output actions as <span class="emphasis"><em>action queues</em></span>. Queues provide two main advantages that both lead to increased performance of message processing:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ they serve as buffers that <span class="emphasis"><em>decouple</em></span> producers and consumers in the structure of <span class="application"><strong>rsyslog</strong></span>
+ </div></li><li class="listitem"><div class="para">
+ they allow for <span class="emphasis"><em>parallelization</em></span> of actions performed on messages
+ </div></li></ul></div><div class="para">
+ Apart from this, queues can be configured with several directives to provide optimal performance for your system. These configuration options are covered in the following sections.
+ </div><div class="section" id="s2-defining_queues"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.3.1. Defining Queues</h3></div></div></div><div class="para">
+ Based on where the messages are stored, there are several types of queues: <span class="emphasis"><em>direct</em></span>, <span class="emphasis"><em>in-memory</em></span>, <span class="emphasis"><em>disk</em></span>, and <span class="emphasis"><em>disk-assisted in-memory</em></span> queues that are most widely used. You can choose one of these types for the main message queue and also for action queues. Add the following into <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueType <em class="replaceable"><code>queue_type</code></em></pre><div class="para">
+ Here, you can apply the setting for the main message queue (replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code>) or for an action queue (replace <em class="replaceable"><code>object</code></em> with <code class="option">Action</code>). Replace <em class="replaceable"><code>queue_type</code></em> with one of <code class="literal">direct</code>, <code class="literal">linkedlist</code> or <code class="literal">fixedarray</code> (which are in-memory queues), or <code class="literal">disk</code>.
+ </div><div class="para">
+ The default setting for a main message queue is the FixedArray queue with a limit of 10,000 messages. Action queues are by default set as Direct queues.
+ </div><h4 id="br-direct_queues">Direct Queues</h4><div class="para">
+ For many simple operations, such as when writing output to a local file, building a queue in front of an action is not needed. To avoid queuing, use:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueType Direct</pre><div class="para">
+ Replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code> or with <code class="option">Action</code> to use this option to the main message queue or for an action queue respectively. With direct queue, messages are passed directly and immediately from the producer to the consumer.
+ </div><h4 id="br-disk_queues">Disk Queues</h4><div class="para">
+ Disk queues store messages strictly on a hard drive, which makes them highly reliable but also the slowest of all possible queuing modes. This mode can be used to prevent the loss of highly important log data. However, disk queues are not recommended in most use cases. To set a disk queue, type the following into <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueType Disk</pre><div class="para">
+ Replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code> or with <code class="option">Action</code> to use this option to the main message queue or for an action queue respectively. Disk queues are written in parts, with a default size 10 Mb. This default size can be modified with the following configuration directive:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueMaxFileSize <em class="replaceable"><code>size</code></em></pre><div class="para">
+ where <em class="replaceable"><code>size</code></em> represents the specified size of disk queue part. The defined size limit is not restrictive, <span class="application"><strong>rsyslog</strong></span> always writes one complete queue entry, even if it violates the size limit. Each part of a disk queue matches with an individual file. The naming directive for these files looks as follows:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueFilename <em class="replaceable"><code>name</code></em></pre><div class="para">
+ This sets a <em class="replaceable"><code>name</code></em> prefix for the file followed by a 7-digit number starting at one and incremented for each file.
+ </div><h4 id="br-in-memory_queues">In-memory Queues</h4><div class="para">
+ With in-memory queue, the enqueued messages are held in memory which makes the process very fast. The queued data is lost if the computer is power cycled or shut down. However, you can use the <code class="option">$ActionQueueSaveOnShutdown</code> setting to save the data before shutdown. There are two types of in-memory queues:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <span class="emphasis"><em>FixedArray</em></span> queue — the default mode for the main message queue, with a limit of 10,000 elements. This type of queue uses a fixed, pre-allocated array that holds pointers to queue elements. Due to these pointers, even if the queue is empty a certain amount of memory is consumed. However, FixedArray offers the best run time performance and is optimal when you expect a relatively low number of queued messages and high performance.
+ </div></li><li class="listitem"><div class="para">
+ <span class="emphasis"><em>LinkedList</em></span> queue — here, all structures are dynamically allocated in a linked list, thus the memory is allocated only when needed. LinkedList queues handle occasional message bursts very well.
+ </div></li></ul></div><div class="para">
+ In general, use LinkedList queues when in doubt. Compared to FixedArray, it consumes less memory and lowers the processing overhead.
+ </div><div class="para">
+ Use the following syntax to configure in-memory queues:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueType LinkedList</pre><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueType FixedArray</pre><div class="para">
+ Replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code> or with <code class="option">Action</code> to use this option to the main message queue or for an action queue respectively.
+ </div><h4 id="br-disk-assisted_in-memory_queues">Disk-Assisted In-memory Queues</h4><div class="para">
+ Both disk and in-memory queues have their advantages and <span class="application"><strong>rsyslog</strong></span> lets you combine them in <span class="emphasis"><em>disk-assisted in-memory queues</em></span>. To do so, configure a normal in-memory queue and then add the <code class="option">$objectQueueFileName</code> directive to define a file name for disk assistance. This queue then becomes <span class="emphasis"><em>disk-assisted</em></span>, which means it couples an in-memory queue with a disk queue to work in tandem.
+ </div><div class="para">
+ The disk queue is activated if the in-memory queue is full or needs to persist after shutdown. With a disk-assisted queue, you can set both disk-specific and in-memory specific configuration parameters. This type of queue is probably the most commonly used, it is especially useful for potentially long-running and unreliable actions.
+ </div><div class="para">
+ To specify the functioning of a disk-assisted in-memory queue, use the so-called <span class="emphasis"><em>watermarks</em></span>:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueHighWatermark <em class="replaceable"><code>number</code></em></pre><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueLowWatermark <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code> or with <code class="option">Action</code> to use this option to the main message queue or for an action queue respectively. Replace <em class="replaceable"><code>number</code></em> with a number of enqueued messages. When an in-memory queue reaches the number defined by the high watermark, it starts writing messages to disk and continues until the in-memory queue size drops to the number defined with the low watermark. Correctly set watermarks minimize unnecessary disk writes, but also leave memory space for message bursts since writing to disk files is rather lengthy. Therefore, the high watermark must be lower than the whole queue capacity set with <span class="emphasis"><em>$objectQueueSize</em></span>. The difference between the high watermark and the overall queue size is a spare memory buffer reserved for message bursts. On the other hand, setting the high watermark t
oo low will turn on disk assistance unnecessarily often.
+ </div><div class="example" id="ex-net_forwarding_with_queue"><h6>Example 17.12. Reliable Forwarding of Log Messages to a Server</h6><div class="example-contents"><div class="para">
+ Rsyslog is often used to maintain a centralized logging system, where log messages are forwarded to a server over the network. To avoid message loss when the server is not available, it is advisable to configure an action queue for the forwarding action. This way, messages that failed to be sent are stored locally until the server is reachable again. Note that such queues are not configurable for connections using the <code class="systemitem">UDP</code> protocol. To establish a fully reliable connection, for example when your logging server is outside of your private network, consider using the RELP protocol described in <a class="xref" href="s2-using_RELP.html">Section 17.4.4, “Using RELP”</a>.
+ </div><div class="procedure" id="proc-net_forwarding_with_queue"><h6>Procedure 17.1. Forwarding To a Single Server</h6><div class="para">
+ Suppose the task is to forward log messages from the system to a server with host name <span class="emphasis"><em>example.com</em></span>, and to configure an action queue to buffer the messages in case of a server outage. To do so, perform the following steps:
+ </div><ol class="1"><li class="step"><div class="para">
+ Create a working directory to store the queue files. For example:
+ </div><pre class="synopsis">~]# <code class="command">mkdir</code> <code class="filename">/rsyslog/work/</code></pre></li><li class="step"><div class="para">
+ Use the following configuration in <code class="filename">/etc/rsyslog.conf</code> or create a file with the following content in the <code class="filename">/etc/rsyslog.d/</code> directory:
+ </div><pre class="screen">$WorkDirectory /rsyslog/work
+
+$ActionQueueType LinkedList
+$ActionQueueFileName example_fwd
+$ActionResumeRetryCount -1
+$ActionQueueSaveOnShutdown on
+*.* @@example.com:18</pre><div class="itemizedlist"><div class="para">
+ Where:
+ </div><ul><li class="listitem"><div class="para">
+ the <code class="filename">/rsyslog/work/</code> directory created in the previous step is marked as a working directory,
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">$ActionQueueType</code> enables a LinkedList in-memory queue,
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">$ActionFileName</code> defines a disk storage, in this case the backup files are created in the <code class="filename">/rsyslog/work/</code> directory with the <span class="emphasis"><em>example_fwd</em></span> prefix,
+ </div></li><li class="listitem"><div class="para">
+ the <code class="option">$ActionResumeRetryCount -1</code> setting prevents rsyslog form dropping messages when retrying to connect if server is not responding,
+ </div></li><li class="listitem"><div class="para">
+ enabled <code class="option">$ActionQueueSaveOnShutdown</code> saves in-memory data if rsyslog shuts down,
+ </div></li><li class="listitem"><div class="para">
+ the last line forwards all received messages to the logging server, port specification is optional.
+ </div></li></ul></div><div class="para">
+ With the above configuration, rsyslog keeps messages in memory if the remote server is not reachable. A file on disk is created only if rsyslog runs out of the configured memory queue space or needs to shut down, which benefits the system performance.
+ </div></li></ol></div><div class="procedure" id="proc-net_forwarding_two_servers"><h6>Procedure 17.2. Forwarding To Multiple Servers</h6><div class="para">
+ The process of forwarding log messages to multiple servers is similar to the previous procedure:
+ </div><ol class="1"><li class="step"><div class="para">
+ Create a working directory for rsyslog to store the queue files. For example:
+ </div><pre class="synopsis">~]# <code class="command">mkdir</code> <code class="filename">/rsyslog/work/</code></pre></li><li class="step"><div class="para">
+ Each destination server requires a separate forwarding rule, action queue specification, and backup file on disk. For example, use the following configuration in <code class="filename">/etc/rsyslog.conf</code> or create a file with the following content in the <code class="filename">/etc/rsyslog.d/</code> directory:
+ </div><pre class="screen">$WorkDirectory /rsyslog/work
+
+$ActionQueueType LinkedList
+$ActionQueueFileName example_fwd1
+$ActionResumeRetryCount -1
+$ActionQueueSaveOnShutdown on
+*.* @@example1.com
+
+$ActionQueueType LinkedList
+$ActionQueueFileName example_fwd2
+$ActionResumeRetryCount -1
+$ActionQueueSaveOnShutdown on
+*.* @@example2.com</pre></li></ol></div></div></div><br class="example-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-compatibility_with_syslogd.html"><strong>Prev</strong>17.2.8. Compatibility with syslogd</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-managing_queues.html"><strong>Next</strong>17.3.2. Managing Queues</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Access_Control.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Access_Control.html
new file mode 100644
index 0000000..a9043b7
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Access_Control.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.8.2. Access Control</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-Using_the_Journal.html" title="17.8. Using the Journal" /><link rel="prev" href="s1-Using_the_Journal.html" title="17.8. Using the Journal" /><link rel="next" href="s2-Using_The_Live_View.html" title="17.8.3. Using The Live View" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-Using_the_Journal.html"><strong>Prev</strong></a></li><li class="next"><a a
ccesskey="n" href="s2-Using_The_Live_View.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-Access_Control"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.8.2. Access Control</h3></div></div></div><div class="para">
+ By default, <span class="application"><strong>Journal</strong></span> users without <code class="systemitem">root</code> privileges can only see log files generated by them. The system administrator can add selected users to the <span class="emphasis"><em>adm</em></span> group, which grants them access to complete log files. To do so, type as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code class="command">usermod</code> <code class="option">-a</code> <code class="option">-G</code> <span class="emphasis"><em>adm</em></span> <em class="replaceable"><code>username</code></em></pre><div class="para">
+ Here, replace <em class="replaceable"><code>username</code></em> with a name of the user to be added to the <span class="emphasis"><em>adm</em></span> group. This user then receives the same output of the <code class="command">journalctl</code> command as the root user. Note that access control only works when persistent storage is enabled for <span class="application"><strong>Journal</strong></span>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-Using_the_Journal.html"><strong>Prev</strong>17.8. Using the Journal</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-Using_The_Live_View.html"><strong>Next</strong>17.8.3. Using The Live View</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Actions.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Actions.html
new file mode 100644
index 0000000..c4d07a9
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Actions.html
@@ -0,0 +1,137 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2.2. Actions</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-basic_configuration_of_rsyslog.html" title="17.2. Basic Configuration of Rsyslog" /><link rel="prev" href="s1-basic_configuration_of_rsyslog.html" title="17.2. Basic Configuration of Rsyslog" /><link rel="next" href="s2-Templates.html" title="17.2.3. Templates" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-basic_configuration_of_rsyslog.html"><stron
g>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-Templates.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-Actions"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.2. Actions</h3></div></div></div><div class="para">
+ Actions specify what is to be done with the messages filtered out by an already-defined selector. The following are some of the actions you can define in your rule:
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term">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:
+ </div><pre class="synopsis"><em class="replaceable"><code>FILTER</code></em> <em class="replaceable"><code>PATH</code></em></pre><div class="para">
+ where <em class="replaceable"><code>FILTER</code></em> stands for user-specified selector and <em class="replaceable"><code>PATH</code></em> is a path of a target file.
+ </div><div class="para">
+ For instance, the following rule is comprised of a selector that selects all <span class="application"><strong>cron</strong></span> syslog messages and an action that saves them into the <code class="filename">/var/log/cron.log</code> log file:
+ </div><pre class="synopsis">cron.* /var/log/cron.log</pre><div class="para">
+ By default, the log file is synchronized every time a syslog message is generated. Use a dash mark (<code class="literal">-</code>) as a prefix of the file path you specified to omit syncing:
+ </div><pre class="synopsis"><em class="replaceable"><code>FILTER</code></em> -<em class="replaceable"><code>PATH</code></em></pre><div class="para">
+ Note that you might lose information if the system terminates right after a write attempt. However, this setting can improve performance, especially if you run programs that produce very verbose log messages.
+ </div><div class="para">
+ Your specified file path can be either <span class="emphasis"><em>static</em></span> or <span class="emphasis"><em>dynamic</em></span>. Static files are represented by a fixed file path as shown in the example above. Dynamic file paths can differ according to the received message. Dynamic file paths are represented by a template and a question mark (<code class="literal">?</code>) prefix:
+ </div><pre class="synopsis"><em class="replaceable"><code>FILTER</code></em> ?<em class="replaceable"><code>DynamicFile</code></em></pre><div class="para">
+ where <em class="replaceable"><code>DynamicFile</code></em> is a name of a predefined template that modifies output paths. You can use the dash prefix (<code class="literal">-</code>) to disable syncing, also you can use multiple templates separated by a colon (<code class="literal">;</code>). For more information on templates, see <a class="xref" href="s2-Templates.html#brid-generating-dynamic-fnames">the section called “Generating Dynamic File Names”</a>.
+ </div><div class="para">
+ If the file you specified is an existing <span class="application"><strong>terminal</strong></span> or <code class="filename">/dev/console</code> device, syslog messages are sent to standard output (using special <span class="application"><strong>terminal</strong></span>-handling) or your console (using special <code class="filename">/dev/console</code>-handling) when using the X Window System, respectively.
+ </div></dd><dt class="varlistentry"><span class="term">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 you to administer syslog messages of multiple hosts on one machine. To forward syslog messages to a remote machine, use the following syntax:
+ </div><pre class="screen">@[<span class="optional">(<code class="command">z<em class="replaceable"><code>NUMBER</code></em></code>)</span>]<em class="replaceable"><code>HOST</code></em>:[<span class="optional"><em class="replaceable"><code>PORT</code></em></span>]
+</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The at sign (<code class="literal">@</code>) indicates that the syslog messages are forwarded to a host using the <code class="systemitem">UDP</code> protocol. To use the <code class="systemitem">TCP</code> protocol, use two at signs with no space between them (<code class="literal">@@</code>).
+ </div></li><li class="listitem"><div class="para">
+ The optional <code class="command">z<em class="replaceable"><code>NUMBER</code></em></code> setting enables <span class="application"><strong>zlib</strong></span> compression for syslog messages. The <em class="replaceable"><code>NUMBER</code></em> attribute specifies the level of compression (from 1 – lowest to 9 – maximum). Compression gain is automatically checked by <code class="systemitem">rsyslogd</code>, messages are compressed only if there is any compression gain and messages below 60 bytes are never compressed.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>HOST</code></em> attribute specifies the host which receives the selected syslog messages.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>PORT</code></em> attribute specifies the host machine's port.
+ </div></li></ul></div><div class="para">
+ When specifying an <code class="systemitem">IPv6</code> address as the host, enclose the address in square brackets (<code class="literal">[</code>, <code class="literal">]</code>).
+ </div><div class="example" id="ex-logging_over_the_network"><h6>Example 17.4. Sending syslog Messages over the Network</h6><div class="example-contents"><div class="para">
+ The following are some examples of actions that forward syslog messages over the network (note that all actions are preceded with a selector that selects all messages with any priority). To forward messages to <code class="systemitem">192.168.0.1</code> via the <code class="systemitem">UDP</code> protocol, type:
+ </div><pre class="screen">
+*.* @192.168.0.1
+</pre><div class="para">
+ To forward messages to "example.com" using port 18 and the <code class="systemitem">TCP</code> protocol, use:
+ </div><pre class="screen">
+*.* @@example.com:18
+</pre><div class="para">
+ The following compresses messages with <span class="application"><strong>zlib</strong></span> (level 9 compression) and forwards them to <code class="systemitem">2001:db8::1</code> using the <code class="systemitem">UDP</code> protocol
+ </div><pre class="screen">
+*.* @(z9)[2001:db8::1]
+</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">Output channels</span></dt><dd><div class="para">
+ Output channels are primarily used to specify the maximum size a log file can grow to. This is very useful for log file rotation (for more information see <a class="xref" href="s2-log_rotation.html">Section 17.2.5, “Log Rotation”</a>). An output channel is basically a collection of information about the output action. Output channels are defined by the <code class="literal">$outchannel</code> directive. To define an output channel in <code class="filename">/etc/rsyslog.conf</code>, use the following syntax:
+ </div><pre class="screen">$outchannel <em class="replaceable"><code>NAME</code></em>, <em class="replaceable"><code>FILE_NAME</code></em>, <em class="replaceable"><code>MAX_SIZE</code></em>, <em class="replaceable"><code>ACTION</code></em></pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>NAME</code></em> attribute specifies the name of the output channel.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>FILE_NAME</code></em> attribute specifies the name of the output file. Output channels can write only into files, not pipes, terminal, or other kind of output.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>MAX_SIZE</code></em> attribute represents the maximum size the specified file (in <em class="replaceable"><code>FILE_NAME</code></em>) can grow to. This value is specified in <span class="emphasis"><em>bytes</em></span>.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>ACTION</code></em> attribute specifies the action that is taken when the maximum size, defined in <em class="replaceable"><code>MAX_SIZE</code></em>, is hit.
+ </div></li></ul></div><div class="para">
+ To use the defined output channel as an action inside a rule, type:
+ </div><pre class="synopsis"><em class="replaceable"><code>FILTER</code></em> :omfile:$<em class="replaceable"><code>NAME</code></em></pre><div class="example" id="example-log-rotation"><h6>Example 17.5. Output channel log rotation</h6><div class="example-contents"><div class="para">
+ The following output shows a simple log rotation through the use of an output channel. First, the output channel is defined via the <em class="parameter"><code>$outchannel</code></em> directive:
+ </div><pre class="screen">
+ $outchannel log_rotation, /var/log/test_log.log, 104857600, /home/joe/log_rotation_script
+</pre><div class="para">
+ and then it is used in a rule that selects every syslog message with any priority and executes the previously-defined output channel on the acquired syslog messages:
+ </div><pre class="screen">
+*.* :omfile:$log_rotation
+</pre><div class="para">
+ Once the limit (in the example <code class="constant">100 MB</code>) is hit, the <code class="filename">/home/joe/log_rotation_script</code> is executed. This script can contain anything from moving the file into a different folder, editing specific content out of it, or simply removing it.
+ </div></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term">Sending syslog messages to specific users</span></dt><dd><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> can send syslog messages to specific users by specifying a user name of the user you want to send the messages to (as in <a class="xref" href="s2-Actions.html#ex-multiple_actions">Example 17.7, “Specifying Multiple Actions”</a>). To specify more than one user, separate each user name with a comma (<code class="literal">,</code>). To send messages to every user that is currently logged on, use an asterisk (<code class="literal">*</code>).
+ </div></dd><dt class="varlistentry"><span class="term">Executing a program</span></dt><dd><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> lets you execute a program for selected syslog messages and uses the <code class="systemitem">system()</code> call to execute the program in shell. To specify a program to be executed, prefix it with a caret character (<code class="literal">^</code>). Consequently, specify a template that formats the received message and passes it to the specified executable as a one line parameter (for more information on templates, see <a class="xref" href="s2-Templates.html">Section 17.2.3, “Templates”</a>).
+ </div><pre class="synopsis"><em class="replaceable"><code>FILTER</code></em> ^<em class="replaceable"><code>EXECUTABLE</code></em>; <em class="replaceable"><code>TEMPLATE</code></em></pre><div class="para">
+ Here an output of the <em class="replaceable"><code>FILTER</code></em> condition is processed by a program represented by <em class="replaceable"><code>EXECUTABLE</code></em>. This program can be any valid executable. Replace <em class="replaceable"><code>TEMPLATE</code></em> with the name of the formatting template.
+ </div><div class="example" id="ex-esecuting_a_program"><h6>Example 17.6. Executing a Program</h6><div class="example-contents"><div class="para">
+ In the following example, any syslog message with any priority is selected, formatted with the <em class="parameter"><code>template</code></em> template and passed as a parameter to the <span class="application"><strong>test-program</strong></span> program, which is then executed with the provided parameter:
+ </div><pre class="screen">*.* ^test-program;template</pre></div></div><br class="example-break" /><div class="warning"><div class="admonition_header"><h2>Be careful when using the shell execute action</h2></div><div class="admonition"><div class="para">
+ When accepting messages from any host, and using the shell execute action, you may be vulnerable to command injection. An attacker may try to inject and execute commands in the program you specified to be executed in your action. To avoid any possible security threats, thoroughly consider the use of the shell execute action.
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Storing syslog messages in a database</span></dt><dd><div class="para">
+ Selected syslog messages can be directly written into a database table using the <span class="emphasis"><em>database writer</em></span> action. The database writer uses the following syntax:
+ </div><pre class="screen">:<em class="replaceable"><code>PLUGIN</code></em>:<em class="replaceable"><code>DB_HOST</code></em>,<em class="replaceable"><code>DB_NAME</code></em>,<em class="replaceable"><code>DB_USER</code></em>,<em class="replaceable"><code>DB_PASSWORD</code></em>;[<span class="optional"><em class="replaceable"><code>TEMPLATE</code></em></span>]</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>PLUGIN</code></em> calls the specified plug-in that handles the database writing (for example, the <code class="systemitem">ommysql</code> plug-in).
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>DB_HOST</code></em> attribute specifies the database host name.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>DB_NAME</code></em> attribute specifies the name of the database.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>DB_USER</code></em> attribute specifies the database user.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>DB_PASSWORD</code></em> attribute specifies the password used with the aforementioned database user.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>TEMPLATE</code></em> attribute specifies an optional use of a template that modifies the syslog message. For more information on templates, see <a class="xref" href="s2-Templates.html">Section 17.2.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> and <code class="systemitem">PostgreSQL</code> databases only. In order to use the <code class="systemitem">MySQL</code> and <code class="systemitem">PostgreSQL</code> database writer functionality, install the <span class="package">rsyslog-mysql</span> and <span class="package">rsyslog-pgsql</span> packages, respectively. Also, make sure you load the appropriate modules in your <code class="filename">/etc/rsyslog.conf</code> configuration file:
+ </div><pre class="screen">
+$ModLoad ommysql # 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, see <a class="xref" href="s1-using_rsyslog_modules.html">Section 17.4, “Using Rsyslog Modules”</a>.
+ </div><div class="para">
+ Alternatively, you may use a generic database interface provided by the <code class="systemitem">omlibdb</code> module (supports: Firebird/Interbase, MS SQL, Sybase, SQLLite, Ingres, Oracle, mSQL).
+ </div></div></div></dd><dt class="varlistentry"><span class="term">Discarding syslog messages</span></dt><dd><div class="para">
+ To discard your selected messages, use the tilde character (<code class="literal">~</code>).
+ </div><pre class="synopsis"><em class="replaceable"><code>FILTER</code></em> ~</pre><div class="para">
+ The discard action is mostly used to filter out messages before carrying on any further processing. It can be effective if you want to omit some repeating messages that would otherwise fill the log files. The results of discard action depend on where in the configuration file it is specified, for the best results place these actions on top of the actions list. Please note that once a message has been discarded there is no way to retrieve it in later configuration file lines.
+ </div><div class="para">
+ For instance, the following rule discards any cron syslog messages:
+ </div><pre class="screen">cron.* ~</pre></dd></dl></div><h4 id="idm261738217392">Specifying Multiple Actions</h4><div class="para">
+ For each selector, you are allowed to specify multiple actions. To specify multiple actions for one selector, write each action on a separate line and precede it with an ampersand character (&):
+ </div><pre class="screen">
+<em class="replaceable"><code>FILTER</code></em> <em class="replaceable"><code>ACTION</code></em>
+& <em class="replaceable"><code>ACTION</code></em>
+& <em class="replaceable"><code>ACTION</code></em>
+</pre><div class="para">
+ Specifying multiple actions improves the overall performance of the desired outcome since the specified selector has to be evaluated only once.
+ </div><div class="example" id="ex-multiple_actions"><h6>Example 17.7. Specifying Multiple Actions</h6><div class="example-contents"><div class="para">
+ In the following example, all kernel syslog messages with the critical priority (<em class="parameter"><code>crit</code></em>) are sent to user <code class="systemitem">user1</code>, processed by the template <em class="parameter"><code>temp</code></em> and passed on to the <em class="parameter"><code>test-program</code></em> executable, and forwarded to <code class="systemitem">192.168.0.1</code> via the <code class="systemitem">UDP</code> protocol.
+ </div><pre class="screen">
+kern.=crit user1
+& ^test-program;temp
+& @192.168.0.1
+</pre></div></div><br class="example-break" /><div class="para">
+ Any action can be followed by a template that formats the message. To specify a template, suffix an action with a semicolon (<code class="literal">;</code>) and specify the name of the template. For more information on templates, see <a class="xref" href="s2-Templates.html">Section 17.2.3, “Templates”</a>.
+ </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. In other words, template definitions should always precede rule definitions in <code class="filename">/etc/rsyslog.conf</code>.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-basic_configuration_of_rsyslog.html"><strong>Prev</strong>17.2. Basic Configuration of Rsyslog</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-Templates.html"><strong>Next</strong>17.2.3. Templates</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Enabling_Persistent_Storage.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Enabling_Persistent_Storage.html
new file mode 100644
index 0000000..35152dd
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Enabling_Persistent_Storage.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.8.5. Enabling Persistent Storage</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-Using_the_Journal.html" title="17.8. Using the Journal" /><link rel="prev" href="s2-Filtering_Messages.html" title="17.8.4. Filtering Messages" /><link rel="next" href="s1-managing_log_files_in_a_graphical_environment.html" title="17.9. Managing Log Files in a Graphical Environment" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-Filtering_Messages.ht
ml"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-managing_log_files_in_a_graphical_environment.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-Enabling_Persistent_Storage"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.8.5. Enabling Persistent Storage</h3></div></div></div><div class="para">
+ By default, <span class="application"><strong>Journal</strong></span> stores log files only in memory or a small ring-buffer in the <code class="filename">/run/log/journal/</code> directory. This is sufficient to show recent log history with <code class="command">journalctl</code>. This directory is volatile, log data is not saved permanently. With the default configuration, syslog reads the journal logs and stores them in the <code class="filename">/var/log/</code> directory. With persistent logging enabled, journal files are stored in <code class="filename">/var/log/journal</code> which means they persist after reboot. Journal can then replace <span class="application"><strong>rsyslog</strong></span> for some users (but see the chapter introduction).
+ </div><div class="para">
+ Enabled persistent storage has the following advantages
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Richer data is recorded for troubleshooting in a longer period of time
+ </div></li><li class="listitem"><div class="para">
+ For immediate troubleshooting, richer data is available after a reboot
+ </div></li><li class="listitem"><div class="para">
+ Server console currently reads data from journal, not log files
+ </div></li></ul></div><div class="para">
+ Persistent storage has also certain disadvantages:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Even with persistent storage the amount of data stored depends on free memory, there is no guarantee to cover a specific time span
+ </div></li><li class="listitem"><div class="para">
+ More disk space is needed for logs
+ </div></li></ul></div><div class="para">
+ To enable persistent storage for Journal, create the journal directory manually as shown in the following example. As <code class="systemitem">root</code> type:
+ </div><pre class="synopsis"><code class="command">mkdir</code> <code class="option">-p</code> <code class="filename">/var/log/journal</code></pre><div class="para">
+ Then, restart <code class="systemitem">journald</code> to apply the change:
+ </div><pre class="synopsis"><code class="command">systemctl</code> <code class="option">restart</code> <code class="systemitem">systemd-journald</code></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-Filtering_Messages.html"><strong>Prev</strong>17.8.4. Filtering Messages</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-managing_log_files_in_a_graphical_environment.html"><strong>Next</strong>17.9. Managing Log Files in a Graphical Environme...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Filtering_Messages.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Filtering_Messages.html
new file mode 100644
index 0000000..9fe6b50
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Filtering_Messages.html
@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.8.4. Filtering Messages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-Using_the_Journal.html" title="17.8. Using the Journal" /><link rel="prev" href="s2-Using_The_Live_View.html" title="17.8.3. Using The Live View" /><link rel="next" href="s2-Enabling_Persistent_Storage.html" title="17.8.5. Enabling Persistent Storage" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-Using_The_Live_View.html"><strong>Prev</strong></a></
li><li class="next"><a accesskey="n" href="s2-Enabling_Persistent_Storage.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-Filtering_Messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.8.4. Filtering Messages</h3></div></div></div><div class="para">
+ The output of the <code class="command">journalctl</code> command executed without parameters is often extensive, therefore you can use various filtering methods to extract information to meet your needs.
+ </div><h4 id="filtering_by_priority">Filtering by Priority</h4><div class="para">
+ Log messages are often used to track erroneous behavior on the system. To view only entries with a selected or higher priority, use the following syntax:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-p</code> <em class="replaceable"><code>priority</code></em></pre><div class="para">
+ Here, replace <em class="replaceable"><code>priority</code></em> with one of the following keywords (or with a number): <code class="command">debug</code> (7), <code class="command">info</code> (6), <code class="command">notice</code> (5), <code class="command">warning</code> (4), <code class="command">err</code> (3), <code class="command">crit</code> (2), <code class="command">alert</code> (1), and <code class="command">emerg</code> (0).
+ </div><div class="example" id="ex-filtering_by_priority"><h6>Example 17.17. Filtering by Priority</h6><div class="example-contents"><div class="para">
+ To view only entries with <span class="emphasis"><em>error</em></span> or higher priority, use:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-p err</code></pre></div></div><br class="example-break" /><h4 id="filtering_by_time">Filtering by Time</h4><div class="para">
+ To view log entries only from the current boot, type:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-b</code></pre><div class="para">
+ If you reboot your system just occasionally, the <code class="option">-b</code> will not significantly reduce the output of <code class="command">journalctl</code>. In such cases, time-based filtering is more helpful:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">--since</code>=<em class="replaceable"><code>value</code></em> <code class="option">--until</code>=<em class="replaceable"><code>value</code></em></pre><div class="para">
+ With <code class="option">--since</code> and <code class="option">--until</code>, you can view only log messages created within a specified time range. You can pass <em class="replaceable"><code>values</code></em> to these options in form of date or time or both as shown in the following example.
+ </div><div class="example" id="ex-filtering_by_time_and_priority"><h6>Example 17.18. Filtering by Time and Priority</h6><div class="example-contents"><div class="para">
+ Filtering options can be combined to reduce the set of results according to specific requests. For example, to view the <span class="emphasis"><em>warning</em></span> or higher priority messages from a certain point in time, type:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-p warning</code> <code class="option">--since="2013-3-16 23:59:59"</code></pre></div></div><br class="example-break" /><h4 id="advanced_filtering">Advanced Filtering</h4><div class="para">
+ <a class="xref" href="s1-Using_the_Journal.html#ex-verbose_journalctl_output">Example 17.16, “Verbose journalctl Output”</a> lists a set of fields that specify a log entry and can all be used for filtering. For a complete description of meta data that <code class="systemitem">systemd</code> can store, see the <code class="filename">systemd.journal-fields(7)</code> manual page. This meta data is collected for each log message, without user intervention. Values are usually text-based, but can take binary and large values; fields can have multiple values assigned though it is not very common.
+ </div><div class="para">
+ To view a list of unique values that occur in a specified field, use the following syntax:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-F</code> <em class="replaceable"><code>fieldname</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>fieldname</code></em> with a name of a field you are interested in.
+ </div><div class="para">
+ To show only log entries that fit a specific condition, use the following syntax:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <em class="replaceable"><code>fieldname</code></em>=<em class="replaceable"><code>value</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>fieldname</code></em> with a name of a field and <em class="replaceable"><code>value</code></em> with a specific value contained in that field. As a result, only lines that match this condition are returned.
+ </div><div class="note"><div class="admonition_header"><h2><span class="keycap"><strong>Tab</strong></span> Completion on Field Names</h2></div><div class="admonition"><div class="para">
+ As the number of meta data fields stored by <code class="systemitem">systemd</code> is quite large, it is easy to forget the exact name of the field of interest. When unsure, type:
+ </div><pre class="synopsis"><code class="command">journalctl</code></pre><div class="para">
+ and press the <span class="keycap"><strong>Tab</strong></span> key two times. This shows a list of available field names. <span class="keycap"><strong>Tab</strong></span> completion based on context works on field names, so you can type a distinctive set of letters from a field name and then press <span class="keycap"><strong>Tab</strong></span> to complete the name automatically. Similarly, you can list unique values from a field. Type:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <em class="replaceable"><code>fieldname</code></em>=</pre><div class="para">
+ and press <span class="keycap"><strong>Tab</strong></span> two times. This serves as an alternative to <code class="command">journalctl</code> <code class="option">-F</code> <em class="replaceable"><code>fieldname</code></em>.
+ </div></div></div><div class="para">
+ You can specify multiple values for one field:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <em class="replaceable"><code>fieldname</code></em>=<em class="replaceable"><code>value1</code></em> <em class="replaceable"><code>fieldname</code></em>=<em class="replaceable"><code>value2</code></em> ...</pre><div class="para">
+ Specifying two matches for the same field results in a logical <code class="function">OR</code> combination of the matches. Entries matching <em class="replaceable"><code>value1</code></em> or <em class="replaceable"><code>value2</code></em> are displayed.
+ </div><div class="para">
+ Also, you can specify multiple field-value pairs to further reduce the output set:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <em class="replaceable"><code>fieldname1</code></em>=<em class="replaceable"><code>value</code></em> <em class="replaceable"><code>fieldname2</code></em>=<em class="replaceable"><code>value</code></em> ...</pre><div class="para">
+ If two matches for different field names are specified, they will be combined with a logical <code class="function">AND</code>. Entries have to match both conditions to be shown.
+ </div><div class="para">
+ With use of the <span class="emphasis"><em>+</em></span> symbol, you can set a logical <code class="function">OR</code> combination of matches for multiple fields:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <em class="replaceable"><code>fieldname1</code></em>=<em class="replaceable"><code>value</code></em> + <em class="replaceable"><code>fieldname2</code></em>=<em class="replaceable"><code>value</code></em> ...</pre><div class="para">
+ This command returns entries that match at least one of the conditions, not only those that match both of them.
+ </div><div class="example" id="ex-advanced_filtering"><h6>Example 17.19. Advanced filtering</h6><div class="example-contents"><div class="para">
+ To display entries created by <code class="systemitem">avahi-daemon.service</code> or <code class="systemitem">crond.service</code> under user with UID 70, use the following command:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="literal">_UID=70</code> <code class="literal">_SYSTEMD_UNIT=avahi-daemon.service</code> <code class="literal">_SYSTEMD_UNIT=crond.service</code></pre><div class="para">
+ Since there are two values set for the <code class="literal">_SYSTEMD_UNIT</code> field, both results will be displayed, but only when matching the <code class="literal">_UID=70</code> condition. This can be expressed simply as: (UID=70 and (avahi or cron)).
+ </div></div></div><br class="example-break" /><div class="para">
+ You can apply the aforementioned filtering also in the live-view mode to keep track of the latest changes in the selected group of log entries:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-f</code> <em class="replaceable"><code>fieldname</code></em>=<em class="replaceable"><code>value</code></em> ...</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-Using_The_Live_View.html"><strong>Prev</strong>17.8.3. Using The Live View</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-Enabling_Persistent_Storage.html"><strong>Next</strong>17.8.5. Enabling Persistent Storage</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Rulesets.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Rulesets.html
new file mode 100644
index 0000000..398d111
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Rulesets.html
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2.7. Rulesets</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-basic_configuration_of_rsyslog.html" title="17.2. Basic Configuration of Rsyslog" /><link rel="prev" href="s2-using_the_new_configuration_format.html" title="17.2.6. Using the New Configuration Format" /><link rel="next" href="s2-compatibility_with_syslogd.html" title="17.2.8. Compatibility with syslogd" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2
-using_the_new_configuration_format.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-compatibility_with_syslogd.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-Rulesets"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.7. Rulesets</h3></div></div></div><div class="para">
+ Leaving special directives aside, <span class="application"><strong>rsyslog</strong></span> handles messages as defined by <span class="emphasis"><em>rules</em></span> that consist of a filter condition and an action to be performed if the condition is true. With a traditionally written <code class="filename">/etc/rsyslog.conf</code> file, all rules are evaluated in order of appearance for every input message. This process starts with the first rule and continues until all rules have been processed or until the message is discarded by one of the rules.
+ </div><div class="para">
+ However, rules can be grouped into sequences called <em class="firstterm">rulesets</em>. With rulesets, you can limit the effect of certain rules only to selected inputs or enhance the performance of <span class="application"><strong>rsyslog</strong></span> by defining a distinct set of actions bound to a specific input. In other words, filter conditions that will be inevitably evaluated as false for certain types of messages can be skipped. With the new configuration format, the <code class="function">input()</code> and <code class="function">ruleset()</code> statements are reserved for this operation. The ruleset definition in <code class="filename">/etc/rsyslog.conf</code> can look as follows:
+ </div><pre class="screen">
+ruleset(name="<em class="replaceable"><code>rulesetname</code></em>") {
+ <em class="replaceable"><code>rule</code></em>
+ <em class="replaceable"><code>rule2</code></em>
+ call <em class="replaceable"><code>rulesetname2</code></em>
+ …
+}
+</pre><div class="para">
+ Replace <em class="replaceable"><code>rulesetname</code></em> with an identifier for your ruleset. The ruleset name cannot start with <code class="literal">RSYSLOG_</code> since this namespace is reserved for use by <span class="application"><strong>rsyslog</strong></span>. <code class="literal">RSYSLOG_DefaultRuleset</code> then defines the default set of rules to be performed if the message has no other ruleset assigned. With <em class="replaceable"><code>rule</code></em> and <em class="replaceable"><code>rule2</code></em> you can define rules in filter-action format mentioned above. With the <em class="parameter"><code>call</code></em> parameter, you can nest rulesets by calling them from inside other ruleset blocks.
+ </div><div class="para">
+ After creating a ruleset, you need to specify what input it will apply to:
+ </div><pre class="synopsis">input(type="<em class="replaceable"><code>input_type</code></em>" port="<em class="replaceable"><code>port_num</code></em>" ruleset="<em class="replaceable"><code>rulesetname</code></em>");</pre><div class="para">
+ Here you can identify an input message by <em class="replaceable"><code>input_type</code></em>, which is an input module that gathered the message, or by <em class="replaceable"><code>port_num</code></em> – the port number. Other parameters such as <span class="emphasis"><em>file</em></span> or <span class="emphasis"><em>tag</em></span> can be specified for <code class="function">input()</code>. Replace <em class="replaceable"><code>rulesetname</code></em> with a name of the ruleset to be evaluated against the message. In case an input message is not explicitly bound to a ruleset, the default ruleset is triggered.
+ </div><div class="para">
+ You can also use the legacy format to define rulesets, for more information see <a class="xref" href="s1-log-files-additional-resources.html#brid-Log_Files-Resources-Online">the section called “Online Documentation”</a>.
+ </div><div class="example" id="ex-using_rulesets"><h6>Example 17.11. Using rulesets</h6><div class="example-contents"><div class="para">
+ The following rulesets ensure different handling of remote messages coming from different ports. Add the following into <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+ruleset(name="remote-10514") {
+ action(type="omfile" file="/var/log/remote-10514")
+}
+
+ruleset(name="remote-10515") {
+ cron.* action(type="omfile" file="/var/log/remote-10515-cron")
+ mail.* action(type="omfile" file="/var/log/remote-10515-mail")
+}
+
+input(type="imtcp" port="10514" ruleset="remote-10514");
+input(type="imtcp" port="10515" ruleset="remote-10515");
+</pre><div class="para">
+ Rulesets shown in the above example define log destinations for the remote input from two ports, in case of 10515, messages are sorted according to the facility. Then, the TCP input is enabled and bound to rulesets. Note that you must load the required modules (imtcp) for this configuration to work.
+ </div></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-using_the_new_configuration_format.html"><strong>Prev</strong>17.2.6. Using the New Configuration 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="s2-compatibility_with_syslogd.html"><strong>Next</strong>17.2.8. Compatibility with syslogd</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Templates.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Templates.html
new file mode 100644
index 0000000..2288210
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Templates.html
@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2.3. Templates</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-basic_configuration_of_rsyslog.html" title="17.2. Basic Configuration of Rsyslog" /><link rel="prev" href="s2-Actions.html" title="17.2.2. Actions" /><link rel="next" href="s2-global_directives.html" title="17.2.4. Global Directives" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-Actions.html"><strong>Prev</strong></a></li><li class="next"><a accessk
ey="n" href="s2-global_directives.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-Templates"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.3. Templates</h3></div></div></div><div class="para">
+ Any output that is generated by <span class="application"><strong>rsyslog</strong></span> can be modified and formatted according to your needs with the use of <span class="emphasis"><em>templates</em></span>. To create a template use the following syntax in <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">$template <em class="replaceable"><code>TEMPLATE_NAME</code></em>,"<em class="replaceable"><code>text %PROPERTY% more text</code></em>", [<span class="optional"><em class="replaceable"><code>OPTION</code></em></span>]</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>$template</code></em> 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, special characters, such as <code class="literal">\n</code> for new line or <code class="literal">\r</code> for carriage return, can be used. Other characters, such as <code class="literal">%</code> or <code class="literal">"</code>, have to be escaped if you want to use those characters literally.
+ </div></li><li class="listitem"><div class="para">
+ The text specified between two percent signs (<code class="literal">%</code>) specifies a <em class="firstterm">property</em> that allows you to access specific contents of a syslog message. For more information on properties, see <a class="xref" href="s2-Templates.html#brid-properties">the section called “Properties”</a>.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="parameter"><code>OPTION</code></em> attribute specifies any options that modify the template functionality. The currently supported template options are <em class="parameter"><code>sql</code></em> and <em class="parameter"><code>stdsql</code></em>, which are used for formatting the text as an SQL query.
+ </div><div class="note"><div class="admonition_header"><h2>The sql and stdsql options</h2></div><div class="admonition"><div class="para">
+ Note that the database writer checks whether the <em class="parameter"><code>sql</code></em> or <em class="parameter"><code>stdsql</code></em> options are specified in the template. If they are not, the database writer does not perform any action. This is to prevent any possible security threats, such as SQL injection.
+ </div><div class="para">
+ See section <em class="citetitle">Storing syslog messages in a database</em> in <a class="xref" href="s2-Actions.html">Section 17.2.2, “Actions”</a> for more information.
+ </div></div></div></li></ul></div><h4 id="brid-generating-dynamic-fnames">Generating Dynamic File Names</h4><div class="para">
+ Templates can be used to generate dynamic file names. By specifying a property as a part of the file path, a new file will be created for each unique property, which is a convenient way to classify syslog messages.
+ </div><div class="para">
+ For example, use the <em class="parameter"><code>timegenerated</code></em> property, which extracts a time stamp from the message, to generate a unique file name for each syslog message:
+ </div><pre class="screen">$template DynamicFile,"/var/log/test_logs/%timegenerated%-test.log"</pre><div class="para">
+ Keep in mind that the <em class="parameter"><code>$template</code></em> directive only specifies the template. You must use it inside a rule for it to take effect. In <code class="filename">/etc/rsyslog.conf</code>, use the question mark (<code class="literal">?</code>) in an action definition to mark the dynamic file name template:
+ </div><pre class="screen">*.* ?DynamicFile</pre><h4 id="brid-properties">Properties</h4><div class="para">
+ Properties defined inside a template (between two percent signs (<code class="literal">%</code>)) enable access various contents of a syslog message through the use of a <em class="firstterm">property replacer</em>. To define a property inside a template (between the two quotation marks (<code class="literal">"</code>…<code class="literal">"</code>)), use the following syntax:
+ </div><pre class="screen">%<em class="replaceable"><code>PROPERTY_NAME</code></em>[<span class="optional">:<em class="replaceable"><code>FROM_CHAR</code></em>:<em class="replaceable"><code>TO_CHAR</code></em>:<em class="replaceable"><code>OPTION</code></em></span>]%</pre><div class="para">
+ where:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>PROPERTY_NAME</code></em> attribute specifies the name of a property. A list of all available properties and their detailed description can be found in the <code class="filename">rsyslog.conf(5)</code> manual page under the section <span class="emphasis"><em>Available Properties</em></span>.
+ </div></li><li class="listitem"><div class="para">
+ <em class="replaceable"><code>FROM_CHAR</code></em> and <em class="replaceable"><code>TO_CHAR</code></em> attributes denote a range of characters that the specified property will act upon. Alternatively, regular expressions can be used to specify a range of characters. To do so, set the letter <code class="literal">R</code> as the <em class="replaceable"><code>FROM_CHAR</code></em> attribute and specify your desired regular expression as the <em class="replaceable"><code>TO_CHAR</code></em> attribute.
+ </div></li><li class="listitem"><div class="para">
+ The <em class="replaceable"><code>OPTION</code></em> attribute specifies any property options, such as the <code class="option">lowercase</code> option to convert the input to lowercase. A list of all available property options and their detailed description can be found in the <code class="filename">rsyslog.conf(5)</code> manual page under the section <span class="emphasis"><em>Property Options</em></span>.
+ </div></li></ul></div><div class="para">
+ The following are some examples of simple properties:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ The following property obtains the whole message text of a syslog message:
+ </div><pre class="screen">%msg%</pre></li><li class="listitem"><div class="para">
+ 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 time stamp that is generated when the syslog message is received and formats it according to the <a href="http://www.rfc-editor.org/info/rfc3999"><em class="citetitle">RFC 3999</em></a> date standard.
+ </div><pre class="screen">%timegenerated:1:10:date-rfc3339%</pre></li></ul></div><h4 id="brid-template-examples">Template Examples</h4><div class="para">
+ This section presents a few examples of <span class="application"><strong>rsyslog</strong></span> templates.
+ </div><div class="para">
+ <a class="xref" href="s2-Templates.html#example-temp1">Example 17.8, “A verbose syslog message template”</a> shows a template that formats a syslog message so that it outputs the message's severity, facility, the time stamp of when the message was received, the host name, the message tag, the message text, and ends with a new line.
+ </div><div class="example" id="example-temp1"><h6>Example 17.8. 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="s2-Templates.html#example-temp2">Example 17.9, “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 host name, message tag and a time stamp, on a new line (using <code class="literal">\r</code> and <code class="literal">\n</code>) and rings the bell (using <code class="literal">\7</code>).
+ </div><div class="example" id="example-temp2"><h6>Example 17.9. 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="s2-Templates.html#example-temp3">Example 17.10, “A database formatted message template”</a> shows a template that formats a syslog message so that it can be used as a database query. Notice the use of the <em class="parameter"><code>sql</code></em> option at the end of the template specified as the template option. It tells the database writer to format the message as an MySQL <code class="systemitem">SQL</code> query.
+ </div><div class="example" id="example-temp3"><h6>Example 17.10. A database formatted message template</h6><div class="example-contents"><pre class="screen">$template dbFormat,"insert into SystemEvents (Message, Facility, FromHost, Priority, DeviceReportedTime, ReceivedAt, InfoUnitID, SysLogTag) values ('%msg%', %syslogfacility%, '%HOSTNAME%', %syslogpriority%, '%timereported:::date-mysql%', '%timegenerated:::date-mysql%', %iut%, '%syslogtag%')", sql</pre></div></div><br class="example-break" /><div class="para">
+ <span class="application"><strong>rsyslog</strong></span> also contains a set of predefined templates identified by the <code class="literal">RSYSLOG_</code> prefix. These are reserved for the syslog's use and it is advisable to not create a template using this prefix to avoid conflicts. The following list shows these predefined templates along with their definitions.
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><em class="parameter"><code>RSYSLOG_DebugFormat</code></em></span></dt><dd><div class="para">
+ A special format used for troubleshooting property problems.
+ </div><pre class="screen">"Debug line with all properties:\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><div class="para">
+ The format specified in IETF's internet-draft ietf-syslog-protocol-23, which is assumed to become the new syslog standard RFC.
+ </div><pre class="screen">"%PRI%1 %TIMESTAMP:::date-rfc3339% %HOSTNAME% %APP-NAME% %PROCID% %MSGID% %STRUCTURED-DATA% %msg%\n\"</pre></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>RSYSLOG_FileFormat</code></em></span></dt><dd><div class="para">
+ A modern-style logfile format similar to TraditionalFileFormat, but with high-precision time stamps and time zone information.
+ </div><pre class="screen">"%TIMESTAMP:::date-rfc3339% %HOSTNAME% %syslogtag%%msg:::sp-if-no-1st-sp%%msg:::drop-last-lf%\n\"</pre></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>RSYSLOG_TraditionalFileFormat</code></em></span></dt><dd><div class="para">
+ The older default log file format with low-precision time stamps.
+ </div><pre class="screen">"%TIMESTAMP% %HOSTNAME% %syslogtag%%msg:::sp-if-no-1st-sp%%msg:::drop-last-lf%\n\"</pre></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>RSYSLOG_ForwardFormat</code></em></span></dt><dd><div class="para">
+ A forwarding format with high-precision time stamps and time zone information.
+ </div><pre class="screen">"%PRI%%TIMESTAMP:::date-rfc3339% %HOSTNAME% %syslogtag:1:32%%msg:::sp-if-no-1st-sp%%msg%\"</pre></dd><dt class="varlistentry"><span class="term"><em class="parameter"><code>RSYSLOG_TraditionalForwardFormat</code></em></span></dt><dd><div class="para">
+ The traditional forwarding format with low-precision time stamps.
+ </div><pre class="screen">"%PRI%%TIMESTAMP% %HOSTNAME% %syslogtag:1:32%%msg:::sp-if-no-1st-sp%%msg%\"</pre></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-Actions.html"><strong>Prev</strong>17.2.2. Actions</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-global_directives.html"><strong>Next</strong>17.2.4. Global Directives</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Using_The_Live_View.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Using_The_Live_View.html
new file mode 100644
index 0000000..b9230c6
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-Using_The_Live_View.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.8.3. Using The Live View</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-Using_the_Journal.html" title="17.8. Using the Journal" /><link rel="prev" href="s2-Access_Control.html" title="17.8.2. Access Control" /><link rel="next" href="s2-Filtering_Messages.html" title="17.8.4. Filtering Messages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-Access_Control.html"><strong>Prev</strong></a></li><li class="next"><a accesskey=
"n" href="s2-Filtering_Messages.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-Using_The_Live_View"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.8.3. Using The Live View</h3></div></div></div><div class="para">
+ When called without parameters, <code class="command">journalctl</code> shows the full list of entries, starting with the oldest entry collected. With the live view, you can supervise the log messages in real time as new entries are continuously printed as they appear. To start <span class="application"><strong>journalctl</strong></span> in live view mode, type:
+ </div><pre class="synopsis"><code class="command">journalctl</code> <code class="option">-f</code></pre><div class="para">
+ This command returns a list of the ten most current log lines. The <span class="application"><strong>journalctl</strong></span> utility then stays running and waits for new changes to show them immediately.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-Access_Control.html"><strong>Prev</strong>17.8.2. Access Control</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-Filtering_Messages.html"><strong>Next</strong>17.8.4. Filtering Messages</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-compatibility_with_syslogd.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-compatibility_with_syslogd.html
new file mode 100644
index 0000000..dcb58a9
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-compatibility_with_syslogd.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2.8. Compatibility with syslogd</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-basic_configuration_of_rsyslog.html" title="17.2. Basic Configuration of Rsyslog" /><link rel="prev" href="s2-Rulesets.html" title="17.2.7. Rulesets" /><link rel="next" href="s1-working_with_queues_in_rsyslog.html" title="17.3. Working with Queues in Rsyslog" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-Rulesets.html"><strong>Prev</strong></a></li>
<li class="next"><a accesskey="n" href="s1-working_with_queues_in_rsyslog.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-compatibility_with_syslogd"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.8. Compatibility with syslogd</h3></div></div></div><div class="para">
+ From <span class="application"><strong>rsyslog</strong></span> version 6, compatibility mode specified via the <code class="option">-c</code> option has been removed. Also, the syslogd-style command line options are deprecated and configuring <span class="application"><strong>rsyslog</strong></span> through these command line options should be avoided. However, you can use several templates and directives to configure <code class="systemitem">rsyslogd</code> to emulate syslogd-like behavior.
+ </div><div class="para">
+ For more information on various <code class="systemitem">rsyslogd</code> options, see the <code class="filename">rsyslogd(8)</code>manual page.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-Rulesets.html"><strong>Prev</strong>17.2.7. Rulesets</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-working_with_queues_in_rsyslog.html"><strong>Next</strong>17.3. Working with Queues in Rsyslog</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-mta-fetchmail.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-mta-fetchmail.html
index 423ba8a..d35f3a1 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-mta-fetchmail.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-mta-fetchmail.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-mta.html" title="10.3. Mail Transport Agents" /><link rel="prev" href="s2-email-mta-sendmail.html" title="10.3.2. Sendmail" /><link rel="next" href="s2-email-switchmail.html" title="10.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="n
ext"><a accesskey="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">10.3.3. Fetchmail</h3></div></div></div><a id="idm225478133984" class="indexterm"></a><a id="idm225476163984" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-mta.html" title="10.3. Mail Transport Agents" /><link rel="prev" href="s2-email-mta-sendmail.html" title="10.3.2. Sendmail" /><link rel="next" href="s2-email-switchmail.html" title="10.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="n
ext"><a accesskey="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">10.3.3. Fetchmail</h3></div></div></div><a id="idm261743509456" class="indexterm"></a><a id="idm261743508016" 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>:
@@ -16,7 +16,7 @@
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">10.3.3.1. Fetchmail Configuration Options</h4></div></div></div><a id="idm225460155440" class="indexterm"></a><a id="idm225460154000" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-email-mda-fetchmail-configuration"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.3.1. Fetchmail Configuration Options</h4></div></div></div><a id="idm261742456704" class="indexterm"></a><a id="idm261742455264" 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:
@@ -46,7 +46,7 @@ poll mail.domain2.com
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">10.3.3.2. Global Options</h4></div></div></div><a id="idm225445504832" class="indexterm"></a><a id="idm225445502912" class="indexterm"></a><div class="para">
+ </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">10.3.3.2. Global Options</h4></div></div></div><a id="idm261744943712" class="indexterm"></a><a id="idm261744941792" 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.
@@ -54,7 +54,7 @@ poll mail.domain2.com
<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">10.3.3.3. Server Options</h4></div></div></div><a id="idm225445474288" class="indexterm"></a><a id="idm225476961504" class="indexterm"></a><div class="para">
+ </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">10.3.3.3. Server Options</h4></div></div></div><a id="idm261759774608" class="indexterm"></a><a id="idm261759772688" 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.
@@ -66,7 +66,7 @@ poll mail.domain2.com
<code class="command">proto <em class="replaceable"><code>protocol</code></em> </code> — Replace <em class="replaceable"><code>protocol</code></em> with the protocol, such as <code class="command">pop3</code> or <code class="command">imap</code>, to use when checking for messages on the server.
</div></li><li class="listitem"><div class="para">
<code class="command">timeout <em class="replaceable"><code>seconds</code></em> </code> — Replace <em class="replaceable"><code>seconds</code></em> with the number of seconds of server inactivity after which Fetchmail gives up on a connection attempt. If this value is not set, a default of <code class="command">300</code> seconds is used.
- </div></li></ul></div></div><div class="section" id="s3-email-fetchmail-configuration-user"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.3.4. User Options</h4></div></div></div><a id="idm225506677600" class="indexterm"></a><a id="idm225506675680" class="indexterm"></a><div class="para">
+ </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">10.3.3.4. User Options</h4></div></div></div><a id="idm261739525760" class="indexterm"></a><a id="idm261739523840" 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.
@@ -86,11 +86,11 @@ poll mail.domain2.com
<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">10.3.3.5. Fetchmail Command Options</h4></div></div></div><a id="idm225445565104" class="indexterm"></a><div class="para">
+ </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">10.3.3.5. Fetchmail Command Options</h4></div></div></div><a id="idm261756557808" 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">10.3.3.6. Informational or Debugging Options</h4></div></div></div><a id="idm225436939456" class="indexterm"></a><div class="para">
+ </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">10.3.3.6. Informational or Debugging Options</h4></div></div></div><a id="idm261778478736" 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.
@@ -100,7 +100,7 @@ poll mail.domain2.com
<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">10.3.3.7. Special Options</h4></div></div></div><a id="idm225474713440" class="indexterm"></a><div class="para">
+ </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">10.3.3.7. Special Options</h4></div></div></div><a id="idm261724370656" 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.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-mta-sendmail.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-mta-sendmail.html
index ebb5759..9e004b5 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-mta-sendmail.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-mta-sendmail.html
@@ -6,15 +6,15 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-mta.html" title="10.3. Mail Transport Agents" /><link rel="prev" href="s1-email-mta.html" title="10.3. Mail Transport Agents" /><link rel="next" href="s2-email-mta-fetchmail.html" title="10.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-emai
l-mta-fetchmail.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">10.3.2. Sendmail</h3></div></div></div><a id="idm225470168256" class="indexterm"></a><a id="idm225470166816" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-mta.html" title="10.3. Mail Transport Agents" /><link rel="prev" href="s1-email-mta.html" title="10.3. Mail Transport Agents" /><link rel="next" href="s2-email-mta-fetchmail.html" title="10.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-emai
l-mta-fetchmail.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">10.3.2. Sendmail</h3></div></div></div><a id="idm261754446016" class="indexterm"></a><a id="idm261754444576" class="indexterm"></a><div class="para">
Sendmail's core purpose, like other MTAs, is to safely transfer email among hosts, usually using the <code class="systemitem">SMTP</code> protocol. Note that Sendmail is considered deprecated and users are encouraged to use Postfix when possible. See <a class="xref" href="s1-email-mta.html#s2-email-mta-postfix">Section 10.3.1, “Postfix”</a> for more information.
- </div><div class="section" id="s3-email-mta-sendmail-purpose"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.1. Purpose and Limitations</h4></div></div></div><a id="idm225471737936" class="indexterm"></a><a id="idm225471736496" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-email-mta-sendmail-purpose"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.1. Purpose and Limitations</h4></div></div></div><a id="idm261754440496" class="indexterm"></a><a id="idm261761575488" class="indexterm"></a><div class="para">
It is important to be aware of what Sendmail is and what it can do, as opposed to what it is not. In these days of monolithic applications that fulfill multiple roles, Sendmail may seem like the only application needed to run an email server within an organization. Technically, this is true, as Sendmail can spool mail to each users' directory and deliver outbound mail for users. However, most users actually require much more than simple email delivery. Users usually want to interact with their email using an MUA, that uses <code class="systemitem">POP</code> or <code class="systemitem">IMAP</code>, to download their messages to their local machine. Or, they may prefer a Web interface to gain access to their mailbox. These other applications can work in conjunction with Sendmail, but they actually exist for different reasons and can operate separately from one another.
</div><div class="para">
It is beyond the scope of this section to go into all that Sendmail should or could be configured to do. With literally hundreds of different options and rule sets, entire volumes have been dedicated to helping explain everything that can be done and how to fix things that go wrong. See the <a class="xref" href="s1-email-additional-resources.html">Section 10.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">10.3.2.2. The Default Sendmail Installation</h4></div></div></div><a id="idm225501126608" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-mta-sendmail-default"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.2. The Default Sendmail Installation</h4></div></div></div><a id="idm261747757264" 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>:
@@ -45,9 +45,9 @@
</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 commands, as <code class="systemitem">root</code>:
-<pre class="screen">~]# <code class="command">cd /etc/mail</code>
-~]# <code class="command">make all</code></pre>
+ Several of the configuration files in the <code class="filename">/etc/mail/</code> directory, such as <code class="filename">access</code>, <code class="filename">domaintable</code>, <code class="filename">mailertable</code> and <code class="filename">virtusertable</code>, must actually store their information in database files before Sendmail can use any configuration changes. To include any changes made to these configurations in their database files, run the following commands, as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">cd /etc/mail/</code>
+~]# <code class="command">make all</code></pre>
This will update <code class="filename">virtusertable.db</code>, <code class="filename">access.db</code>, <code class="filename">domaintable.db</code>, <code class="filename">mailertable.db</code>, <code class="filename">sendmail.cf</code>, and <code class="filename">submit.cf</code>.
</div><div class="para">
To update all the database files listed above and to update a custom database file, use a command in the following format: <pre class="synopsis"><code class="command">make <em class="replaceable"><code>name.db</code></em> all</code></pre> where <em class="replaceable"><code>name</code></em> represents the name of the custom database file to be updated.
@@ -62,7 +62,7 @@
To finalize the change, the <code class="filename">virtusertable.db</code> file must be updated:
</div><pre class="screen">~]# <code class="command">make <code class="filename">virtusertable.db</code> all</code></pre><div class="para">
Using the <code class="option">all</code> option will result in the <code class="filename">virtusertable.db</code> and <code class="filename">access.db</code> being updated at the same time.
- </div></div><div class="section" id="s3-email-mta-sendmail-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.3. Common Sendmail Configuration Changes</h4></div></div></div><a id="idm225471715312" class="indexterm"></a><a id="idm225498216080" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-mta-sendmail-changes"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.3. Common Sendmail Configuration Changes</h4></div></div></div><a id="idm261754102976" class="indexterm"></a><a id="idm261754101568" 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 replacing or making any changes to the <code class="filename">sendmail.cf</code> file, create a backup copy.
@@ -73,8 +73,8 @@
</div><pre class="screen">~]# <code class="command">systemctl restart sendmail</code></pre></div></div><div class="para">
The default configuration in Fedora works for most <code class="systemitem">SMTP</code>-only sites. However, it does not work for <em class="firstterm">UUCP</em> (<em class="firstterm">UNIX-to-UNIX Copy Protocol</em>) sites. If using UUCP mail transfers, the <code class="filename">/etc/mail/sendmail.mc</code> file must be reconfigured and a new <code class="filename">/etc/mail/sendmail.cf</code> file must be generated.
</div><div class="para">
- Consult the <code class="filename">/usr/share/sendmail-cf/README</code> file before editing any files in the directories under the <code class="filename">/usr/share/sendmail-cf</code> directory, as they can affect the future configuration of the <code class="filename">/etc/mail/sendmail.cf</code> file.
- </div></div><div class="section" id="s3-email-sendmail-changes-masquerading"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.4. Masquerading</h4></div></div></div><a id="idm225464947808" class="indexterm"></a><a id="idm225464946368" class="indexterm"></a><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">10.3.2.4. Masquerading</h4></div></div></div><a id="idm261741354352" class="indexterm"></a><a id="idm261741352912" class="indexterm"></a><div class="para">
One common Sendmail configuration is to have a single machine act as a mail gateway for all machines on the network. For example, a company may want to have a machine called <code class="computeroutput">mail.example.com</code> that handles all of their email and assigns a consistent return address to all outgoing mail.
</div><div class="para">
In this situation, the Sendmail server must masquerade the machine names on the company network so that their return address is <code class="computeroutput">user at example.com</code> instead of <code class="computeroutput">user at host.example.com</code>.
@@ -88,7 +88,7 @@ MASQUERADE_AS(`example.com.')dnl
MASQUERADE_DOMAIN(`example.com.')dnl
MASQUERADE_AS(example.com)dnl</pre><div class="para">
After generating a new <code class="filename">sendmail.cf</code> file using the <code class="command">m4</code> macro processor, this configuration makes all mail from inside the network appear as if it were sent from <code class="systemitem">example.com</code>.
- </div></div><div class="section" id="s3-email-sendmail-stopping-spam"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.5. Stopping Spam</h4></div></div></div><a id="idm225435475808" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-sendmail-stopping-spam"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.5. Stopping Spam</h4></div></div></div><a id="idm261748238176" 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>.
@@ -106,7 +106,7 @@ MASQUERADE_AS(example.com)dnl</pre><div class="para">
The above examples only represent a small part of what Sendmail can do in terms of allowing or blocking access. See the <code class="filename">/usr/share/sendmail-cf/README</code> file for more information and examples.
</div><div class="para">
Since Sendmail calls the Procmail MDA when delivering mail, it is also possible to use a spam filtering program, such as SpamAssassin, to identify and file spam for users. See <a class="xref" href="s2-email-procmail-recipes.html#s3-email-mda-spam">Section 10.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">10.3.2.6. Using Sendmail with LDAP</h4></div></div></div><a id="idm225449910496" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-mta-sendmail-ldap"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.3.2.6. Using Sendmail with LDAP</h4></div></div></div><a id="idm261718592704" 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.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-procmail-recipes.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-procmail-recipes.html
index 5dfb36b..4519b53 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-procmail-recipes.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-procmail-recipes.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-mda.html" title="10.4. Mail Delivery Agents" /><link rel="prev" href="s1-email-mda.html" title="10.4. Mail Delivery Agents" /><link rel="next" href="s1-email-mua.html" title="10.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.h
tml"><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">10.4.2. Procmail Recipes</h3></div></div></div><a id="idm225455908608" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-mda.html" title="10.4. Mail Delivery Agents" /><link rel="prev" href="s1-email-mda.html" title="10.4. Mail Delivery Agents" /><link rel="next" href="s1-email-mua.html" title="10.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.h
tml"><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">10.4.2. Procmail Recipes</h3></div></div></div><a id="idm261751178656" class="indexterm"></a><div class="para">
New users often find the construction of recipes the most difficult part of learning to use Procmail. This difficulty is often attributed to recipes matching messages by using <em class="firstterm">regular expressions</em> which are used to specify qualifications for string matching. However, regular expressions are not very difficult to construct and even less difficult to understand when read. Additionally, the consistency of the way Procmail recipes are written, regardless of regular expressions, makes it easy to learn by example. To see example Procmail recipes, see <a class="xref" href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-examples">Section 10.4.2.5, “Recipe Examples”</a>.
</div><div class="para">
Procmail recipes take the following form:
@@ -21,11 +21,11 @@
A recipe can contain several conditions to match against the message. If it has no conditions, every message matches the recipe. Regular expressions are placed in some conditions to facilitate message matching. If multiple conditions are used, they must all match for the action to be performed. Conditions are checked based on the flags set in the recipe's first line. Optional special characters placed after the asterisk character (<code class="command">*</code>) can further control the condition.
</div><div class="para">
The <code class="command"><em class="replaceable"><code>action-to-perform</code></em></code> argument specifies the action taken when the message matches one of the conditions. There can only be one action per recipe. In many cases, the name of a mailbox is used here to direct matching messages into that file, effectively sorting the email. Special action characters may also be used before the action is specified. See <a class="xref" href="s2-email-procmail-recipes.html#s3-email-procmail-recipes-special">Section 10.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">10.4.2.1. Delivering vs. Non-Delivering Recipes</h4></div></div></div><a id="idm225438588880" class="indexterm"></a><a id="idm225468287312" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s2-email-procmail-recipes-delivering"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.4.2.1. Delivering vs. Non-Delivering Recipes</h4></div></div></div><a id="idm261726428160" class="indexterm"></a><a id="idm261746833136" 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">10.4.2.2. Flags</h4></div></div></div><a id="idm225445954144" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-procmail-recipes-flags"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.4.2.2. Flags</h4></div></div></div><a id="idm261746825952" class="indexterm"></a><div class="para">
Flags are essential to determine how or if a recipe's conditions are compared to a message. The <span class="application"><strong>egrep</strong></span> utility is used internally for matching of the conditions. The following flags are commonly used:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">A</code> — Specifies that this recipe is only used if the previous recipe without an <code class="command">A</code> or <code class="command">a</code> flag also matched this message.
@@ -55,11 +55,11 @@
<code class="command">W</code> — Is identical to <code class="command">w</code> except that "Program failure" messages are suppressed.
</div></li></ul></div><div class="para">
For a detailed list of additional flags, see the <code class="filename">procmailrc</code> man page.
- </div></div><div class="section" id="s3-email-procmail-recipes-lockfile"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.4.2.3. Specifying a Local Lockfile</h4></div></div></div><a id="idm225498130240" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-procmail-recipes-lockfile"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.4.2.3. Specifying a Local Lockfile</h4></div></div></div><a id="idm261786678096" 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">10.4.2.4. Special Conditions and Actions</h4></div></div></div><a id="idm225450421552" class="indexterm"></a><a id="idm225450419632" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-procmail-recipes-special"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.4.2.4. Special Conditions and Actions</h4></div></div></div><a id="idm261751390704" class="indexterm"></a><a id="idm261751388784" 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:
@@ -81,7 +81,7 @@
<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">10.4.2.5. Recipe Examples</h4></div></div></div><a id="idm225446606704" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-procmail-recipes-examples"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.4.2.5. Recipe Examples</h4></div></div></div><a id="idm261749248016" 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. The proper use and adaptation of regular expressions can be derived by viewing these recipe examples. In addition, introductory information about basic regular expression rules can be found in the <code class="filename">grep(1)</code> man page.
@@ -112,7 +112,7 @@ tuxlug</pre><div class="para">
Any messages sent from the <code class="computeroutput">tux-lug at domain.com</code> mailing list are placed in the <code class="filename">tuxlug</code> mailbox automatically for the MUA. Note that the condition in this example matches the message if it has the mailing list's email address on the <code class="computeroutput">From</code>, <code class="computeroutput">Cc</code>, or <code class="computeroutput">To</code> lines.
</div><div class="para">
Consult the many Procmail online resources available in <a class="xref" href="s1-email-additional-resources.html">Section 10.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">10.4.2.6. Spam Filters</h4></div></div></div><a id="idm225476040160" class="indexterm"></a><a id="idm225476038240" class="indexterm"></a><a id="idm225458363520" class="indexterm"></a><div class="para">
+ </div></div><div class="section" id="s3-email-mda-spam"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">10.4.2.6. Spam Filters</h4></div></div></div><a id="idm261723359712" class="indexterm"></a><a id="idm261723357792" class="indexterm"></a><a id="idm261723356352" 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.
@@ -136,7 +136,7 @@ tuxlug</pre><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">
+ </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">
See <a class="xref" href="ch-Services_and_Daemons.html">Chapter 6, <em>Services and Daemons</em></a> for more information on how to configure services in Fedora.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-related-books.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-related-books.html
index 8b8fb68..a570fdc 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-related-books.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-related-books.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-additional-resources.html" title="10.6. Additional Resources" /><link rel="prev" href="s2-email-useful-websites.html" title="10.6.2. Useful Websites" /><link rel="next" href="ch-Directory_Servers.html" title="Chapter 11. 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="next"><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">10.6.3. Related Books</h3></div></div></div><a id="idm225475637200" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-additional-resources.html" title="10.6. Additional Resources" /><link rel="prev" href="s2-email-useful-websites.html" title="10.6.2. Useful Websites" /><link rel="next" href="ch-Directory_Servers.html" title="Chapter 11. 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="next"><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">10.6.3. Related Books</h3></div></div></div><a id="idm261740740112" 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.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-switchmail.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-switchmail.html
index 02f4e25..f86abbd 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-switchmail.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-switchmail.html
@@ -6,10 +6,10 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-mta.html" title="10.3. Mail Transport Agents" /><link rel="prev" href="s2-email-mta-fetchmail.html" title="10.3.3. Fetchmail" /><link rel="next" href="s1-email-mda.html" title="10.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-mda.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">10.3.4. Mail Transport Agent (MTA) Configuration</h3></div></div></div><a id="idm225442591840" class="indexterm"></a><a id="idm225442590400" class="indexterm"></a><a id="idm225442588960" class="indexterm"></a><a id="idm225442587232" class="indexterm"></a><a id="idm225499508656" class="indexterm"></a><a id="idm225499507696" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-mta.html" title="10.3. Mail Transport Agents" /><link rel="prev" href="s2-email-mta-fetchmail.html" title="10.3.3. Fetchmail" /><link rel="next" href="s1-email-mda.html" title="10.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-mda.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">10.3.4. Mail Transport Agent (MTA) Configuration</h3></div></div></div><a id="idm261738663872" class="indexterm"></a><a id="idm261738662432" class="indexterm"></a><a id="idm261738660992" class="indexterm"></a><a id="idm261738659264" class="indexterm"></a><a id="idm261738658176" class="indexterm"></a><a id="idm261738657216" class="indexterm"></a><div class="para">
A <em class="firstterm">Mail Transport Agent</em> (MTA) is essential for sending email. A <em class="firstterm">Mail User Agent</em> (MUA) such as <span class="application"><strong>Evolution</strong></span>, <span class="application"><strong>Thunderbird</strong></span>, and <span class="application"><strong>Mutt</strong></span>, is used to read and compose email. When a user sends an email from an MUA, the message is handed off to the MTA, which sends the message through a series of MTAs until it reaches its destination.
</div><div class="para">
Even if a user does not plan to send email from the system, some automated tasks or system programs might use the <code class="command">mail</code> command to send email containing log messages to the <code class="systemitem">root</code> user of the local system.
- </div><a id="idm225452476736" class="indexterm"></a><a id="idm225452475776" class="indexterm"></a><div class="para">
+ </div><a id="idm261741001808" class="indexterm"></a><a id="idm261741000848" class="indexterm"></a><div class="para">
Fedora 21 provides two MTAs: Postfix and Sendmail. If both are installed, Postfix is the default MTA. Note that Sendmail is considered deprecated in MAJOROS;.
</div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-email-mta-fetchmail.html"><strong>Prev</strong>10.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>10.4. Mail Delivery Agents</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-types-mda.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-types-mda.html
index 3942a57..5be7653 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-types-mda.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-types-mda.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-types.html" title="10.2. Email Program Classifications" /><link rel="prev" href="s1-email-types.html" title="10.2. Email Program Classifications" /><link rel="next" href="s2-email-types-mua.html" title="10.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 acc
esskey="n" href="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">10.2.2. Mail Delivery Agent</h3></div></div></div><a id="idm225462889232" class="indexterm"></a><a id="idm225469017344" class="indexterm"></a><a id="idm225469015904" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-types.html" title="10.2. Email Program Classifications" /><link rel="prev" href="s1-email-types.html" title="10.2. Email Program Classifications" /><link rel="next" href="s2-email-types-mua.html" title="10.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 acc
esskey="n" href="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">10.2.2. Mail Delivery Agent</h3></div></div></div><a id="idm261714665600" class="indexterm"></a><a id="idm261714663680" class="indexterm"></a><a id="idm261738046448" 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.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-types-mua.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-types-mua.html
index 22ec9ae..d93b20a 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-types-mua.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-types-mua.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-types.html" title="10.2. Email Program Classifications" /><link rel="prev" href="s2-email-types-mda.html" title="10.2.2. Mail Delivery Agent" /><link rel="next" href="s1-email-mta.html" title="10.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 acces
skey="n" href="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">10.2.3. Mail User Agent</h3></div></div></div><a id="idm225463247168" class="indexterm"></a><a id="idm225463245248" class="indexterm"></a><a id="idm225458647024" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-types.html" title="10.2. Email Program Classifications" /><link rel="prev" href="s2-email-types-mda.html" title="10.2.2. Mail Delivery Agent" /><link rel="next" href="s1-email-mta.html" title="10.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 acces
skey="n" href="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">10.2.3. Mail User Agent</h3></div></div></div><a id="idm261787177072" class="indexterm"></a><a id="idm261787175152" class="indexterm"></a><a id="idm261787173712" class="indexterm"></a><div class="para">
A <em class="firstterm">Mail User Agent</em> (<em class="firstterm">MUA</em>) is synonymous with an email client application. An MUA is a program that, at a minimum, allows a user to read and compose email messages. Many MUAs are capable of retrieving messages via the <code class="systemitem">POP</code> or <code class="systemitem">IMAP</code> protocols, setting up mailboxes to store messages, and sending outbound messages to an MTA.
</div><div class="para">
MUAs may be graphical, such as <span class="application"><strong>Evolution</strong></span>, or have simple text-based interfaces, such as <span class="application"><strong>Mutt</strong></span>.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-useful-websites.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-useful-websites.html
index 7c5de42..d3b852f 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-useful-websites.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-email-useful-websites.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-additional-resources.html" title="10.6. Additional Resources" /><link rel="prev" href="s1-email-additional-resources.html" title="10.6. Additional Resources" /><link rel="next" href="s2-email-related-books.html" title="10.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 class="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">10.6.2. Useful Websites</h3></div></div></div><a id="idm225497754736" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-email-additional-resources.html" title="10.6. Additional Resources" /><link rel="prev" href="s1-email-additional-resources.html" title="10.6. Additional Resources" /><link rel="next" href="s2-email-related-books.html" title="10.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 class="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">10.6.2. Useful Websites</h3></div></div></div><a id="idm261748908176" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://www.sendmail.org/">http://www.sendmail.org/</a> — Offers a thorough technical breakdown of Sendmail features, documentation and configuration examples.
</div></li><li class="listitem"><div class="para">
<a href="http://www.sendmail.com/">http://www.sendmail.com/</a> — Contains news, interviews and articles concerning Sendmail, including an expanded view of the many options available.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-enabling_encrypted_transport.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-enabling_encrypted_transport.html
new file mode 100644
index 0000000..8f84432
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-enabling_encrypted_transport.html
@@ -0,0 +1,15 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.4.3. Enabling Encrypted Transport</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-using_rsyslog_modules.html" title="17.4. Using Rsyslog Modules" /><link rel="prev" href="s2-exporting_messages_to_a_database.html" title="17.4.2. Exporting Messages to a Database" /><link rel="next" href="s2-using_RELP.html" title="17.4.4. Using RELP" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-exporting_messages_to_a_database.html"><strong>Prev</
strong></a></li><li class="next"><a accesskey="n" href="s2-using_RELP.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-enabling_encrypted_transport"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.4.3. Enabling Encrypted Transport</h3></div></div></div><div class="para">
+ Confidentiality and integrity in network transmissions can be provided by either the <span class="emphasis"><em>TLS</em></span> or <span class="emphasis"><em>GSSAPI</em></span> encryption protocol.
+ </div><div class="para">
+ <span class="emphasis"><em>Transport Layer Security</em></span> (TLS) is a cryptographic protocol designed to provide communication security over the network. When using TLS, rsyslog messages are encrypted before sending, and mutual authentication exists between the sender and receiver.
+ </div><div class="para">
+ <span class="emphasis"><em>Generic Security Service API</em></span> (GSSAPI) is an application programming interface for programs to access security services. To use it in connection with <span class="application"><strong>rsyslog</strong></span> you must have a functioning <span class="application"><strong>Kerberos</strong></span> environment.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-exporting_messages_to_a_database.html"><strong>Prev</strong>17.4.2. Exporting Messages to a 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="s2-using_RELP.html"><strong>Next</strong>17.4.4. Using RELP</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-exporting_messages_to_a_database.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-exporting_messages_to_a_database.html
new file mode 100644
index 0000000..18ff203
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-exporting_messages_to_a_database.html
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.4.2. Exporting Messages to a Database</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-using_rsyslog_modules.html" title="17.4. Using Rsyslog Modules" /><link rel="prev" href="s1-using_rsyslog_modules.html" title="17.4. Using Rsyslog Modules" /><link rel="next" href="s2-enabling_encrypted_transport.html" title="17.4.3. Enabling Encrypted Transport" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-using_rsyslog_modules.html"><strong>Prev<
/strong></a></li><li class="next"><a accesskey="n" href="s2-enabling_encrypted_transport.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-exporting_messages_to_a_database"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.4.2. Exporting Messages to a Database</h3></div></div></div><div class="para">
+ Processing of log data can be faster and more convenient when performed in a database rather than with text files. Based on the type of DBMS used, choose from various output modules such as <code class="command">ommysql</code>, <code class="command">ompgsql</code>, <code class="command">omoracle</code>, or <code class="command">ommongodb</code>. As an alternative, use the generic <code class="command">omlibdbi</code> output module that relies on the <code class="systemitem">libdbi</code> library. The <code class="command">omlibdbi</code> module supports database systems Firebird/Interbase, MS SQL, Sybase, SQLite, Ingres, Oracle, mSQL, MySQL, and PostgreSQL.
+ </div><div class="example" id="ex-exporting_rsyslog_messages_to_a_database"><h6>Example 17.14. Exporting Rsyslog Messages to a Database</h6><div class="example-contents"><div class="para">
+ To store the rsyslog messages in a MySQL database, add the following into <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad ommysql
+
+$ActionOmmysqlServerPort 1234
+*.* :ommysql:database-server,database-name,database-userid,database-password
+</pre><div class="para">
+ First, the output module is loaded, then the communication port is specified. Additional information, such as name of the server and the database, and authentication data, is specified on the last line of the above example.
+ </div></div></div><br class="example-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-using_rsyslog_modules.html"><strong>Prev</strong>17.4. Using Rsyslog 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-enabling_encrypted_transport.html"><strong>Next</strong>17.4.3. Enabling Encrypted Transport</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-filtering_structured_messages.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-filtering_structured_messages.html
new file mode 100644
index 0000000..de40861
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-filtering_structured_messages.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.6.2. Filtering Structured Messages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-structured_logging_with_rsyslog.html" title="17.6. Structured Logging with Rsyslog" /><link rel="prev" href="s1-structured_logging_with_rsyslog.html" title="17.6. Structured Logging with Rsyslog" /><link rel="next" href="s2-parsing_JSON.html" title="17.6.3. Parsing JSON" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-structured_logging_with_rsyslog.h
tml"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-parsing_JSON.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-filtering_structured_messages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.6.2. Filtering Structured Messages</h3></div></div></div><div class="para">
+ To create a lumberjack-formatted message that is required by <span class="application"><strong>rsyslog</strong></span>'s parsing module, use the following template:
+ </div><pre class="screen">
+template(name="CEETemplate" type="string" string="%TIMESTAMP% %HOSTNAME% %syslogtag% @cee: %$!all-json%\n")
+</pre><div class="para">
+ This template prepends the <code class="literal">@cee:</code> string to the JSON string and can be applied, for example, when creating an output file with <code class="systemitem">omfile</code> module. To access JSON field names, use the <span class="bold bold"><strong>$!</strong></span> prefix. For example, the following filter condition searches for messages with specific <span class="emphasis"><em>hostname</em></span> and <span class="emphasis"><em>UID</em></span> :
+ </div><pre class="screen">
+($!hostname == "<em class="replaceable"><code>hostname</code></em>" && $!UID== "<em class="replaceable"><code>UID</code></em>")
+</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-structured_logging_with_rsyslog.html"><strong>Prev</strong>17.6. Structured Logging with Rsyslog</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-parsing_JSON.html"><strong>Next</strong>17.6.3. Parsing JSON</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-resources.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-resources.html
index 3ee5b80..98ef1c9 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-resources.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-resources.html
@@ -6,9 +6,9 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-FTP.html" title="12.2. FTP" /><link rel="prev" href="s2-ftp-vsftpd-conf.html" title="12.2.5. vsftpd Configuration Options" /><link rel="next" href="sec-Printer_Configuration.html" title="12.3. Printer 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-ftp-vsftpd-conf.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" hr
ef="sec-Printer_Configuration.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">12.2.6. Additional Resources</h3></div></div></div><a id="idm225475509152" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-FTP.html" title="12.2. FTP" /><link rel="prev" href="s2-ftp-vsftpd-conf.html" title="12.2.5. vsftpd Configuration Options" /><link rel="next" href="sec-Printer_Configuration.html" title="12.3. Printer 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-ftp-vsftpd-conf.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" hr
ef="sec-Printer_Configuration.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">12.2.6. Additional Resources</h3></div></div></div><a id="idm261715141456" 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">12.2.6.1. Installed Documentation</h4></div></div></div><a id="idm225468470048" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><div class="section" id="s3-ftp-installed-documentation"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.6.1. Installed Documentation</h4></div></div></div><a id="idm261754866112" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
The <code class="filename">/usr/share/doc/vsftpd/</code> directory — This directory contains a <code class="filename">README</code> with basic information about the software. The <code class="filename">TUNING</code> file contains basic performance tuning tips and the <code class="filename">SECURITY/</code> directory contains information about the security model employed by <code class="command">vsftpd</code>.
</div></li><li class="listitem"><div class="para">
<code class="command">vsftpd</code> related man pages — There are a number of man pages for the daemon and configuration files. The following lists some of the more important man pages.
@@ -18,7 +18,7 @@
<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">12.2.6.2. Useful Websites</h4></div></div></div><a id="idm225472617152" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </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">12.2.6.2. Useful Websites</h4></div></div></div><a id="idm261783208864" class="indexterm"></a><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<a href="http://vsftpd.beasts.org/">http://vsftpd.beasts.org/</a> — The <code class="command">vsftpd</code> project page is a great place to locate the latest documentation and to contact the author of the software.
</div></li><li class="listitem"><div class="para">
<a href="http://slacksite.com/other/ftp.html">http://slacksite.com/other/ftp.html</a> — This website provides a concise explanation of the differences between active and passive mode <code class="systemitem">FTP</code>.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-servers.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-servers.html
index 10e4710..9faefb9 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-servers.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-servers.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-FTP.html" title="12.2. FTP" /><link rel="prev" href="s1-FTP.html" title="12.2. FTP" /><link rel="next" href="s3-ftp-vsftpd-conf.html" title="12.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">12.2.2. FTP Servers</h3></div></div></div><a id="idm225466495360" class="indexterm"></a><a id="idm225475179232" class="indexterm"></a><a id="idm225503128384" class="indexterm"></a><a id="idm225480131696" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-FTP.html" title="12.2. FTP" /><link rel="prev" href="s1-FTP.html" title="12.2. FTP" /><link rel="next" href="s3-ftp-vsftpd-conf.html" title="12.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">12.2.2. FTP Servers</h3></div></div></div><a id="idm261726545264" class="indexterm"></a><a id="idm261756650768" class="indexterm"></a><a id="idm261759852880" class="indexterm"></a><a id="idm261738537424" class="indexterm"></a><div class="para">
Fedora ships with two different <code class="systemitem">FTP</code> servers:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="command">proftpd</code> - A fast, stable, and highly configurable FTP server.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-vsftpd-conf.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-vsftpd-conf.html
index 70ae8e1..f735ed0 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-vsftpd-conf.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-vsftpd-conf.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-FTP.html" title="12.2. FTP" /><link rel="prev" href="s2-ftp-vsftpd-start.html" title="12.2.4. Starting and Stopping vsftpd" /><link rel="next" href="s2-ftp-resources.html" title="12.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-resources.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">12.2.5. <code class="command">vsftpd</code> Configuration Options</h3></div></div></div><a id="idm225446020064" class="indexterm"></a><a id="idm225458648416" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-FTP.html" title="12.2. FTP" /><link rel="prev" href="s2-ftp-vsftpd-start.html" title="12.2.4. Starting and Stopping vsftpd" /><link rel="next" href="s2-ftp-resources.html" title="12.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-resources.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">12.2.5. <code class="command">vsftpd</code> Configuration Options</h3></div></div></div><a id="idm261723291984" class="indexterm"></a><a id="idm261726371632" 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:
@@ -22,7 +22,7 @@
For an overview of ways to secure <code class="command">vsftpd</code>, refer to the Fedora 21 <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">12.2.5.1. Daemon Options</h4></div></div></div><a id="idm225436146848" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-ftp-vsftpd-conf-opt-daemon"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.5.1. Daemon Options</h4></div></div></div><a id="idm261741197776" 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.
@@ -36,7 +36,7 @@
<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">12.2.5.2. Log In Options and Access Controls</h4></div></div></div><a id="idm225438743520" class="indexterm"></a><a id="idm225461790336" class="indexterm"></a><div class="para">
+ </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">12.2.5.2. Log In Options and Access Controls</h4></div></div></div><a id="idm261752141920" class="indexterm"></a><a id="idm261746412192" 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.
@@ -88,7 +88,7 @@
<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">12.2.5.3. Anonymous User Options</h4></div></div></div><a id="idm225477910864" class="indexterm"></a><div class="para">
+ </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">12.2.5.3. Anonymous User Options</h4></div></div></div><a id="idm261749544288" 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.
@@ -120,7 +120,7 @@
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">12.2.5.4. Local User Options</h4></div></div></div><a id="idm225504583040" class="indexterm"></a><div class="para">
+ </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">12.2.5.4. Local User Options</h4></div></div></div><a id="idm261763933216" 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.
@@ -166,7 +166,7 @@
<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">12.2.5.5. Directory Options</h4></div></div></div><a id="idm225474418688" class="indexterm"></a><div class="para">
+ </div></li></ul></div></div><div class="section" id="s3-ftp-vsftpd-conf-opt-dir"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.5.5. Directory Options</h4></div></div></div><a id="idm261754846816" 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.
@@ -196,7 +196,7 @@
<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">12.2.5.6. File Transfer Options</h4></div></div></div><a id="idm225467433216" class="indexterm"></a><div class="para">
+ </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">12.2.5.6. File Transfer Options</h4></div></div></div><a id="idm261757898704" 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.
@@ -214,7 +214,7 @@
<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">12.2.5.7. Logging Options</h4></div></div></div><a id="idm225478749680" class="indexterm"></a><div class="para">
+ </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">12.2.5.7. Logging Options</h4></div></div></div><a id="idm261737206816" 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).
@@ -250,7 +250,7 @@
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">12.2.5.8. Network Options</h4></div></div></div><a id="idm225476732416" class="indexterm"></a><div class="para">
+ </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">12.2.5.8. Network Options</h4></div></div></div><a id="idm261734650512" 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.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-vsftpd-start.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-vsftpd-start.html
index 8e9db16..3fbd033 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-vsftpd-start.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ftp-vsftpd-start.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-FTP.html" title="12.2. FTP" /><link rel="prev" href="s3-ftp-vsftpd-conf.html" title="12.2.3. Files Installed with vsftpd" /><link rel="next" href="s2-ftp-vsftpd-conf.html" title="12.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" h
ref="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">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </h3></div></div></div><a id="idm225447381120" class="indexterm"></a><a id="idm225480752768" class="indexterm"></a><a id="idm225442834224" class="indexterm"></a><a id="idm225498868208" class="indexterm"></a><a id="idm225469052064" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-FTP.html" title="12.2. FTP" /><link rel="prev" href="s3-ftp-vsftpd-conf.html" title="12.2.3. Files Installed with vsftpd" /><link rel="next" href="s2-ftp-vsftpd-conf.html" title="12.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" h
ref="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">12.2.4. Starting and Stopping <code class="command">vsftpd</code> </h3></div></div></div><a id="idm261726051056" class="indexterm"></a><a id="idm261751237072" class="indexterm"></a><a id="idm261723995504" class="indexterm"></a><a id="idm261726370144" class="indexterm"></a><a id="idm261759439104" 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:
@@ -22,12 +22,12 @@
To conditionally restart the server, as <code class="systemitem">root</code> type:
</div><pre class="screen"><code class="command">systemctl condrestart vsftpd.service</code></pre><div class="para">
By default, the <code class="command">vsftpd</code> service does <span class="emphasis"><em>not</em></span> start automatically at boot time. To configure the <code class="command">vsftpd</code> service to start at boot time, use a service manager such as <code class="command">systemctl</code>. See <a class="xref" href="ch-Services_and_Daemons.html">Chapter 6, <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">12.2.4.1. Starting Multiple Copies of <code class="command">vsftpd</code> </h4></div></div></div><a id="idm225478514288" class="indexterm"></a><a id="idm225435680896" class="indexterm"></a><div class="para">
+ </div><div class="section" id="s3-ftp-vsftpd-start-multi"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">12.2.4.1. Starting Multiple Copies of <code class="command">vsftpd</code> </h4></div></div></div><a id="idm261744710016" class="indexterm"></a><a id="idm261740645568" class="indexterm"></a><div class="para">
Sometimes one computer is used to serve multiple <code class="systemitem">FTP</code> domains. This is a technique called <em class="firstterm">multihoming</em>. One way to multihome using <code class="command">vsftpd</code> is by running multiple copies of the daemon, each with its own configuration file.
</div><div class="para">
- To do this, first assign all relevant <code class="systemitem">IP</code> addresses to network devices or alias network devices on the system. For more information about configuring network devices, device aliases, and additional information about network configuration scripts, refer to the <em class="citetitle">Red Hat Enterprise Linux 7 Networking Guide</em>.
+ To do this, first assign all relevant <code class="systemitem">IP</code> addresses to network devices or alias network devices on the system. For more information about configuring network devices, device aliases, and additional information about network configuration scripts, refer to the <a href="http://docs.fedoraproject.org/en-US/Fedora/21/html/Networking_Guide/index.html"><em class="citetitle">Fedora Networking Guide</em></a>.
</div><div class="para">
- Next, the DNS server for the <code class="systemitem">FTP</code> domains must be configured to reference the correct machine. For information about BIND and its configuration files, refer to the <em class="citetitle">Red Hat Enterprise Linux 7 Networking Guide</em>.
+ Next, the DNS server for the <code class="systemitem">FTP</code> domains must be configured to reference the correct machine. For information about BIND and its configuration files, refer to the <a href="http://docs.fedoraproject.org/en-US/Fedora/21/html/Networking_Guide/index.html"><em class="citetitle">Fedora Networking Guide</em></a>.
</div><div class="para">
If there is more configuration files present in the <code class="filename">/etc/vsftpd</code> directory, calling <code class="command">systemctl start vsftpd.service</code> results in the <code class="filename">/etc/rc.d/init.d/vsftpd</code> initscript starting the same number of processes as the number of configuration files. Each configuration file must have a unique name in the <code class="filename">/etc/vsftpd/</code> directory and must be readable and writable only by <code class="systemitem">root</code>.
</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s3-ftp-vsftpd-conf.html"><strong>Prev</strong>12.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>12.2.5. vsftpd Configuration Options</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-global_directives.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-global_directives.html
new file mode 100644
index 0000000..3289f5c
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-global_directives.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2.4. Global Directives</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-basic_configuration_of_rsyslog.html" title="17.2. Basic Configuration of Rsyslog" /><link rel="prev" href="s2-Templates.html" title="17.2.3. Templates" /><link rel="next" href="s2-log_rotation.html" title="17.2.5. Log Rotation" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-Templates.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="
n" href="s2-log_rotation.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-global_directives"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.4. Global Directives</h3></div></div></div><div class="para">
+ Global directives are configuration options that apply to the <code class="systemitem">rsyslogd</code> daemon. They usually specify a value for a specific predefined variable that affects the behavior of the <code class="systemitem">rsyslogd</code> daemon or a rule that follows. All of the global directives must start with a dollar sign (<code class="literal">$</code>). Only one directive can be specified per line. The following is an example of a global directive that specifies the maximum size of the syslog message queue:
+ </div><pre class="screen">
+$MainMsgQueueSize 50000
+</pre><div class="para">
+ The default size defined for this directive (<code class="constant">10,000</code> messages) can be overridden by specifying a different value (as shown in the example above).
+ </div><div class="para">
+ You may define multiple directives in your <code class="filename">/etc/rsyslog.conf</code> configuration file. A directive affects the behavior of all configuration options until another occurrence of that same directive is detected. Global directives can be used to configure actions, queues and for debugging. A comprehensive list of all available configuration directives can be found in <a class="xref" href="s1-log-files-additional-resources.html#brid-Log_Files-Resources-Online">the section called “Online Documentation”</a>. Currently, a new configuration format has been developed that replaces the $-based syntax (see <a class="xref" href="s2-using_the_new_configuration_format.html">Section 17.2.6, “Using the New Configuration Format”</a>). However, classic global directives remain supported as a legacy format.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-Templates.html"><strong>Prev</strong>17.2.3. Templates</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_rotation.html"><strong>Next</strong>17.2.5. Log Rotation</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-kernel-boot-loader-iseries.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-kernel-boot-loader-iseries.html
index a2e5468..dec3ce0 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-kernel-boot-loader-iseries.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-kernel-boot-loader-iseries.html
@@ -1,12 +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>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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.6.2. Configuring the OS/400 Boot Loader</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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>Pr
ev</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">20.6.2. Configuring the OS/400 Boot Loader</h3></div></div></div><a id="idm225458716528" class="indexterm"></a><a id="idm225468416608" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-kernel-boot-loader.html" title="21.6. Verifying the Boot Loader" /><link rel="prev" href="s1-kernel-boot-loader.html" title="21.6. Verifying the Boot Loader" /><link rel="next" href="s2-kernel-boot-loader-pseries.html" title="21.6.3. Configuring the YABOOT Boot Loader" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-boot-loader.html"><strong>Pr
ev</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">21.6.2. Configuring the OS/400 Boot Loader</h3></div></div></div><a id="idm261730191968" class="indexterm"></a><a id="idm261730190528" 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).
@@ -14,4 +14,4 @@
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>
\ No newline at end of file
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-boot-loader.html"><strong>Prev</strong>21.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>21.6.3. Configuring the YABOOT Boot Loader</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-kernel-boot-loader-pseries.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-kernel-boot-loader-pseries.html
index 7df2e3b..fa58c82 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-kernel-boot-loader-pseries.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-kernel-boot-loader-pseries.html
@@ -1,12 +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>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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>21.6.3. Configuring the YABOOT Boot Loader</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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-loade
r-iseries.html"><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">20.6.3. Configuring the YABOOT Boot Loader</h3></div></div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-kernel-boot-loader.html" title="21.6. Verifying the Boot Loader" /><link rel="prev" href="s2-kernel-boot-loader-iseries.html" title="21.6.2. Configuring the OS/400 Boot Loader" /><link rel="next" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kernel-boot-loade
r-iseries.html"><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">21.6.3. Configuring the YABOOT Boot Loader</h3></div></div></div><div class="para">
IBM eServer System p uses YABOOT as its boot loader. YABOOT uses <code class="filename">/etc/aboot.conf</code> as its configuration file. Confirm that the file contains an <code class="computeroutput">image</code> section with the same version as the <span class="package">kernel</span> package just installed, and likewise for the <code class="systemitem">initramfs</code> image:
</div><pre class="screen">boot=/dev/sda1 init-message=Welcome to Fedora! Hit <TAB> for boot options
partition=2 timeout=30 install=/usr/lib/yaboot/yaboot delay=10 nonvram
@@ -23,4 +23,4 @@ image=/vmlinuz-2.6.32-19.EL
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>
\ No newline at end of file
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-kernel-boot-loader-iseries.html"><strong>Prev</strong>21.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 22. Working with Kernel Modules</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-log_rotation.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-log_rotation.html
new file mode 100644
index 0000000..a3ef9d1
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-log_rotation.html
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2.5. Log Rotation</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-basic_configuration_of_rsyslog.html" title="17.2. Basic Configuration of Rsyslog" /><link rel="prev" href="s2-global_directives.html" title="17.2.4. Global Directives" /><link rel="next" href="s2-using_the_new_configuration_format.html" title="17.2.6. Using the New Configuration Format" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-global_directives
.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-using_the_new_configuration_format.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-log_rotation"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.5. Log Rotation</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 four weeks, and all rotated log files are compressed by <span class="application"><strong>gzip</strong></span> into the <code class="literal">.gz</code> format. Any lines that begin with a hash sign (#) are comments and are not processed.
+ </div><div class="para">
+ You may define configuration options for a specific log file and place it under the global options. However, it is advisable to create a separate configuration file for any specific log file in the <code class="filename">/etc/logrotate.d/</code> directory and define any configuration options there.
+ </div><div class="para">
+ The following is an example of a configuration file placed in the <code class="filename">/etc/logrotate.d/</code> directory:
+ </div><pre class="screen">
+/var/log/messages {
+ rotate 5
+ weekly
+ postrotate
+ /usr/bin/killall -HUP syslogd
+ endscript
+}
+</pre><div class="para">
+ The configuration options in this file are specific for the <code class="filename">/var/log/messages</code> log file only. The settings specified here override the global settings where possible. Thus the rotated <code class="filename">/var/log/messages</code> log file will be kept for five weeks instead of four weeks as was defined in the global options.
+ </div><div class="para">
+ The following is a list of some of the directives you can specify in your <span class="application"><strong>logrotate</strong></span> configuration file:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>weekly</code></em> — Specifies the rotation of log files to be done weekly. Similar directives include:
+ <div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <em class="parameter"><code>daily</code></em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>monthly</code></em>
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>yearly</code></em>
+ </div></li></ul></div>
+
+ </div></li><li class="listitem"><div class="para">
+ <em class="parameter"><code>compress</code></em> — 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 about-to-expire log files are to be mailed, instead of the just-rotated log files. This is the default option when <em class="parameter"><code>mail</code></em> is enabled.
+ </div></li></ul></div></li></ul></div><div class="para">
+ For the full list of directives and various configuration options, see the <code class="filename">logrotate(5)</code> manual page.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-global_directives.html"><strong>Prev</strong>17.2.4. Global Directives</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-using_the_new_configuration_format.html"><strong>Next</strong>17.2.6. Using the New Configuration Format</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-logfiles-adding.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-logfiles-adding.html
new file mode 100644
index 0000000..03bfd65
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-logfiles-adding.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.9.2. 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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-managing_log_files_in_a_graphical_environment.html" title="17.9. Managing Log Files in a Graphical Environment" /><link rel="prev" href="s1-managing_log_files_in_a_graphical_environment.html" title="17.9. Managing Log Files in a Graphical Environment" /><link rel="next" href="s2-logfiles-examining.html" title="17.9.3. 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-managing_log_files_in_a_graphical_environment.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-logfiles-examining.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-logfiles-adding"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.9.2. Adding a Log File</h3></div></div></div><div class="para">
+ To add a log file you want to view in the list, select <span class="guimenu"><strong>File</strong></span> → <span class="guimenuitem"><strong>Open</strong></span>. This will display the <span class="guilabel"><strong>Open Log</strong></span> window where you can select the directory and file name of the log file you want to view. <a class="xref" href="s2-logfiles-adding.html#fig-redhat-logviewer-add">Figure 17.6, “System Log - adding a log file”</a> illustrates the <span class="guimenu"><strong>Open Log</strong></span> window.
+ </div><div class="figure" id="fig-redhat-logviewer-add"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-add.png" width="444" alt="System Log - adding a log file" /><div class="longdesc"><div class="para">
+ System Log - Adding a Log File
+ </div></div></div></div><h6>Figure 17.6. System Log - adding a log file</h6></div><br class="figure-break" /><div class="para">
+ Click on the <span class="guibutton"><strong>Open</strong></span> button to open the file. The file is immediately added to the viewing list where you can select it and view its contents.
+ </div><div class="note"><div class="admonition_header"><h2>Reading zipped log files</h2></div><div class="admonition"><div class="para">
+ The <span class="application"><strong>System Log</strong></span> also allows you to open log files zipped in the <code class="literal">.gz</code> format.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-managing_log_files_in_a_graphical_environment.html"><strong>Prev</strong>17.9. Managing Log Files in a Graphical Environme...</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-logfiles-examining.html"><strong>Next</strong>17.9.3. Monitoring Log Files</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-logfiles-examining.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-logfiles-examining.html
new file mode 100644
index 0000000..6ea9f57
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-logfiles-examining.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.9.3. 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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-managing_log_files_in_a_graphical_environment.html" title="17.9. Managing Log Files in a Graphical Environment" /><link rel="prev" href="s2-logfiles-adding.html" title="17.9.2. Adding a Log File" /><link rel="next" href="s1-log-files-additional-resources.html" title="17.10. 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-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="s2-logfiles-examining"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.9.3. Monitoring Log Files</h3></div></div></div><a id="idm261727695984" class="indexterm"></a><a id="idm261727694544" class="indexterm"></a><div class="para">
+ <span class="application"><strong>System Log</strong></span> monitors all opened logs by default. If a new line is added to a monitored log file, the log name appears in bold in the log list. If the log file is selected or displayed, the new lines appear in bold at the bottom of the log file. <a class="xref" href="s2-logfiles-examining.html#fig-redhat-logviewer-monitoring">Figure 17.7, “System Log - new log alert”</a> illustrates a new alert in the <span class="guilabel"><strong>cron</strong></span> log file and in the <span class="guilabel"><strong>messages</strong></span> log file. Clicking on the <span class="guimenuitem"><strong>messages</strong></span> log file displays the logs in the file with the new lines in bold.
+ </div><div class="figure" id="fig-redhat-logviewer-monitoring"><div class="figure-contents"><div class="mediaobject"><img src="images/redhat-logviewer-monitoring.png" width="444" alt="System Log - new log alert" /><div class="longdesc"><div class="para">
+ System Log - New Log Alert
+ </div></div></div></div><h6>Figure 17.7. System Log - new log alert</h6></div><br class="figure-break" /></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-logfiles-adding.html"><strong>Prev</strong>17.9.2. 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.10. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-managing_queues.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-managing_queues.html
new file mode 100644
index 0000000..d6f1bbf
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-managing_queues.html
@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.3.2. Managing Queues</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-working_with_queues_in_rsyslog.html" title="17.3. Working with Queues in Rsyslog" /><link rel="prev" href="s1-working_with_queues_in_rsyslog.html" title="17.3. Working with Queues in Rsyslog" /><link rel="next" href="s1-using_rsyslog_modules.html" title="17.4. Using Rsyslog Modules" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-working_with_queues_i
n_rsyslog.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-using_rsyslog_modules.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-managing_queues"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.3.2. Managing Queues</h3></div></div></div><div class="para">
+ All types of queues can be further configured to match your requirements. You can use several directives to modify both action queues and the main message queue. Currently, there are more than 20 queue parameters available, see <a class="xref" href="s1-log-files-additional-resources.html#brid-Log_Files-Resources-Online">the section called “Online Documentation”</a>. Some of these settings are used commonly, others, such as worker thread management, provide closer control over the queue behavior and are reserved for advanced users. With advanced settings, you can optimize <span class="application"><strong>rsyslog</strong></span>'s performance, schedule queuing, or modify the behavior of queue on system shutdown.
+ </div><h4 id="br-limiting_queue_size">Limiting Queue Size</h4><div class="para">
+ You can limit the number of messages that queue can contain with the following setting:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueHighWatermark <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code> or with <code class="option">Action</code> to use this option to the main message queue or for an action queue respectively. Replace <em class="replaceable"><code>number</code></em> with a number of enqueued messages. You can set the queue size only as the number of messages, not as their actual memory size. The default queue size is 10,000 messages for the main message queue and ruleset queues, and 1000 for action queues.
+ </div><div class="para">
+ Disk assisted queues are unlimited by default and can not be restricted with this directive, but you can reserve them physical disk space in bytes with the following settings:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueMaxDiscSpace <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code> or with <code class="option">Action</code>. When the size limit specified by <em class="replaceable"><code>number</code></em> is hit, messages are discarded until sufficient amount of space is freed by dequeued messages.
+ </div><h4 id="br-discarding_messages">Discarding Messages</h4><div class="para">
+ When a queue reaches a certain number of messages, you can discard less important messages in order to save space in the queue for entries of higher priority. The threshold that launches the discarding process can be set with the so-called <span class="emphasis"><em>discard mark</em></span>:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueDiscardMark <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>object</code></em> with <code class="option">MainMsg</code> or with <code class="option">Action</code> to use this option to the main message queue or for an action queue respectively. Here, <em class="replaceable"><code>number</code></em> stands for a number of messages that have to be in the queue to start the discarding process. To define which messages to discard, use:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueDiscardSeverity <em class="replaceable"><code>priority</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>priority</code></em> with one of the following keywords (or with a number): <code class="command">debug</code> (7), <code class="command">info</code> (6), <code class="command">notice</code> (5), <code class="command">warning</code> (4), <code class="command">err</code> (3), <code class="command">crit</code> (2), <code class="command">alert</code> (1), and <code class="command">emerg</code> (0). With this setting, both newly incoming and already queued messages with lower than defined priority are erased from the queue immediately after the discard mark is reached.
+ </div><h4 id="br-using_timeframes">Using Timeframes</h4><div class="para">
+ You can configure <span class="application"><strong>rsyslog</strong></span> to process queues during a specific time period. With this option you can, for example, transfer some processing into off-peak hours. To define a time frame, use the following syntax:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueDequeueTimeBegin <em class="replaceable"><code>hour</code></em></pre><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueDequeueTimeEnd <em class="replaceable"><code>hour</code></em></pre><div class="para">
+ With <em class="replaceable"><code>hour</code></em> you can specify hours that bound your time frame. Use the 24-hour format without minutes.
+ </div><h4 id="br-configuring_worker_threads">Configuring Worker Threads</h4><div class="para">
+ A <em class="firstterm">worker thread</em> performs a specified action on the enqueued message. For example, in the main message queue, a worker task is to apply filter logic to each incoming message and enqueue them to the relevant action queues. When a message arrives, a worker thread is started automatically. When the number of messages reaches a certain number, another worker thread is turned on. To specify this number, use:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueWorkerThreadMinimumMessages <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>number</code></em> with a number of messages that will trigger a supplemental worker thread. For example, with <em class="replaceable"><code>number</code></em> set to 100, a new worker thread is started when more than 100 messages arrive. When more than 200 messages arrive, the third worker thread starts and so on. However, too many working threads running in parallel becomes ineffective, so you can limit the maximum number of them by using:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueWorkerThreads <em class="replaceable"><code>number</code></em></pre><div class="para">
+ where <em class="replaceable"><code>number</code></em> stands for a maximum number of working threads that can run in parallel. For the main message queue, the default limit is 1 thread. Once a working thread has been started, it keeps running until an inactivity timeout appears. To set the length of timeout, type:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueWorkerTimeoutThreadShutdown <em class="replaceable"><code>time</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>time</code></em> with the duration set in milliseconds. Without this setting, a zero timeout is applied and a worker thread is terminated immediately when it runs out of messages. If you specify <em class="replaceable"><code>time</code></em> as <code class="literal">-1</code>, no thread will be closed.
+ </div><h4 id="br-batch_dequeuing">Batch Dequeuing</h4><div class="para">
+ To increase performance, you can configure <span class="application"><strong>rsyslog</strong></span> to dequeue multiple messages at once. To set the upper limit for such dequeueing, use:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueDequeueBatchSize <em class="replaceable"><code>number</code></em></pre><div class="para">
+ Replace <em class="replaceable"><code>number</code></em> with the maximum number of messages that can be dequeued at once. Note that a higher setting combined with a higher number of permitted working threads results in greater memory consumption.
+ </div><h4 id="br-terminating_queues">Terminating Queues</h4><div class="para">
+ When terminating a queue that still contains messages, you can try to minimize the data loss by specifying a time interval for worker threads to finish the queue processing:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueTimeoutShutdown <em class="replaceable"><code>time</code></em></pre><div class="para">
+ Specify <em class="replaceable"><code>time</code></em> in milliseconds. If after that period there are still some enqueued messages, workers finish the current data element and then terminate. Unprocessed messages are therefore lost. Another time interval can be set for workers to finish the final element:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueTimeoutActionCompletion <em class="replaceable"><code>time</code></em></pre><div class="para">
+ In case this timeout expires, any remaining workers are shut down. To save data at shutdown, use:
+ </div><pre class="synopsis">$<em class="replaceable"><code>object</code></em>QueueTimeoutSaveOnShutdown <em class="replaceable"><code>time</code></em></pre><div class="para">
+ If set, all queue elements are saved to disk before <span class="application"><strong>rsyslog</strong></span> terminates.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-working_with_queues_in_rsyslog.html"><strong>Prev</strong>17.3. Working with Queues in Rsyslog</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-using_rsyslog_modules.html"><strong>Next</strong>17.4. Using Rsyslog Modules</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-operf-categorization.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-operf-categorization.html
new file mode 100644
index 0000000..bc33614
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-operf-categorization.html
@@ -0,0 +1,13 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.3. Categorization of Samples</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-using-operf.html" title="19.2. Using operf" /><link rel="prev" href="s2-operf-events.html" title="19.2.2. Setting Events to Monitor" /><link rel="next" href="s1-oprofile-configuring.html" title="19.3. Configuring OProfile Using Legacy Mode" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-operf-events.html"><strong>Prev</strong></a></li><li class="next
"><a accesskey="n" href="s1-oprofile-configuring.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-operf-categorization"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.3. Categorization of Samples</h3></div></div></div><div class="para">
+ The <code class="option">--separate-thread</code> option categorizes samples by thread group ID (tgid) and thread ID (tid). This is useful for seeing per-thread samples in multi-threaded applications. When used in conjunction with the <code class="option">--system-wide</code> option, <code class="option">--separate-thread</code> is also useful for seeing per-process (i.e., per-thread group) samples for the case where multiple processes are executing the same program during a profiling run.
+ </div><div class="para">
+ The <code class="option">--separate-cpu</code> option categorizes samples by CPU.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-operf-events.html"><strong>Prev</strong>19.2.2. Setting Events to Monitor</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-oprofile-configuring.html"><strong>Next</strong>19.3. Configuring OProfile Using Legacy Mode</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-operf-events.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-operf-events.html
new file mode 100644
index 0000000..093290b
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-operf-events.html
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.2. Setting Events to Monitor</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-using-operf.html" title="19.2. Using operf" /><link rel="prev" href="s1-using-operf.html" title="19.2. Using operf" /><link rel="next" href="s2-operf-categorization.html" title="19.2.3. Categorization of Samples" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-using-operf.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-o
perf-categorization.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-operf-events"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.2. Setting Events to Monitor</h3></div></div></div><div class="para">
+ Most processors contain counters, which are used by OProfile to monitor specific events. As shown in <a class="xref" href="s2-oprofile-events.html#tb-oprofile-processors">Table 19.3, “OProfile Processors and Counters”</a>, the number of counters available depends on the processor.
+ </div><div class="para">
+ The events for each counter can be configured via the command line or with a graphical interface. For more information on the graphical interface, see <a class="xref" href="s1-oprofile-gui.html">Section 19.10, “Graphical Interface”</a>. If the counter cannot be set to a specific event, an error message is displayed.
+ </div><div class="note"><div class="admonition_header"><h2>Older Processors and operf</h2></div><div class="admonition"><div class="para">
+ Some older processor models are not supported by the underlying Linux Performance Events Subsystem kernel and therefore are not supported by <code class="command">operf</code>. If you receive this message:
+<pre class="screen">
+Your kernel's Performance Events Subsystem does not support your processor type
+</pre>
+ when attempting to use <code class="command">operf</code>, try profiling with <code class="command">opcontrol</code> to see if your processor type may be supported by OProfile's legacy mode.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Using operf on Virtual Systems</h2></div><div class="admonition"><div class="para">
+ Since hardware performance counters are not available on guest virtual machines, you have to enable <span class="emphasis"><em>timer</em></span> mode to use <span class="application"><strong>operf</strong></span> on virtual systems. To do so, type as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code class="command">opcontrol</code> <code class="option">--deinit</code></pre><pre class="synopsis"><code class="command">modprobe</code> <code class="command">oprofile</code> <code class="option">timer=1</code></pre></div></div><div class="para">
+ To set the event for each configurable counter via the command line, use:
+ </div><pre class="synopsis"><code class="command">operf</code> <code class="option">--events</code>=<em class="replaceable"><code>event1</code></em>,<em class="replaceable"><code>event2</code></em>…</pre><div class="para">
+ Here, pass a comma-separated list of event specifications for profiling. Each event specification is a colon-separated list of attributes in the following form:
+ </div><pre class="synopsis"><em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em>:<em class="replaceable"><code>kernel</code></em>:<em class="replaceable"><code>user</code></em></pre><div class="para">
+ <a class="xref" href="s2-operf-events.html#tab_event_specifications">Table 19.2, “Event Specifications”</a> summarizes these options. The last three values are optional, if you omit them, they will be set to their default values. Note that certain events do require a unit mask.
+ </div><div class="table" id="tab_event_specifications"><h6>Table 19.2. Event Specifications</h6><div class="table-contents"><table summary="Event Specifications" border="1"><colgroup><col width="50%" /><col width="50%" /></colgroup><thead><tr><th class="" align="left">
+ Specification
+ </th><th class="" align="left">
+ Description
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ <em class="replaceable"><code>event-name</code></em>
+ </td><td class="" align="left">
+ The exact symbolic event name taken from <code class="command">ophelp</code>
+ </td></tr><tr><td class="" align="left">
+ <em class="replaceable"><code>sample-rate</code></em>
+ </td><td class="" align="left">
+ The number of events to wait before sampling again. The smaller the count, the more frequent the samples. For events that do not happen frequently, a lower count may be needed to capture a statistically significant number of event instances. On the other hand, sampling too frequently can overload the system. By default, OProfile uses a time-based event set, which creates a sample every 100,000 clock cycles per processor.
+ </td></tr><tr><td class="" align="left">
+ <em class="replaceable"><code>unit-mask</code></em>
+ </td><td class="" align="left">
+ Unit masks, which further define the event, are listed in <code class="command">ophelp</code>. You can insert either a hexadecimal value, beginning with "0x", or a string that matches the first word of the unit mask description in <code class="command">ophelp</code>. Definition by name is valid only for unit masks having "extra:" parameters, as shown by the output of <code class="command">ophelp</code>. This type of unit mask cannot be defined with a hexadecimal value. Note that on certain architectures, there can be multiple unit masks with the same hexadecimal value. In that case they have to be specified by their names only.
+ </td></tr><tr><td class="" align="left">
+ <em class="replaceable"><code>kernel</code></em>
+ </td><td class="" align="left">
+ Specifies whether to profile kernel code (insert <code class="literal">0</code> or <code class="literal">1</code>(default))
+ </td></tr><tr><td class="" align="left">
+ <em class="replaceable"><code>user</code></em>
+ </td><td class="" align="left">
+ Specifies whether to profile user-space code (insert <code class="literal">0</code> or <code class="literal">1</code> (default))
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The events available vary depending on the processor type. When no event specification is given, the default event for the running processor type will be used for profiling. See <a class="xref" href="s2-oprofile-events.html#tb-oprofile-default-events">Table 19.4, “Default Events”</a> for a list of these default events. To determine the events available for profiling, use the <code class="command">ophelp</code> command.
+ </div><pre class="synopsis"><code class="command">ophelp</code></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-using-operf.html"><strong>Prev</strong>19.2. Using operf</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-operf-categorization.html"><strong>Next</strong>19.2.3. Categorization of Samples</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-events.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-events.html
index d0bb5c7..746351b 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-events.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-events.html
@@ -1,14 +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.2.2. Setting Events to Monitor</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Setting Events to Monitor</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-oprofile-configuring.html" title="19.2. Configuring OProfile" /><link rel="prev" href="s1-oprofile-configuring.html" title="19.2. Configuring OProfile" /><link rel="next" href="s2-oprofile-starting-separate.html" title="19.2.3. Separating Kernel and User-space Profiles" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-configuring.html"><strong
>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-oprofile-starting-separate.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-oprofile-events"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.2. Setting Events to Monitor</h3></div></div></div><a id="idm225463433344" class="indexterm"></a><div class="para">
- Most processors contain <em class="firstterm">counters</em>, which are used by OProfile to monitor specific events. As shown in <a class="xref" href="s2-oprofile-events.html#tb-oprofile-processors">Table 19.2, “OProfile Processors and Counters”</a>, the number of counters available depends on the processor.
- </div><div class="table" id="tb-oprofile-processors"><h6>Table 19.2. OProfile Processors and Counters</h6><div class="table-contents"><table summary="OProfile Processors and Counters" border="1"><colgroup><col width="43%" class="option" /><col width="29%" class="description" /><col width="29%" class="description" /></colgroup><thead><tr><th class="">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-oprofile-configuring.html" title="19.3. Configuring OProfile Using Legacy Mode" /><link rel="prev" href="s1-oprofile-configuring.html" title="19.3. Configuring OProfile Using Legacy Mode" /><link rel="next" href="s2-oprofile-starting-separate.html" title="19.3.3. Separating Kernel and User-space Profiles" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s
1-oprofile-configuring.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-oprofile-starting-separate.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-oprofile-events"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.3.2. Setting Events to Monitor</h3></div></div></div><a id="idm261758429296" class="indexterm"></a><div class="para">
+ Most processors contain <em class="firstterm">counters</em>, which are used by OProfile to monitor specific events. As shown in <a class="xref" href="s2-oprofile-events.html#tb-oprofile-processors">Table 19.3, “OProfile Processors and Counters”</a>, the number of counters available depends on the processor.
+ </div><div class="table" id="tb-oprofile-processors"><h6>Table 19.3. OProfile Processors and Counters</h6><div class="table-contents"><table summary="OProfile Processors and Counters" border="1"><colgroup><col width="43%" class="option" /><col width="29%" class="description" /><col width="29%" class="description" /></colgroup><thead><tr><th class="">
Processor
</th><th class="">
<code class="command">cpu_type</code>
@@ -21,12 +21,6 @@
</td><td class="">
4
</td></tr><tr><td class="">
- AMD Athlon
- </td><td class="">
- i386/athlon
- </td><td class="">
- 4
- </td></tr><tr><td class="">
AMD Family 10h
</td><td class="">
x86-64/family10
@@ -57,6 +51,24 @@
</td><td class="">
6
</td></tr><tr><td class="">
+ Applied Micro X-Gene
+ </td><td class="">
+ arm/armv8-xgene
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ ARM Cortex A53
+ </td><td class="">
+ arm/armv8-ca53
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ ARM Cortex A57
+ </td><td class="">
+ arm/armv8-ca57
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
IBM eServer System i and IBM eServer System p
</td><td class="">
timer
@@ -81,6 +93,42 @@
</td><td class="">
8
</td></tr><tr><td class="">
+ IBM PowerPC 970MP
+ </td><td class="">
+ ppc64/970MP
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ IBM POWER5+
+ </td><td class="">
+ ppc64/power5+
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER5++
+ </td><td class="">
+ ppc64/power5++
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER56
+ </td><td class="">
+ ppc64/power6
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER7
+ </td><td class="">
+ ppc64/power7
+ </td><td class="">
+ 6
+ </td></tr><tr><td class="">
+ IBM POWER8
+ </td><td class="">
+ ppc64/power7
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
IBM S/390 and IBM System z
</td><td class="">
timer
@@ -99,36 +147,78 @@
</td><td class="">
4
</td></tr><tr><td class="">
- Intel Pentium 4 (non-hyper-threaded)
+ Intel Westmere microarchitecture
+ </td><td class="">
+ i386/westmere
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Haswell microarchitecture (non-hyper-threaded)
</td><td class="">
- i386/p4
+ i386/haswell
</td><td class="">
8
</td></tr><tr><td class="">
- Intel Pentium 4 (hyper-threaded)
+ Intel Haswell microarchitecture (hyper-threaded)
</td><td class="">
- i386/p4-ht
+ i386/haswell-ht
</td><td class="">
4
</td></tr><tr><td class="">
- Intel Westmere microarchitecture
+ Intel Ivy Bridge microarchitecture (non-hyper-threaded)
</td><td class="">
- i386/westmere
+ i386/ivybridge
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Ivy Bridge microarchitecture (hyper-threaded)
+ </td><td class="">
+ i386/ivybridge-ht
</td><td class="">
4
</td></tr><tr><td class="">
+ Intel Sandy Bridge microarchitecture (non-hyper-threaded)
+ </td><td class="">
+ i386/sandybridge
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Sandy Bridge microarchitecture
+ </td><td class="">
+ i386/sandybridge-ht
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Broadwell microarchitecture (non-hyper-threaded)
+ </td><td class="">
+ i386/broadwell
+ </td><td class="">
+ 8
+ </td></tr><tr><td class="">
+ Intel Broadwell microarchitecture (hyper-threaded)
+ </td><td class="">
+ i386/broadwell-ht
+ </td><td class="">
+ 4
+ </td></tr><tr><td class="">
+ Intel Silvermont microarchitecture
+ </td><td class="">
+ i386/silvermont
+ </td><td class="">
+ 2
+ </td></tr><tr><td class="">
TIMER_INT
</td><td class="">
timer
</td><td class="">
1
</td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
- Use <a class="xref" href="s2-oprofile-events.html#tb-oprofile-processors">Table 19.2, “OProfile Processors and Counters”</a> to verify that the correct processor type was detected and to determine the number of events that can be monitored simultaneously. <code class="computeroutput">timer</code> is used as the processor type if the processor does not have supported performance monitoring hardware.
+ Use <a class="xref" href="s2-oprofile-events.html#tb-oprofile-processors">Table 19.3, “OProfile Processors and Counters”</a> to determine the number of events that can be monitored simultaneously for your CPU type. If the processor does not have supported performance monitoring hardware, the <code class="computeroutput">timer</code> is used as the processor type.
</div><div class="para">
If <code class="computeroutput">timer</code> is used, events cannot be set for any processor because the hardware does not have support for hardware performance counters. Instead, the timer interrupt is used for profiling.
</div><div class="para">
- If <code class="computeroutput">timer</code> is not used as the processor type, the events monitored can be changed, and counter 0 for the processor is set to a time-based event by default. If more than one counter exists on the processor, the counters other than counter 0 are not set to an event by default. The default events monitored are shown in <a class="xref" href="s2-oprofile-events.html#tb-oprofile-default-events">Table 19.3, “Default Events”</a>.
- </div><div class="table" id="tb-oprofile-default-events"><h6>Table 19.3. Default Events</h6><div class="table-contents"><table summary="Default Events" border="1"><colgroup><col width="25%" class="option" /><col width="33%" class="description" /><col width="42%" class="description" /></colgroup><thead><tr><th class="">
+ If <code class="computeroutput">timer</code> is not used as the processor type, the events monitored can be changed, and counter 0 for the processor is set to a time-based event by default. If more than one counter exists on the processor, the counters other than 0 are not set to an event by default. The default events monitored are shown in <a class="xref" href="s2-oprofile-events.html#tb-oprofile-default-events">Table 19.4, “Default Events”</a>.
+ </div><div class="table" id="tb-oprofile-default-events"><h6>Table 19.4. Default Events</h6><div class="table-contents"><table summary="Default Events" border="1"><colgroup><col width="25%" class="option" /><col width="33%" class="description" /><col width="42%" class="description" /></colgroup><thead><tr><th class="">
Processor
</th><th class="">
Default Event for Counter
@@ -153,6 +243,24 @@
</td><td class="">
The processor's clock is not halted
</td></tr><tr><td class="">
+ Applied Micro X-Gene
+ </td><td class="">
+ CPU_CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ ARM Cortex A53
+ </td><td class="">
+ CPU_CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
+ ARM Cortex A57
+ </td><td class="">
+ CPU_CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
IBM POWER4
</td><td class="">
CYCLES
@@ -165,6 +273,12 @@
</td><td class="">
Processor Cycles
</td></tr><tr><td class="">
+ IBM POWER8
+ </td><td class="">
+ CYCLES
+ </td><td class="">
+ Processor Cycles
+ </td></tr><tr><td class="">
IBM PowerPC 970
</td><td class="">
CYCLES
@@ -195,6 +309,18 @@
</td><td class="">
The processor's clock is not halted
</td></tr><tr><td class="">
+ Intel Broadwell microarchitecture
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
+ Intel Silvermont microarchitecture
+ </td><td class="">
+ CPU_CLK_UNHALTED
+ </td><td class="">
+ The processor's clock is not halted
+ </td></tr><tr><td class="">
TIMER_INT
</td><td class="">
(none)
@@ -204,22 +330,31 @@
The number of events that can be monitored at one time is determined by the number of counters for the processor. However, it is not a one-to-one correlation; on some processors, certain events must be mapped to specific counters. To determine the number of counters available, execute the following command:
</div><pre class="screen">~]# <code class="command">ls -d /dev/oprofile/[0-9]*</code></pre><div class="para">
The events available vary depending on the processor type. To determine the events available for profiling, execute the following command as root (the list is specific to the system's processor type):
- </div><a id="idm225464869952" class="indexterm"></a><a id="idm225464867840" class="indexterm"></a><pre class="screen">~]# <code class="command">ophelp</code></pre><div class="para">
- The events for each counter can be configured via the command line or with a graphical interface. For more information on the graphical interface, refer to <a class="xref" href="s1-oprofile-gui.html">Section 19.9, “Graphical Interface”</a>. If the counter cannot be set to a specific event, an error message is displayed.
+ </div><a id="idm261714717104" class="indexterm"></a><a id="idm261714715184" class="indexterm"></a><pre class="screen">~]# <code class="command">ophelp</code></pre><div class="note"><div class="admonition_header"><h2>Make sure that OProfile is configured</h2></div><div class="admonition"><div class="para">
+ Unless OProfile is properly configured, <code class="command">ophelp</code> fails with the following error message:
+ </div><pre class="screen">Unable to open cpu_type file for reading
+Make sure you have done opcontrol --init
+cpu_type 'unset' is not valid
+you should upgrade oprofile or force the use of timer mode</pre><div class="para">
+ To configure OProfile, follow the instructions in <a class="xref" href="s1-oprofile-configuring.html">Section 19.3, “Configuring OProfile Using Legacy Mode”</a>.
+ </div></div></div><div class="para">
+ The events for each counter can be configured via the command line or with a graphical interface. For more information on the graphical interface, see <a class="xref" href="s1-oprofile-gui.html">Section 19.10, “Graphical Interface”</a>. If the counter cannot be set to a specific event, an error message is displayed.
</div><div class="para">
To set the event for each configurable counter via the command line, use <code class="command">opcontrol</code>:
</div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em></code></pre><div class="para">
Replace <em class="replaceable"><code>event-name</code></em> with the exact name of the event from <code class="command">ophelp</code>, and replace <em class="replaceable"><code>sample-rate</code></em> with the number of events between samples.
- </div><div class="section" id="s3-oprofile-events-sampling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">19.2.2.1. Sampling Rate</h4></div></div></div><a id="idm225459323984" class="indexterm"></a><div class="para">
- By default, a time-based event set is selected. It creates a sample every 100,000 clock cycles per processor. If the timer interrupt is used, the timer is set to whatever the jiffy rate is and is not user-settable. If the <code class="computeroutput">cpu_type</code> is not <code class="computeroutput">timer</code>, each event can have a <em class="firstterm">sampling rate</em> set for it. The sampling rate is the number of events between each sample snapshot.
+ </div><div class="section" id="s3-oprofile-events-sampling"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">19.3.2.1. Sampling Rate</h4></div></div></div><a id="idm261747206976" class="indexterm"></a><div class="para">
+ By default, a time-based event set is selected. It creates a sample every 100,000 clock cycles per processor. If the timer interrupt is used, the timer is set to the respective rate and is not user-settable. If the <code class="computeroutput">cpu_type</code> is not <code class="computeroutput">timer</code>, each event can have a <em class="firstterm">sampling rate</em> set for it. The sampling rate is the number of events between each sample snapshot.
</div><div class="para">
When setting the event for the counter, a sample rate can also be specified:
</div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em></code></pre><div class="para">
Replace <em class="replaceable"><code>sample-rate</code></em> with the number of events to wait before sampling again. The smaller the count, the more frequent the samples. For events that do not happen frequently, a lower count may be needed to capture the event instances.
</div><div class="warning"><div class="admonition_header"><h2>Sampling too frequently can overload the system</h2></div><div class="admonition"><div class="para">
- Be extremely careful when setting sampling rates. Sampling too frequently can overload the system, causing the system to appear as if it is frozen or causing the system to actually freeze.
- </div></div></div></div><div class="section" id="s3-oprofile-events-unit-masks"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">19.2.2.2. Unit Masks</h4></div></div></div><a id="idm225461653600" class="indexterm"></a><div class="para">
+ Be extremely careful when setting sampling rates. Sampling too frequently can overload the system, causing the system to appear frozen or causing the system to actually freeze.
+ </div></div></div></div><div class="section" id="s3-oprofile-events-unit-masks"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">19.3.2.2. Unit Masks</h4></div></div></div><a id="idm261741772272" class="indexterm"></a><div class="para">
Some user performance monitoring events may also require unit masks to further define the event.
</div><div class="para">
Unit masks for each event are listed with the <code class="command">ophelp</code> command. The values for each unit mask are listed in hexadecimal format. To specify more than one unit mask, the hexadecimal values must be combined using a bitwise <em class="firstterm">or</em> operation.
- </div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em></code></pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-configuring.html"><strong>Prev</strong>19.2. Configuring OProfile</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-oprofile-starting-separate.html"><strong>Next</strong>19.2.3. Separating Kernel and User-space Profiles</a></li></ul></body></html>
\ No newline at end of file
+ </div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em></code></pre><div class="para">
+ Note that on certain architectures, there can be multiple unit masks with the same hexadecimal value. In that case they have to be specified by their names only.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-configuring.html"><strong>Prev</strong>19.3. Configuring OProfile Using Legacy Mode</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-oprofile-starting-separate.html"><strong>Next</strong>19.3.3. Separating Kernel and User-space Profiles</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-module-output.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-module-output.html
index ec7ddb4..5305484 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-module-output.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-module-output.html
@@ -1,13 +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>19.5.3. Getting more detailed output on the modules</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.3. Getting More Detailed Output on the Modules</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-oprofile-analyzing-data.html" title="19.5. Analyzing the Data" /><link rel="prev" href="s2-oprofile-reading-opreport-single.html" title="19.5.2. Using opreport on a Single Executable" /><link rel="next" href="s2-oprofile-reading-opannotate.html" title="19.5.4. Using opannotate" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-reading-opreport-
single.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-oprofile-reading-opannotate.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-oprofile-module-output"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.5.3. Getting more detailed output on the modules</h3></div></div></div><a id="idm225442107120" class="indexterm"></a><a id="idm225442104896" class="indexterm"></a><div class="para">
- OProfile collects data on a system-wide basis for kernel- and user-space code running on the machine. However, once a module is loaded into the kernel, the information about the origin of the kernel module is lost. The module could have come from the <code class="filename">initrd</code> file on boot up, the directory with the various kernel modules, or a locally created kernel module. As a result, when OProfile records sample for a module, it just lists the samples for the modules for an executable in the root directory, but this is unlikely to be the place with the actual code for the module. You will need to take some steps to make sure that analysis tools get the executable.
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-oprofile-analyzing-data.html" title="19.6. Analyzing the Data" /><link rel="prev" href="s2-oprofile-reading-opreport-single.html" title="19.6.2. Using opreport on a Single Executable" /><link rel="next" href="s2-oprofile-reading-opannotate.html" title="19.6.4. Using opannotate" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-reading-opreport-
single.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-oprofile-reading-opannotate.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-oprofile-module-output"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.6.3. Getting More Detailed Output on the Modules</h3></div></div></div><a id="idm261752496576" class="indexterm"></a><a id="idm261752494656" class="indexterm"></a><div class="para">
+ OProfile collects data on a system-wide basis for kernel- and user-space code running on the machine. However, once a module is loaded into the kernel, the information about the origin of the kernel module is lost. The module could come from the <code class="filename">initrd</code> file on boot up, the directory with the various kernel modules, or a locally created kernel module. As a result, when OProfile records samples for a module, it just lists the samples for the modules for an executable in the root directory, but this is unlikely to be the place with the actual code for the module. You will need to take some steps to make sure that analysis tools get the proper executable.
</div><div class="para">
To get a more detailed view of the actions of the module, you will need to either have the module "unstripped" (that is installed from a custom build) or have the <span class="package">debuginfo</span> package installed for the kernel.
</div><div class="para">
@@ -34,4 +34,4 @@ samples % symbol name
583 3.5361 ext4_xattr_get
479 2.9053 ext4_htree_store_dirent
469 2.8447 ext4_get_group_desc
-414 2.5111 ext4_dx_find_entry</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-reading-opreport-single.html"><strong>Prev</strong>19.5.2. Using opreport on a Single Executable</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-oprofile-reading-opannotate.html"><strong>Next</strong>19.5.4. Using opannotate </a></li></ul></body></html>
\ No newline at end of file
+414 2.5111 ext4_dx_find_entry</pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-reading-opreport-single.html"><strong>Prev</strong>19.6.2. Using opreport on a Single Executable</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-oprofile-reading-opannotate.html"><strong>Next</strong>19.6.4. Using opannotate</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-reading-opannotate.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-reading-opannotate.html
index 61fd4b1..2111572 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-reading-opannotate.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-reading-opannotate.html
@@ -1,17 +1,17 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.5.4. Using opannotate</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.4. Using opannotate</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-oprofile-analyzing-data.html" title="19.5. Analyzing the Data" /><link rel="prev" href="s2-oprofile-module-output.html" title="19.5.3. Getting more detailed output on the modules" /><link rel="next" href="s1-oprofile-dev-oprofile.html" title="19.6. Understanding /dev/oprofile/" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-module-output.htm
l"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-oprofile-dev-oprofile.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-oprofile-reading-opannotate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.5.4. Using <code class="command">opannotate</code> </h3></div></div></div><a id="idm225452601408" class="indexterm"></a><a id="idm225452599184" class="indexterm"></a><div class="para">
- The <code class="command">opannotate</code> tool tries to match the samples for particular instructions to the corresponding lines in the source code. The resulting files generated should have the samples for the lines at the left. It also puts in a comment at the beginning of each function listing the total samples for the function.
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-oprofile-analyzing-data.html" title="19.6. Analyzing the Data" /><link rel="prev" href="s2-oprofile-module-output.html" title="19.6.3. Getting More Detailed Output on the Modules" /><link rel="next" href="s1-oprofile-dev-oprofile.html" title="19.7. Understanding the /dev/oprofile/ directory" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-mod
ule-output.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-oprofile-dev-oprofile.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-oprofile-reading-opannotate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.6.4. Using <code class="command">opannotate</code></h3></div></div></div><a id="idm261784214096" class="indexterm"></a><a id="idm261784212176" class="indexterm"></a><div class="para">
+ The <code class="command">opannotate</code> tool tries to match the samples for particular instructions to the corresponding lines in the source code. The resulting generated files should have the samples for the lines at the left. It also puts in a comment at the beginning of each function listing the total samples for the function.
</div><div class="para">
- For this utility to work, the appropriate <span class="package">debuginfo</span> package for the executable must be installed on the system. By default, Fedora <span class="package">debuginfo</span> packages are not installed together with their corresponding packages, which contain the executable, so that you have to obtain and install the <span class="package">debuginfo</span> packages separately.
+ For this utility to work, the appropriate <span class="package">debuginfo</span> package for the executable must be installed on the system. On Fedora, the <span class="package">debuginfo</span> packages are not automatically installed with the corresponding packages that contain the executable. You have to obtain and install them separately.
</div><div class="para">
The general syntax for <code class="command">opannotate</code> is as follows:
</div><pre class="screen">~]# <code class="command">opannotate --search-dirs <em class="replaceable"><code>src-dir</code></em> --source <em class="replaceable"><code>executable</code></em></code></pre><div class="para">
- The directory containing the source code and the executable to be analyzed must be specified. See the <code class="command">opannotate</code> man page for a list of additional command line options.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-module-output.html"><strong>Prev</strong>19.5.3. Getting more detailed output on the modul...</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-oprofile-dev-oprofile.html"><strong>Next</strong>19.6. Understanding /dev/oprofile/ </a></li></ul></body></html>
\ No newline at end of file
+ These command-line options are mandatory. Replace <em class="replaceable"><code>src-dir</code></em> with a path to the directory containing the source code and specify the executable to be analyzed. See the <code class="systemitem">opannotate(1)</code> manual page for a list of additional command line options.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-module-output.html"><strong>Prev</strong>19.6.3. Getting More Detailed Output on the Modul...</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-oprofile-dev-oprofile.html"><strong>Next</strong>19.7. Understanding the /dev/oprofile/ directory </a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-reading-opreport-single.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-reading-opreport-single.html
index 1892333..79911c0 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-reading-opreport-single.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-reading-opreport-single.html
@@ -1,17 +1,19 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.5.2. Using opreport on a Single Executable</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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.2. Using opreport on a Single Executable</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-oprofile-analyzing-data.html" title="19.5. Analyzing the Data" /><link rel="prev" href="s1-oprofile-analyzing-data.html" title="19.5. Analyzing the Data" /><link rel="next" href="s2-oprofile-module-output.html" title="19.5.3. Getting more detailed output on the modules" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-analyzing-data.html"><str
ong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-oprofile-module-output.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-oprofile-reading-opreport-single"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.5.2. Using opreport on a Single Executable</h3></div></div></div><a id="idm225474925664" class="indexterm"></a><a id="idm225474922960" class="indexterm"></a><div class="para">
- To retrieve more detailed profiled information about a specific executable, use <code class="command">opreport</code>:
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-oprofile-analyzing-data.html" title="19.6. Analyzing the Data" /><link rel="prev" href="s1-oprofile-analyzing-data.html" title="19.6. Analyzing the Data" /><link rel="next" href="s2-oprofile-module-output.html" title="19.6.3. Getting More Detailed Output on the Modules" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-analyzing-data.html"><str
ong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-oprofile-module-output.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-oprofile-reading-opreport-single"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.6.2. Using opreport on a Single Executable</h3></div></div></div><a id="idm261744164544" class="indexterm"></a><a id="idm261744162144" class="indexterm"></a><div class="para">
+ To retrieve more detailed profiled information about a specific executable, use the <code class="command">opreport</code> command:
</div><pre class="screen">~]# <code class="command">opreport <em class="replaceable"><code>mode</code></em> <em class="replaceable"><code>executable</code></em></code></pre><div class="para">
- <em class="replaceable"><code>executable</code></em> must be the full path to the executable to be analyzed. <em class="replaceable"><code>mode</code></em> must be one of the following:
+ Replace <em class="replaceable"><code>executable</code></em> with the full path to the executable to be analyzed. <em class="replaceable"><code>mode</code></em> stands for one of the following options:
</div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <code class="option">-l</code> </span></dt><dd><div class="para">
- List sample data by symbols. For example, the following is part of the output from running the command <code class="command">opreport -l /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code>:
+ This option is used to list sample data by symbols. For example, running this command: <pre class="synopsis">~]# <code class="command">opreport -l /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code></pre>
+ </div><div class="para">
+ produces the following output:
</div><pre class="screen">samples % symbol name
12 21.4286 __gconv_transform_utf8_internal
5 8.9286 _int_malloc 4 7.1429 malloc
@@ -42,14 +44,18 @@
</div><div class="para">
To sort the output from the largest number of samples to the smallest (reverse order), use <code class="option">-r</code> in conjunction with the <code class="option">-l</code> option.
</div></dd><dt class="varlistentry"><span class="term"> <code class="option">-i <em class="replaceable"><code>symbol-name</code></em> </code> </span></dt><dd><div class="para">
- List sample data specific to a symbol name. For example, the following output is from the command <code class="command">opreport -l -i __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code>:
+ List sample data specific to a symbol name. For example, running: <pre class="synopsis">~]# <code class="command">opreport -l -i __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code></pre>
+ </div><div class="para">
+ returns the following output:
</div><pre class="screen">samples % symbol name
12 100.000 __gconv_transform_utf8_internal</pre><div class="para">
The first line is a summary for the symbol/executable combination.
</div><div class="para">
The first column is the number of samples for the memory symbol. The second column is the percentage of samples for the memory address relative to the total number of samples for the symbol. The third column is the symbol name.
</div></dd><dt class="varlistentry"><span class="term"> <code class="option">-d</code> </span></dt><dd><div class="para">
- List sample data by symbols with more detail than <code class="option">-l</code>. For example, the following output is from the command <code class="command">opreport -l -d __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code>:
+ This option lists sample data by symbols with more detail than the <code class="option">-l</code> option. For example, with the following command: <pre class="synopsis">~]# <code class="command">opreport -d -i __gconv_transform_utf8_internal /lib/tls/libc-<em class="replaceable"><code>version</code></em>.so</code></pre>
+ </div><div class="para">
+ this output is returned:
</div><pre class="screen">vma samples % symbol name
00a98640 12 100.000 __gconv_transform_utf8_internal
00a98640 1 8.3333
@@ -64,8 +70,8 @@
00a98869 1 8.3333
00a98b08 1 8.3333</pre><div class="para">
The data is the same as the <code class="option">-l</code> option except that for each symbol, each virtual memory address used is shown. For each virtual memory address, the number of samples and percentage of samples relative to the number of samples for the symbol is displayed.
- </div></dd><dt class="varlistentry"><span class="term"> <code class="option">-x</code> <em class="replaceable"><code>symbol-name</code></em> </span></dt><dd><div class="para">
- Exclude the comma-separated list of symbols from the output.
+ </div></dd><dt class="varlistentry"><span class="term"> <code class="option">-e</code> <em class="replaceable"><code>symbol-name</code></em>… </span></dt><dd><div class="para">
+ With this option, you can exclude some symbols from the output. Replace <em class="replaceable"><code>symbol-name</code></em> with the comma-separated list of symbols you want to exclude.
</div></dd><dt class="varlistentry"><span class="term"> <code class="option">session</code>:<em class="replaceable"><code>name</code></em> </span></dt><dd><div class="para">
- Specify the full path to the session or a directory relative to the <code class="filename">/var/lib/oprofile/samples/</code> directory.
- </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-analyzing-data.html"><strong>Prev</strong>19.5. Analyzing the Data</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-oprofile-module-output.html"><strong>Next</strong>19.5.3. Getting more detailed output on the modul...</a></li></ul></body></html>
\ No newline at end of file
+ Here, you can specify the full path to the session, a directory relative to the <code class="filename">/var/lib/oprofile/samples/</code> directory, or if you are using <code class="command">operf</code>, a directory relative to <code class="filename">./oprofile_data/samples/</code>.
+ </div></dd></dl></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-oprofile-analyzing-data.html"><strong>Prev</strong>19.6. Analyzing the Data</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-oprofile-module-output.html"><strong>Next</strong>19.6.3. Getting More Detailed Output on the Modul...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-starting-separate.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-starting-separate.html
index 6961249..458b047 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-starting-separate.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-oprofile-starting-separate.html
@@ -1,33 +1,33 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>19.2.3. Separating Kernel and User-space Profiles</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. Separating Kernel and User-space Profiles</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-oprofile-configuring.html" title="19.2. Configuring OProfile" /><link rel="prev" href="s2-oprofile-events.html" title="19.2.2. Setting Events to Monitor" /><link rel="next" href="s1-oprofile-starting.html" title="19.3. Starting and Stopping OProfile" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-events.html"><strong>Prev</strong></a></li><l
i class="next"><a accesskey="n" href="s1-oprofile-starting.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-oprofile-starting-separate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.2.3. Separating Kernel and User-space Profiles</h3></div></div></div><a id="idm225479504592" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-oprofile-configuring.html" title="19.3. Configuring OProfile Using Legacy Mode" /><link rel="prev" href="s2-oprofile-events.html" title="19.3.2. Setting Events to Monitor" /><link rel="next" href="s1-oprofile-starting.html" title="19.4. Starting and Stopping OProfile Using Legacy Mode" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-events.ht
ml"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-oprofile-starting.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-oprofile-starting-separate"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">19.3.3. Separating Kernel and User-space Profiles</h3></div></div></div><a id="idm261723594576" class="indexterm"></a><div class="para">
By default, kernel mode and user mode information is gathered for each event. To configure OProfile to ignore events in kernel mode for a specific counter, execute the following command:
</div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em>:0</code></pre><div class="para">
Execute the following command to start profiling kernel mode for the counter again:
</div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em>:1</code></pre><div class="para">
To configure OProfile to ignore events in user mode for a specific counter, execute the following command:
- </div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em>:<em class="replaceable"><code>kernel</code></em>:0</code></pre><div class="para">
+ </div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em>:1:0</code></pre><div class="para">
Execute the following command to start profiling user mode for the counter again:
- </div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em>:<em class="replaceable"><code>kernel</code></em>:1</code></pre><div class="para">
+ </div><pre class="screen">~]# <code class="command">opcontrol --event=<em class="replaceable"><code>event-name</code></em>:<em class="replaceable"><code>sample-rate</code></em>:<em class="replaceable"><code>unit-mask</code></em>:1:1</code></pre><div class="para">
When the OProfile daemon writes the profile data to sample files, it can separate the kernel and library profile data into separate sample files. To configure how the daemon writes to sample files, execute the following command as root:
</div><pre class="screen">~]# <code class="command">opcontrol --separate=<em class="replaceable"><code>choice</code></em></code></pre><div class="para">
- <em class="replaceable"><code>choice</code></em> can be one of the following:
+ The <em class="replaceable"><code>choice</code></em> argument can be one of the following:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
- <code class="computeroutput">none</code> — do not separate the profiles (default)
+ <code class="computeroutput">none</code> — Do not separate the profiles (default).
</div></li><li class="listitem"><div class="para">
- <code class="command">library</code> — generate per-application profiles for libraries
+ <code class="command">library</code> — Generate per-application profiles for libraries.
</div></li><li class="listitem"><div class="para">
- <code class="command">kernel</code> — generate per-application profiles for the kernel and kernel modules
+ <code class="command">kernel</code> — Generate per-application profiles for the kernel and kernel modules.
</div></li><li class="listitem"><div class="para">
- <code class="command">all</code> — generate per-application profiles for libraries and per-application profiles for the kernel and kernel modules
+ <code class="command">all</code> — Generate per-application profiles for libraries and per-application profiles for the kernel and kernel modules.
</div></li></ul></div><div class="para">
If <code class="option">--separate=library</code> is used, the sample file name includes the name of the executable as well as the name of the library.
</div><div class="note"><div class="admonition_header"><h2>Restart the OProfile profiler</h2></div><div class="admonition"><div class="para">
These configuration changes will take effect when the OProfile profiler is restarted.
- </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-events.html"><strong>Prev</strong>19.2.2. Setting Events to Monitor</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-oprofile-starting.html"><strong>Next</strong>19.3. Starting and Stopping OProfile</a></li></ul></body></html>
\ No newline at end of file
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-oprofile-events.html"><strong>Prev</strong>19.3.2. Setting Events to Monitor</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-oprofile-starting.html"><strong>Next</strong>19.4. Starting and Stopping OProfile Using Legacy...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-parsing_JSON.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-parsing_JSON.html
new file mode 100644
index 0000000..c36e103
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-parsing_JSON.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.6.3. Parsing JSON</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-structured_logging_with_rsyslog.html" title="17.6. Structured Logging with Rsyslog" /><link rel="prev" href="s2-filtering_structured_messages.html" title="17.6.2. Filtering Structured Messages" /><link rel="next" href="s2-storing_messages_in_the_mongodb.html" title="17.6.4. Storing Messages in the MongoDB" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="
s2-filtering_structured_messages.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-storing_messages_in_the_mongodb.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-parsing_JSON"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.6.3. Parsing JSON</h3></div></div></div><div class="para">
+ The <code class="systemitem">mmjsonparse</code> module is used for parsing structured messages. These messages can come from <span class="application"><strong>Journal</strong></span> or from other input sources, and must be formatted in a way defined by the <span class="bold bold"><strong>Lumberjack</strong></span> project. These messages are identified by the presence of the <span class="bold bold"><strong>@cee:</strong></span> string. Then, <code class="systemitem">mmjsonparse</code> checks if the JSON structure is valid and then the message is parsed.
+ </div><div class="para">
+ To parse lumberjack-formatted JSON messages with <code class="systemitem">mmjsonparse</code>, use the following configuration in the <code class="filename">/etc/rsyslog.conf</code>:
+ </div><pre class="screen">
+$ModLoad mmjsonparse
+
+*.* :mmjsonparse:
+</pre><div class="para">
+ In this example, the <code class="systemitem">mmjsonparse</code> module is loaded on the first line, then all messages are forwarded to it. Currently, there are no configuration parameters available for <code class="systemitem">mmjsonparse</code>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-filtering_structured_messages.html"><strong>Prev</strong>17.6.2. Filtering Structured Messages</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-storing_messages_in_the_mongodb.html"><strong>Next</strong>17.6.4. Storing Messages in the MongoDB</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-freshening.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-freshening.html
index a1ff0ea..d2a690a 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-freshening.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-freshening.html
@@ -1,23 +1,17 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.3. Freshening Packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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">A.2.5. Freshening</h3></div></div></div><a id="idm225455260096" class="indexterm"></a><a id="idm225439466752" 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.fc21.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.
+ </script><link rel="home" href="index.html" title="System Administrator's 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.2. Uninstalling Packages" /><link rel="next" href="s2-rpm-querying.html" title="A.2.4. Querying Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-uninstalling.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-rp
m-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">A.2.3. Freshening Packages</h3></div></div></div><a id="idm261722068688" class="indexterm"></a><a id="idm261722067248" class="indexterm"></a><div class="para">
+ Freshening is similar to upgrading, except that only installed packages are upgraded. Type the following command at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code class="command">rpm -Fvh <em class="replaceable"><code>package.rpm</code></em></code></pre><div class="para">
+ The <code class="option">-F</code> (or <code class="option">--freshen</code>) option compares the versions of the packages specified on the command line with the versions of packages that are already installed on the system. When a newer version of an already-installed package is processed by the <code class="option">--freshen</code> option, it is upgraded to the newer version. However, the <code class="option">--freshen</code> option does not install a package if no previously-installed package of the same name exists. This differs from regular upgrading, as an upgrade installs all specified packages regardless of whether or not older versions of the packages are already installed.
</div><div class="para">
- Freshening works for single packages or package groups. 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>
\ No newline at end of file
+ Freshening works for single packages or package groups. For example, freshening can help if you download a large number of different packages, and you only want to upgrade those packages that are already installed on the system. In this case, issue the following command with the <code class="filename">*.rpm</code> global expression:
+ </div><pre class="screen">~]# <code class="command">rpm -Fvh *.rpm</code></pre><div class="para">
+ <span class="application"><strong>RPM</strong></span> then automatically upgrades only those packages that are already installed.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-uninstalling.html"><strong>Prev</strong>A.2.2. Uninstalling 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="s2-rpm-querying.html"><strong>Next</strong>A.2.4. Querying Packages</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-querying.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-querying.html
index 38c4554..70b43a6 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-querying.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-querying.html
@@ -1,35 +1,16 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.4. Querying Packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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"><str
ong>Next</strong></a></li></ul><div class="section" id="s2-rpm-querying"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">A.2.6. Querying</h3></div></div></div><a id="idm225480070128" class="indexterm"></a><a id="idm225480068688" 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.fc21.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>
\ No newline at end of file
+ </script><link rel="home" href="index.html" title="System Administrator's 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.3. Freshening Packages" /><link rel="next" href="s2-rpm-verifying.html" title="A.2.5. Verifying Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-freshening.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-rpm-ve
rifying.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-rpm-querying"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">A.2.4. Querying Packages</h3></div></div></div><a id="idm261722056080" class="indexterm"></a><a id="idm261722054640" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>RPM</strong></span> database stores information about all <span class="application"><strong>RPM</strong></span> packages installed on the system. It is stored in the <code class="filename">/var/lib/rpm/</code> directory and is used for many things, including querying what packages are installed, what version each package is, and for calculating changes to files in packages since their installation. To query this database, use the <code class="command">rpm</code> command with the <code class="option">-q</code> (or <code class="option">--query</code>) option:
+ </div><pre class="synopsis"><code class="command">rpm -q <em class="replaceable"><code>package_name</code></em></code></pre><div class="para">
+ This command displays the package name, version, and release number of the installed package <em class="replaceable"><code>package_name</code></em>. For example:
+ </div><pre class="screen">~]$ <code class="command">rpm -q tree</code>
+tree-1.7.0-3.fc21.x86_64</pre><div class="para">
+ See the <code class="computeroutput">Package Selection Options</code> subheading in the <span class="citerefentry"><span class="refentrytitle">rpm</span>(8)</span> manual page for a list of options that can be used to further refine or qualify your query. Use options listed below the <code class="computeroutput">Package Query Options</code> subheading to specify what information to display about the queried packages.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-freshening.html"><strong>Prev</strong>A.2.3. Freshening 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="s2-rpm-verifying.html"><strong>Next</strong>A.2.5. Verifying Packages</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-uninstalling.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-uninstalling.html
index 8cb66da..4813d3e 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-uninstalling.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-uninstalling.html
@@ -1,26 +1,23 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.2. Uninstalling Packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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 acc
esskey="n" href="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">A.2.4. Uninstalling</h3></div></div></div><a id="idm225500131584" class="indexterm"></a><a id="idm225500130144" class="indexterm"></a><a id="idm225500128704" class="indexterm"></a><a id="idm225500126784" 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.fc21.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.
+ </script><link rel="home" href="index.html" title="System Administrator's 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="s2-rpm-freshening.html" title="A.2.3. Freshening Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rpm-using.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-rpm-freshening.html"><stro
ng>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">A.2.2. Uninstalling Packages</h3></div></div></div><a id="idm261737770720" class="indexterm"></a><a id="idm261737769280" class="indexterm"></a><a id="idm261737767840" class="indexterm"></a><a id="idm261722439520" class="indexterm"></a><div class="para">
+ Uninstalling a package is just as simple as installing one. Type the following command at a shell prompt as <code class="systemitem">root</code>:
+ </div><pre class="synopsis"><code class="command">rpm -e <em class="replaceable"><code>package</code></em></code></pre><div class="note"><div class="admonition_header"><h2>rpm -e and package name errors</h2></div><div class="admonition"><div class="para">
+ Note that the command expects only the package <span class="emphasis"><em>name</em></span>, not the name of the original package <span class="emphasis"><em>file</em></span>. If you attempt to uninstall a package using the <code class="command">rpm -e</code> command and provide the original full file name, you receive a package-name error.
</div></div></div><div class="para">
You can encounter dependency errors when uninstalling a package if another installed package depends on the one you are trying to remove. For example:
- </div><pre class="screen">
-<code class="command">rpm -e ghostscript</code>
+ </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.fc21.x86_64
- libgs.so.8()(64bit) is needed by (installed) foomatic-4.0.3-1.fc21.x86_64
- libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.4-5.fc21.x86_64
- ghostscript is needed by (installed) printer-filters-1.1-4.fc21.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.fc21.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>
\ No newline at end of file
+ ghostscript is needed by (installed) ghostscript-cups-9.07-16.fc21.x86_64
+ ghostscript is needed by (installed) foomatic-4.0.9-6.fc21.x86_64
+ libgs.so.9()(64bit) is needed by (installed) libspectre-0.2.7-4.fc21.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed) gutenprint-5.2.9-15.fc21.x86_64
+ libijs-0.35.so()(64bit) is needed by (installed) cups-filters-1.0.35-15.fc21.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 you can <span class="emphasis"><em>force</em></span> <code class="command">rpm</code> to uninstall a package that has unresolved dependencies (using the <code class="option">--nodeps</code> option), this is <span class="emphasis"><em>not</em></span> recommended. Removing packages with <code class="option">--nodeps</code> can cause applications from the packages whose dependencies are removed to misbehave or terminate unexpectedly. It can also cause serious package-management problems or system failure. For these reasons, heed the warnings about failed dependencies.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-rpm-using.html"><strong>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="s2-rpm-freshening.html"><strong>Next</strong>A.2.3. Freshening Packages</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-verifying.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-verifying.html
index f313d0a..42a2a22 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-verifying.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-rpm-verifying.html
@@ -1,51 +1,87 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>A.2.5. Verifying Packages</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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-s
ig.html"><strong>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">A.2.7. Verifying</h3></div></div></div><a id="idm225472182112" class="indexterm"></a><a id="idm225472180672" 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.
+ </script><link rel="home" href="index.html" title="System Administrator's 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.4. Querying Packages" /><link rel="next" href="s1-find-verify-rpm.html" title="A.3. Finding and Verifying RPM Packages" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-querying.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href=
"s1-find-verify-rpm.html"><strong>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">A.2.5. Verifying Packages</h3></div></div></div><a id="idm261721881904" class="indexterm"></a><a id="idm261721880464" class="indexterm"></a><div class="para">
+ Verifying a package is comparing information about files on the system installed from a package with the same information from the original package. Among other parameters, verifying compares the file size, MD5 sum, permissions, type, owner, and the group of each file.
</div><div class="para">
- 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.fc21.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">
+ Use the <code class="command">rpm</code> command with the <code class="option">-V</code> (or <code class="option">--verify</code>) option to verify packages. For example:
+ </div><pre class="screen">~]$ <code class="command">rpm -V tree</code></pre><div class="para">
+ See the <code class="computeroutput">Package Selection Options</code> subheading in the <span class="citerefentry"><span class="refentrytitle">rpm</span>(8)</span> manual page for a list of options that can be used to further refine or qualify your query. Use options listed below the <code class="computeroutput">Verify Options</code> subheading to specify what characteristics to verify in the queried packages.
+ </div><div class="para">
+ If everything verifies properly, there is no output. If there are any discrepancies, they are displayed. The output consists of lines similar to these:
+ </div><pre class="screen">~]# <code class="command">rpm -V abrt</code>
+S.5....T. c /etc/abrt/abrt.conf
+.M....... /var/spool/abrt-upload</pre><div class="para">
+ The format of the output is a string of nine characters followed by an optional attribute marker and the name of the processed file.
+ </div><div class="para">
+ The first nine characters are the results of tests performed on the file. Each test is the comparison of one attribute of the file to the value of that attribute as recorded in the <span class="application"><strong>RPM</strong></span> database. A single period (<code class="computeroutput">.</code>) means the test passed, and the question-mark character (<code class="computeroutput">?</code>) signifies that the test could not be performed. The following table lists symbols that denote specific discrepancies:
+ </div><div class="table" id="tab-rpm-verification-symbols"><h6>Table A.1. RPM Verification Symbols</h6><div class="table-contents"><a id="idm261721706048" class="indexterm"></a><table summary="RPM Verification Symbols" border="1"><colgroup><col width="20%" class="symbol" /><col width="80%" class="description" /></colgroup><thead><tr><th class="">
+ Symbol
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="computeroutput">S</code>
+ </td><td class="">
+ file size differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">M</code>
+ </td><td class="">
+ mode differs (includes permissions and file type)
+ </td></tr><tr><td class="">
+ <code class="computeroutput">5</code>
+ </td><td class="">
+ digest (formerly MD5 sum) differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">D</code>
+ </td><td class="">
+ device major/minor number mismatch
+ </td></tr><tr><td class="">
+ <code class="computeroutput">L</code>
+ </td><td class="">
+ <span class="citerefentry"><span class="refentrytitle">readLink</span>(2)</span> path mismatch
+ </td></tr><tr><td class="">
+ <code class="computeroutput">U</code>
+ </td><td class="">
+ user ownership differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">G</code>
+ </td><td class="">
+ group ownership differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">T</code>
+ </td><td class="">
+ mtime differs
+ </td></tr><tr><td class="">
+ <code class="computeroutput">P</code>
+ </td><td class="">
+ capabilities differ
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ The attribute marker, if present, describes the purpose of the given file. The following table lists the available attribute markers:
+ </div><div class="table" id="tab-rpm-verification-markers"><h6>Table A.2. RPM Verification Symbols</h6><div class="table-contents"><a id="idm261721071456" class="indexterm"></a><table summary="RPM Verification Symbols" border="1"><colgroup><col width="20%" class="marker" /><col width="80%" class="description" /></colgroup><thead><tr><th class="">
+ Marker
+ </th><th class="">
+ Description
+ </th></tr></thead><tbody><tr><td class="">
+ <code class="computeroutput">c</code>
+ </td><td class="">
+ configuration file
+ </td></tr><tr><td class="">
+ <code class="computeroutput">d</code>
+ </td><td class="">
+ documentation file
+ </td></tr><tr><td class="">
+ <code class="computeroutput">l</code>
+ </td><td class="">
+ license file
+ </td></tr><tr><td class="">
+ <code class="computeroutput">r</code>
+ </td><td class="">
+ readme file
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
If you see any output, use your best judgment to determine if you should remove the package, reinstall it, or fix the problem in another way.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-querying.html"><strong>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>
\ No newline at end of file
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-rpm-querying.html"><strong>Prev</strong>A.2.4. Querying 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-find-verify-rpm.html"><strong>Next</strong>A.3. Finding and Verifying RPM Packages</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-beyondshell-tcpip.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-beyondshell-tcpip.html
index c7e5c505..e4773d4 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-beyondshell-tcpip.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-beyondshell-tcpip.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-ssh-beyondshell.html" title="7.4. More Than a Secure Shell" /><link rel="prev" href="s1-ssh-beyondshell.html" title="7.4. More Than a Secure Shell" /><link rel="next" href="s1-openssh-additional-resources.html" title="7.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 clas
s="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">7.4.2. Port Forwarding</h3></div></div></div><a id="idm225470484176" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-ssh-beyondshell.html" title="7.4. More Than a Secure Shell" /><link rel="prev" href="s1-ssh-beyondshell.html" title="7.4. More Than a Secure Shell" /><link rel="next" href="s1-openssh-additional-resources.html" title="7.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 clas
s="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">7.4.2. Port Forwarding</h3></div></div></div><a id="idm261730487312" 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.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-clients-scp.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-clients-scp.html
index 002ba66..eca8e92 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-clients-scp.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-clients-scp.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-ssh-clients.html" title="7.3. OpenSSH Clients" /><link rel="prev" href="s1-ssh-clients.html" title="7.3. OpenSSH Clients" /><link rel="next" href="s2-ssh-clients-sftp.html" title="7.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-sftp.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">7.3.2. Using the <code class="command">scp</code> Utility</h3></div></div></div><a id="idm225438933472" class="indexterm"></a><a id="idm225453062320" class="indexterm"></a><a id="idm225453060240" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-ssh-clients.html" title="7.3. OpenSSH Clients" /><link rel="prev" href="s1-ssh-clients.html" title="7.3. OpenSSH Clients" /><link rel="next" href="s2-ssh-clients-sftp.html" title="7.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-sftp.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">7.3.2. Using the <code class="command">scp</code> Utility</h3></div></div></div><a id="idm261715176800" class="indexterm"></a><a id="idm261715175200" class="indexterm"></a><a id="idm261756260688" 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:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-clients-sftp.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-clients-sftp.html
index 638c504..4b3c52f 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-clients-sftp.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-clients-sftp.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-ssh-clients.html" title="7.3. OpenSSH Clients" /><link rel="prev" href="s2-ssh-clients-scp.html" title="7.3.2. Using the scp Utility" /><link rel="next" href="s1-ssh-beyondshell.html" title="7.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">7.3.3. Using the <code class="command">sftp</code> Utility</h3></div></div></div><a id="idm225448656848" class="indexterm"></a><a id="idm225448655248" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-ssh-clients.html" title="7.3. OpenSSH Clients" /><link rel="prev" href="s2-ssh-clients-scp.html" title="7.3.2. Using the scp Utility" /><link rel="next" href="s1-ssh-beyondshell.html" title="7.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">7.3.3. Using the <code class="command">sftp</code> Utility</h3></div></div></div><a id="idm261751786304" class="indexterm"></a><a id="idm261751784704" 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:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-configuration-keypairs.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-configuration-keypairs.html
index 1c39c81..ebf7fb4 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-configuration-keypairs.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-configuration-keypairs.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-ssh-configuration.html" title="7.2. An OpenSSH Configuration" /><link rel="prev" href="s2-ssh-configuration-requiring.html" title="7.2.3. Requiring SSH for Remote Connections" /><link rel="next" href="s1-ssh-clients.html" title="7.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><li 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">7.2.4. Using Key-based Authentication</h3></div></div></div><a id="idm225463127904" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-ssh-configuration.html" title="7.2. An OpenSSH Configuration" /><link rel="prev" href="s2-ssh-configuration-requiring.html" title="7.2.3. Requiring SSH for Remote Connections" /><link rel="next" href="s1-ssh-clients.html" title="7.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><li 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">7.2.4. Using Key-based Authentication</h3></div></div></div><a id="idm261758976976" class="indexterm"></a><div class="para">
To improve the system security even further, generate SSH key pairs and then enforce key-based authentication by disabling password authentication. To do so, open the <code class="filename">/etc/ssh/sshd_config</code> configuration file in a text editor such as <span class="application"><strong>vi</strong></span> or <span class="application"><strong>nano</strong></span>, and change the <code class="option">PasswordAuthentication</code> option as follows:
</div><pre class="screen">PasswordAuthentication no</pre><div class="para">
If you are working on a system other than a new default installation, check that <code class="command">PubkeyAuthentication no</code> has <span class="bold bold"><strong>not</strong></span> been set. If connected remotely, not using console or out-of-band access, testing the key-based log in process before disabling password authentication is advised.
@@ -18,9 +18,9 @@
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 pairs, backup the <code class="filename">~/.ssh/</code> directory. After reinstalling, copy it back to your home directory. This process can be done for all users on your system, including <code class="systemitem">root</code>.
- </div></div></div><div class="section" id="s3-ssh-configuration-keypairs-generating"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.2.4.1. Generating Key Pairs</h4></div></div></div><a id="idm225478008080" class="indexterm"></a><a id="idm225453077728" class="indexterm"></a><div class="para">
+ </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">7.2.4.1. Generating Key Pairs</h4></div></div></div><a id="idm261736313344" class="indexterm"></a><a id="idm261736311904" 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="idm225453075360" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ </div><a id="idm261736309536" 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.
@@ -51,9 +51,9 @@ The key's randomart image is:
~]$ ls -ld ~/.ssh/
drwx------. 2 USER USER 54 Nov 25 16:56 /home/USER/.ssh/</pre></li><li class="step"><div class="para">
To copy the public key to a remote machine, issue a command in the following format: <pre class="synopsis"> <code class="command">ssh-copy-id <em class="replaceable"><code>user at hostname</code></em></code></pre> This will copy all <code class="filename">~/.ssh/id*.pub</code> public keys. Alternatively, specify the public keys file name as follows: <pre class="synopsis"><code class="command">ssh-copy-id -i <code class="filename">~/.ssh/id_rsa.pub</code> <em class="replaceable"><code>user at hostname</code></em></code></pre> This will copy the content of <code class="filename">~/.ssh/id_rsa.pub</code> into the <code class="filename">~/.ssh/authorized_keys</code> file on the machine to which you want to connect. If the file already exists, the keys are appended to its end.
- </div></li></ol></div><a id="idm225459045168" class="indexterm"></a><a id="idm225462182320" class="indexterm"></a><div class="para">
+ </div></li></ol></div><a id="idm261748665280" class="indexterm"></a><a id="idm261748663840" class="indexterm"></a><div class="para">
To generate an ECDSA key pair for version 2 of the SSH protocol, follow these steps:
- </div><a id="idm225462179952" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ </div><a id="idm261748661360" class="indexterm"></a><div class="procedure"><ol class="1"><li class="step"><div class="para">
Generate an ECDSA key pair by typing the following at a shell prompt:
</div><pre class="screen">~]$ <code class="command">ssh-keygen -t ecdsa</code>
Generating public/private ecdsa key pair.
@@ -66,7 +66,7 @@ Enter file in which to save the key (/home/USER/.ssh/id_ecdsa):</pre></li><li cl
</div><pre class="screen">Your identification has been saved in /home/USER/.ssh/id_ecdsa.
Your public key has been saved in /home/USER/.ssh/id_ecdsa.pub.
The key fingerprint is:
-fd:1d:ca:10:52:96:21:43:7e:bd:4c:fc:5b:35:6b:63 USER at my-server
+fd:1d:ca:10:52:96:21:43:7e:bd:4c:fc:5b:35:6b:63 USER at penguin.example.com
The key's randomart image is:
+--[ECDSA 256]---+
| .+ +o |
@@ -88,7 +88,7 @@ drwx------. 2 USER USER 54 Nov 25 16:56 /home/USER/.ssh/</pre></li><li class="st
See <a class="xref" href="s2-ssh-configuration-keypairs.html#s3-ssh-configuration-keypairs-agent">Section 7.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">7.2.4.2. Configuring ssh-agent</h4></div></div></div><a id="idm225477353376" class="indexterm"></a><a id="idm225477351776" class="indexterm"></a><div class="para">
+ </div></div></div></div><div class="section" id="s3-ssh-configuration-keypairs-agent"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">7.2.4.2. Configuring ssh-agent</h4></div></div></div><a id="idm261745684560" class="indexterm"></a><a id="idm261745682960" 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/USER/.ssh/id_rsa:</pre><div class="para">
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-configuration-requiring.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-configuration-requiring.html
index 9ae846d..6f5d6e8 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-configuration-requiring.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-configuration-requiring.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-ssh-configuration.html" title="7.2. An OpenSSH Configuration" /><link rel="prev" href="s2-ssh-configuration-sshd.html" title="7.2.2. Starting an OpenSSH Server" /><link rel="next" href="s2-ssh-configuration-keypairs.html" title="7.2.4. Using Key-based Authentication" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-configuration-sshd.html"><strong>
Prev</strong></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">7.2.3. Requiring SSH for Remote Connections</h3></div></div></div><a id="idm225480775280" class="indexterm"></a><a id="idm225480773840" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-ssh-configuration.html" title="7.2. An OpenSSH Configuration" /><link rel="prev" href="s2-ssh-configuration-sshd.html" title="7.2.2. Starting an OpenSSH Server" /><link rel="next" href="s2-ssh-configuration-keypairs.html" title="7.2.4. Using Key-based Authentication" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ssh-configuration-sshd.html"><strong>
Prev</strong></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">7.2.3. Requiring SSH for Remote Connections</h3></div></div></div><a id="idm261754109712" class="indexterm"></a><a id="idm261754108272" 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">
These services are not installed by default in Fedora. If required, to make sure these services are not running, type the following commands at a shell prompt:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-configuration-sshd.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-configuration-sshd.html
index 9031e61..39312cf 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-configuration-sshd.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-ssh-configuration-sshd.html
@@ -6,11 +6,11 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-ssh-configuration.html" title="7.2. An OpenSSH Configuration" /><link rel="prev" href="s1-ssh-configuration.html" title="7.2. An OpenSSH Configuration" /><link rel="next" href="s2-ssh-configuration-requiring.html" title="7.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</s
trong></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">7.2.2. Starting an OpenSSH Server</h3></div></div></div><a id="idm225459237776" 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">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-ssh-configuration.html" title="7.2. An OpenSSH Configuration" /><link rel="prev" href="s1-ssh-configuration.html" title="7.2. An OpenSSH Configuration" /><link rel="next" href="s2-ssh-configuration-requiring.html" title="7.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</s
trong></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">7.2.2. Starting an OpenSSH Server</h3></div></div></div><a id="idm261759572128" 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> package installed. See <a class="xref" href="sec-Installing.html">Section 5.2.4, “Installing Packages”</a> for more information on how to install new packages in Fedora.
- </div></div></div><a id="idm225459234032" class="indexterm"></a><div class="para">
+ </div></div></div><a id="idm261725588096" class="indexterm"></a><div class="para">
To start the <code class="command">sshd</code> daemon in the current session, type the following at a shell prompt as <code class="systemitem">root</code>:
- </div><pre class="screen">~]# <code class="command">systemctl start sshd.service</code></pre><a id="idm225460182784" class="indexterm"></a><div class="para">
+ </div><pre class="screen">~]# <code class="command">systemctl start sshd.service</code></pre><a id="idm261725583808" class="indexterm"></a><div class="para">
To stop the running <code class="command">sshd</code> daemon in the current session, use the following command as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">systemctl stop sshd.service</code></pre><div class="para">
If you want the daemon to start automatically at the boot time, type as <code class="systemitem">root</code>:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-storing_messages_in_the_mongodb.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-storing_messages_in_the_mongodb.html
new file mode 100644
index 0000000..2f34f4e
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-storing_messages_in_the_mongodb.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.6.4. Storing Messages in the MongoDB</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-structured_logging_with_rsyslog.html" title="17.6. Structured Logging with Rsyslog" /><link rel="prev" href="s2-parsing_JSON.html" title="17.6.3. Parsing JSON" /><link rel="next" href="s1-debugging_rsyslog.html" title="17.7. Debugging Rsyslog" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-parsing_JSON.html"><strong>Prev</strong></a></li><li class="n
ext"><a accesskey="n" href="s1-debugging_rsyslog.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-storing_messages_in_the_mongodb"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.6.4. Storing Messages in the MongoDB</h3></div></div></div><div class="para">
+ <span class="application"><strong>Rsyslog</strong></span> supports storing JSON logs in the <span class="database">MongoDB</span> document database through the <span class="emphasis"><em>ommongodb</em></span> output module.
+ </div><div class="para">
+ To forward log messages into <span class="database">MongoDB</span>, use the following syntax in the <code class="filename">/etc/rsyslog.conf</code> (configuration parameters for <span class="emphasis"><em>ommongodb</em></span> are available only in the new configuration format; see <a class="xref" href="s2-using_the_new_configuration_format.html">Section 17.2.6, “Using the New Configuration Format”</a>):
+ </div><pre class="screen">
+$ModLoad ommongodb
+
+*.* action(type="ommongodb" server="<em class="replaceable"><code>DB_server</code></em>" serverport="<em class="replaceable"><code>port</code></em>" db="<em class="replaceable"><code>DB_name</code></em>" collection="<em class="replaceable"><code>collection_name</code></em>" uid="<em class="replaceable"><code>UID</code></em>" pwd="<em class="replaceable"><code>password</code></em>")
+</pre><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Replace <em class="replaceable"><code>DB_server</code></em> with the name or address of the MongoDB server. Specify <em class="replaceable"><code>port</code></em> to select a non-standard port from the MongoDB server. The default <em class="replaceable"><code>port</code></em> value is <code class="literal">0</code> and usually there is no need to change this parameter.
+ </div></li><li class="listitem"><div class="para">
+ With <em class="replaceable"><code>DB_name</code></em>, you identify to which database on the MongoDB server you want to direct the output. Replace <em class="replaceable"><code>collection_name</code></em> with the name of a collection in this database. In <span class="database">MongoDB</span>, collection is a group of documents, the equivalent of an RDBMS table.
+ </div></li><li class="listitem"><div class="para">
+ You can set your login details by replacing <em class="replaceable"><code>UID</code></em> and <em class="replaceable"><code>password</code></em>.
+ </div></li></ul></div><div class="para">
+ You can shape the form of the final database output with use of templates. By default, <span class="application"><strong>ryslog</strong></span> uses a template based on standard <span class="application"><strong>lumberjack</strong></span> field names.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-parsing_JSON.html"><strong>Prev</strong>17.6.3. Parsing JSON</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-debugging_rsyslog.html"><strong>Next</strong>17.7. Debugging Rsyslog</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-blkid.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-blkid.html
index 7a48ad9..1127093 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-blkid.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-blkid.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /><link rel="prev" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /><link rel="next" href="s2-sysinfo-filesystems-partx.html" title="16.4.3. Using the partx Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-filesystems
.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-filesystems-partx.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-filesystems-blkid"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.2. Using the blkid Command</h3></div></div></div><a id="idm225481537440" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /><link rel="prev" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /><link rel="next" href="s2-sysinfo-filesystems-partx.html" title="16.4.3. Using the partx Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-filesystems
.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-filesystems-partx.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-filesystems-blkid"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.2. Using the blkid Command</h3></div></div></div><a id="idm261741534320" class="indexterm"></a><div class="para">
The <code class="command">blkid</code> command allows you to display information about available block devices. To do so, type the following at a shell prompt as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">blkid</code></pre><div class="para">
For each listed block device, the <code class="command">blkid</code> command displays available attributes such as its <em class="firstterm">universally unique identifier</em> (<code class="computeroutput">UUID</code>), file system type (<code class="computeroutput">TYPE</code>), or volume label (<code class="computeroutput">LABEL</code>). For example:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-df.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-df.html
index 4c1ac3a..43e4cfb 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-df.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-df.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /><link rel="prev" href="s2-sysinfo-filesystems-findmnt.html" title="16.4.4. Using the findmnt Command" /><link rel="next" href="s2-sysinfo-filesystems-du.html" title="16.4.6. Using the du Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-filesystems-findmnt.
html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-filesystems-du.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-filesystems-df"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.5. Using the df Command</h3></div></div></div><a id="idm225500123984" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /><link rel="prev" href="s2-sysinfo-filesystems-findmnt.html" title="16.4.4. Using the findmnt Command" /><link rel="next" href="s2-sysinfo-filesystems-du.html" title="16.4.6. Using the du Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-filesystems-findmnt.
html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-filesystems-du.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-filesystems-df"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.5. Using the df Command</h3></div></div></div><a id="idm261753982320" class="indexterm"></a><div class="para">
The <code class="command">df</code> command allows you to display a detailed report on the system's disk space usage. To do so, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">df</code></pre><div class="para">
For each listed file system, the <code class="command">df</code> command displays its name (<code class="computeroutput">Filesystem</code>), size (<code class="computeroutput">1K-blocks</code> or <code class="computeroutput">Size</code>), how much space is used (<code class="computeroutput">Used</code>), how much space is still available (<code class="computeroutput">Available</code>), the percentage of space usage (<code class="computeroutput">Use%</code>), and where is the file system mounted (<code class="computeroutput">Mounted on</code>). For example:
@@ -32,7 +32,7 @@ tmpfs 373M 3.0M 370M 1% /run
/dev/mapper/vg_fedora-lv_root 19G 4.4G 14G 25% /
tmpfs 373M 0 373M 0% /sys/fs/cgroup
tmpfs 373M 0 373M 0% /media
-/dev/vda1 497M 84M 389M 18% /boot</pre><a id="idm225478370160" class="indexterm"></a><a id="idm225478368080" class="indexterm"></a><a id="idm225478366960" class="indexterm"></a><a id="idm225476189456" class="indexterm"></a><a id="idm225476188336" class="indexterm"></a><a id="idm225476186256" class="indexterm"></a><div class="para">
+/dev/vda1 497M 84M 389M 18% /boot</pre><a id="idm261747632800" class="indexterm"></a><a id="idm261747630720" class="indexterm"></a><a id="idm261747629600" class="indexterm"></a><a id="idm261749405440" class="indexterm"></a><a id="idm261749404320" class="indexterm"></a><a id="idm261749402240" class="indexterm"></a><div class="para">
Note that the <code class="filename">/dev/shm</code> entry represents the system's virtual memory file system, <code class="filename">/sys/fs/cgroup</code> is a cgroup file system, and <code class="filename">/run</code> contains information about the running system.
</div><div class="para">
For a complete list of available command line options, refer to the <span class="bold bold"><strong>df</strong></span>(1) manual page.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-du.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-du.html
index d0d4101..d6b1d25 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-du.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-du.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /><link rel="prev" href="s2-sysinfo-filesystems-df.html" title="16.4.5. Using the df Command" /><link rel="next" href="s2-sysinfo-filesystems-system_monitor.html" title="16.4.7. Using the System Monitor Tool" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-filesyste
ms-df.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-filesystems-system_monitor.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-filesystems-du"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.6. Using the du Command</h3></div></div></div><a id="idm225478129488" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /><link rel="prev" href="s2-sysinfo-filesystems-df.html" title="16.4.5. Using the df Command" /><link rel="next" href="s2-sysinfo-filesystems-system_monitor.html" title="16.4.7. Using the System Monitor Tool" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-filesyste
ms-df.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-filesystems-system_monitor.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-filesystems-du"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.6. Using the du Command</h3></div></div></div><a id="idm261758376400" class="indexterm"></a><div class="para">
The <code class="command">du</code> command allows you to displays the amount of space that is being used by files in a directory. To display the disk usage for each of the subdirectories in the current working directory, run the command with no additional command line options:
</div><pre class="synopsis"><code class="command">du</code></pre><div class="para">
For example:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-findmnt.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-findmnt.html
index 0949a10..774600e 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-findmnt.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-findmnt.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /><link rel="prev" href="s2-sysinfo-filesystems-partx.html" title="16.4.3. Using the partx Command" /><link rel="next" href="s2-sysinfo-filesystems-df.html" title="16.4.5. Using the df Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-filesystems-partx.html">
<strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-filesystems-df.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-filesystems-findmnt"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.4. Using the findmnt Command</h3></div></div></div><a id="idm225459817120" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /><link rel="prev" href="s2-sysinfo-filesystems-partx.html" title="16.4.3. Using the partx Command" /><link rel="next" href="s2-sysinfo-filesystems-df.html" title="16.4.5. Using the df Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-filesystems-partx.html">
<strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-filesystems-df.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-filesystems-findmnt"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.4. Using the findmnt Command</h3></div></div></div><a id="idm261746839376" class="indexterm"></a><div class="para">
The <code class="command">findmnt</code> command allows you to display a list of currently mounted file systems. To do so, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">findmnt</code></pre><div class="para">
For each listed file system, the <code class="command">findmnt</code> command displays the target mount point (<code class="computeroutput">TARGET</code>), source device (<code class="computeroutput">SOURCE</code>), file system type (<code class="computeroutput">FSTYPE</code>), and relevant mount options (<code class="computeroutput">OPTIONS</code>). For example:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-partx.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-partx.html
index 49a16e7..0cbfde7 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-partx.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-partx.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /><link rel="prev" href="s2-sysinfo-filesystems-blkid.html" title="16.4.2. Using the blkid Command" /><link rel="next" href="s2-sysinfo-filesystems-findmnt.html" title="16.4.4. Using the findmnt Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-filesystems-bl
kid.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-filesystems-findmnt.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-filesystems-partx"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.3. Using the partx Command</h3></div></div></div><a id="idm225479332608" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /><link rel="prev" href="s2-sysinfo-filesystems-blkid.html" title="16.4.2. Using the blkid Command" /><link rel="next" href="s2-sysinfo-filesystems-findmnt.html" title="16.4.4. Using the findmnt Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-filesystems-bl
kid.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-filesystems-findmnt.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-filesystems-partx"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.3. Using the partx Command</h3></div></div></div><a id="idm261748805984" class="indexterm"></a><div class="para">
The <code class="command">partx</code> command allows you to display a list of disk partitions. To list the partition table of a particular disk, as <code class="systemitem">root</code>, run this command with the <code class="option">-s</code> option followed by the device name:
</div><pre class="synopsis"><code class="command">partx</code> <code class="option">-s</code> <em class="replaceable"><code>device_name</code></em></pre><div class="para">
For example, to list partitions on <code class="filename">/dev/vda</code>, type:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-system_monitor.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-system_monitor.html
index 28174dc..954a7d0 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-system_monitor.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-filesystems-system_monitor.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /><link rel="prev" href="s2-sysinfo-filesystems-du.html" title="16.4.6. Using the du Command" /><link rel="next" href="s1-sysinfo-hardware.html" title="16.5. Viewing Hardware Information" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-filesystems-du.html"><strong>P
rev</strong></a></li><li class="next"><a accesskey="n" href="s1-sysinfo-hardware.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-filesystems-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.7. Using the System Monitor Tool</h3></div></div></div><a id="idm225464734400" class="indexterm"></a><a id="idm225464733280" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-filesystems.html" title="16.4. Viewing Block Devices and File Systems" /><link rel="prev" href="s2-sysinfo-filesystems-du.html" title="16.4.6. Using the du Command" /><link rel="next" href="s1-sysinfo-hardware.html" title="16.5. Viewing Hardware Information" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-filesystems-du.html"><strong>P
rev</strong></a></li><li class="next"><a accesskey="n" href="s1-sysinfo-hardware.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-filesystems-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.4.7. Using the System Monitor Tool</h3></div></div></div><a id="idm261758345680" class="indexterm"></a><a id="idm261758344560" class="indexterm"></a><div class="para">
The <span class="guilabel"><strong>File Systems</strong></span> tab of the <span class="application"><strong>System Monitor</strong></span> tool allows you to view file systems and disk space usage in the graphical user interface.
</div><div class="para">
To start the <span class="application"><strong>System Monitor</strong></span> tool, either select <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Monitor</strong></span> from the <span class="guimenu"><strong>Activities</strong></span> menu, or type <code class="command">gnome-system-monitor</code> at a shell prompt. Then click the <span class="guilabel"><strong>File Systems</strong></span> tab to view a list of file systems.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-hardware-lscpu.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-hardware-lscpu.html
index a80affc..dc56214 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-hardware-lscpu.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-hardware-lscpu.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-hardware.html" title="16.5. Viewing Hardware Information" /><link rel="prev" href="s2-sysinfo-hardware-lspcmcia.html" title="16.5.3. Using the lspcmcia Command" /><link rel="next" href="sect-System_Monitoring_Tools-Net-SNMP.html" title="16.6. Monitoring Performance with Net-SNMP" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-hardware
-lspcmcia.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-System_Monitoring_Tools-Net-SNMP.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-hardware-lscpu"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.4. Using the lscpu Command</h3></div></div></div><a id="idm225444694080" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-hardware.html" title="16.5. Viewing Hardware Information" /><link rel="prev" href="s2-sysinfo-hardware-lspcmcia.html" title="16.5.3. Using the lspcmcia Command" /><link rel="next" href="sect-System_Monitoring_Tools-Net-SNMP.html" title="16.6. Monitoring Performance with Net-SNMP" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-hardware
-lspcmcia.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-System_Monitoring_Tools-Net-SNMP.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-hardware-lscpu"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.4. Using the lscpu Command</h3></div></div></div><a id="idm261778083680" class="indexterm"></a><div class="para">
The <code class="command">lscpu</code> command allows you to list information about CPUs that are present in the system, including the number of CPUs, their architecture, vendor, family, model, CPU caches, etc. To do so, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">lscpu</code></pre><div class="para">
For example:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-hardware-lspcmcia.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-hardware-lspcmcia.html
index 5ee3514..e74b8cf 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-hardware-lspcmcia.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-hardware-lspcmcia.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-hardware.html" title="16.5. Viewing Hardware Information" /><link rel="prev" href="s2-sysinfo-hardware-lsusb.html" title="16.5.2. Using the lsusb Command" /><link rel="next" href="s2-sysinfo-hardware-lscpu.html" title="16.5.4. Using the lscpu Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-hardware-lsusb.html"><strong>Prev</st
rong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-hardware-lscpu.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-hardware-lspcmcia"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.3. Using the lspcmcia Command</h3></div></div></div><a id="idm225464399680" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-hardware.html" title="16.5. Viewing Hardware Information" /><link rel="prev" href="s2-sysinfo-hardware-lsusb.html" title="16.5.2. Using the lsusb Command" /><link rel="next" href="s2-sysinfo-hardware-lscpu.html" title="16.5.4. Using the lscpu Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-sysinfo-hardware-lsusb.html"><strong>Prev</st
rong></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-hardware-lscpu.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-hardware-lspcmcia"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.3. Using the lspcmcia Command</h3></div></div></div><a id="idm261738710544" class="indexterm"></a><div class="para">
The <code class="command">lspcmcia</code> command allows you to list all PCMCIA devices that are present in the system. To do so, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">lspcmcia</code></pre><div class="para">
For example:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-hardware-lsusb.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-hardware-lsusb.html
index eb3e4ce..ac8cb2e 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-hardware-lsusb.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-hardware-lsusb.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-hardware.html" title="16.5. Viewing Hardware Information" /><link rel="prev" href="s1-sysinfo-hardware.html" title="16.5. Viewing Hardware Information" /><link rel="next" href="s2-sysinfo-hardware-lspcmcia.html" title="16.5.3. Using the lspcmcia Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-hardware.html"><strong>Prev</stron
g></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-hardware-lspcmcia.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-hardware-lsusb"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.2. Using the lsusb Command</h3></div></div></div><a id="idm225499518208" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-hardware.html" title="16.5. Viewing Hardware Information" /><link rel="prev" href="s1-sysinfo-hardware.html" title="16.5. Viewing Hardware Information" /><link rel="next" href="s2-sysinfo-hardware-lspcmcia.html" title="16.5.3. Using the lspcmcia Command" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-hardware.html"><strong>Prev</stron
g></a></li><li class="next"><a accesskey="n" href="s2-sysinfo-hardware-lspcmcia.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-hardware-lsusb"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.5.2. Using the lsusb Command</h3></div></div></div><a id="idm261784815696" class="indexterm"></a><div class="para">
The <code class="command">lsusb</code> command allows you to display information about USB buses and devices that are attached to them. To list all USB devices that are in the system, type the following at a shell prompt:
</div><pre class="synopsis"><code class="command">lsusb</code></pre><div class="para">
This displays a simple list of devices, for example:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-memory-usage-system_monitor.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-memory-usage-system_monitor.html
index 5a8e2e4..13ba4fa 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-memory-usage-system_monitor.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-sysinfo-memory-usage-system_monitor.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-memory-usage.html" title="16.2. Viewing Memory Usage" /><link rel="prev" href="s1-sysinfo-memory-usage.html" title="16.2. Viewing Memory Usage" /><link rel="next" href="s1-sysinfo-cpu.html" title="16.3. Viewing CPU Usage" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-memory-usage.html"><strong>Prev</strong></a></li><li class="next"><
a accesskey="n" href="s1-sysinfo-cpu.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-memory-usage-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.2.2. Using the System Monitor Tool</h3></div></div></div><a id="idm225468221984" class="indexterm"></a><a id="idm225468220864" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-sysinfo-memory-usage.html" title="16.2. Viewing Memory Usage" /><link rel="prev" href="s1-sysinfo-memory-usage.html" title="16.2. Viewing Memory Usage" /><link rel="next" href="s1-sysinfo-cpu.html" title="16.3. Viewing CPU Usage" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-sysinfo-memory-usage.html"><strong>Prev</strong></a></li><li class="next"><
a accesskey="n" href="s1-sysinfo-cpu.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-sysinfo-memory-usage-system_monitor"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">16.2.2. Using the System Monitor Tool</h3></div></div></div><a id="idm261714733024" class="indexterm"></a><a id="idm261714731904" class="indexterm"></a><div class="para">
The <span class="guilabel"><strong>Resources</strong></span> tab of the <span class="application"><strong>System Monitor</strong></span> tool allows you to view the amount of free and used memory on the system.
</div><div class="para">
To start the <span class="application"><strong>System Monitor</strong></span> tool, either select <span class="guimenu"><strong>Applications</strong></span> → <span class="guisubmenu"><strong>System Tools</strong></span> → <span class="guimenuitem"><strong>System Monitor</strong></span> from the <span class="guimenu"><strong>Activities</strong></span> menu, or type <code class="command">gnome-system-monitor</code> at a shell prompt. Then click the <span class="guilabel"><strong>Resources</strong></span> tab to view the system's memory usage.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-users-tools-groups-add.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-users-tools-groups-add.html
index 7461144..ae89db3 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-users-tools-groups-add.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-users-tools-groups-add.html
@@ -6,11 +6,11 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-users-tools.html" title="4.3. Using Command Line Tools" /><link rel="prev" href="s1-users-tools.html" title="4.3. Using Command Line Tools" /><link rel="next" href="s2-users-tools-password-aging.html" title="4.3.3. Enabling Password Aging" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 accesskey="n" href="s2-users-tools-password-aging.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-users-tools-groups-add"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.2. Adding a New Group</h3></div></div></div><a id="idm225468716528" class="indexterm"></a><a id="idm225468714928" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-users-tools.html" title="4.3. Using Command Line Tools" /><link rel="prev" href="s1-users-tools.html" title="4.3. Using Command Line Tools" /><link rel="next" href="s2-users-tools-password-aging.html" title="4.3.3. Enabling Password Aging" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 accesskey="n" href="s2-users-tools-password-aging.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-users-tools-groups-add"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.2. Adding a New Group</h3></div></div></div><a id="idm261715839936" class="indexterm"></a><a id="idm261715838336" class="indexterm"></a><div class="para">
To add a new group to the system, type the following at a shell prompt as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">groupadd</code> [<span class="optional"><em class="replaceable"><code>options</code></em></span>] <em class="replaceable"><code>group_name</code></em></pre><div class="para">
- …where <em class="replaceable"><code>options</code></em> are command line options as described in <a class="xref" href="s2-users-tools-groups-add.html#table-groupadd-options">Table 4.3, “groupadd command line options”</a>.
- </div><div class="table" id="table-groupadd-options"><h6>Table 4.3. groupadd command line options</h6><div class="table-contents"><table summary="groupadd command line options" border="1"><colgroup><col width="30%" class="option" /><col width="70%" class="description" /></colgroup><thead><tr><th class="">
+ …where <em class="replaceable"><code>options</code></em> are command-line options as described in <a class="xref" href="s2-users-tools-groups-add.html#table-groupadd-options">Table 4.3, “Common groupadd command-line options”</a>.
+ </div><div class="table" id="table-groupadd-options"><h6>Table 4.3. Common groupadd command-line options</h6><div class="table-contents"><table summary="Common groupadd command-line options" border="1"><colgroup><col width="30%" class="option" /><col width="70%" class="description" /></colgroup><thead><tr><th class="">
Option
</th><th class="">
Description
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-users-tools-groups-directories.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-users-tools-groups-directories.html
index 6ccc95c..ac945b5 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-users-tools-groups-directories.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-users-tools-groups-directories.html
@@ -6,8 +6,8 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-users-tools.html" title="4.3. Using Command Line Tools" /><link rel="prev" href="s2-users-tools-users-logout.html" title="4.3.4. Enabling Automatic Logouts" /><link rel="next" href="s1-users-groups-additional-resources.html" title="4.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="s2-users-tools-users-logout.html"><strong>Prev</s
trong></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="s2-users-tools-groups-directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.5. Creating Group Directories</h3></div></div></div><a id="idm225504129392" class="indexterm"></a><a id="idm225504127952" 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.
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-users-tools.html" title="4.3. Using Command Line Tools" /><link rel="prev" href="s2-users-tools-users-logout.html" title="4.3.4. Enabling Automatic Logouts" /><link rel="next" href="sect-Users_and_Groups-Resources.html" title="4.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="s2-users-tools-users-logout.html"><strong>Prev</strong
></a></li><li class="next"><a accesskey="n" href="sect-Users_and_Groups-Resources.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-users-tools-groups-directories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.5. Creating Group Directories</h3></div></div></div><a id="idm261741553200" class="indexterm"></a><a id="idm261741551760" class="indexterm"></a><div class="para">
+ System administrators usually like to create a group for each major project and assign people to the group when they need to access that project's files. With this traditional scheme, file management is difficult; when someone creates a file, it is associated with the primary group to which they belong. When a single person works on multiple projects, it becomes difficult to associate the right files with the right group. However, with the UPG scheme, groups are automatically assigned to files created within a directory with the <em class="firstterm">setgid</em> bit set. The setgid bit makes managing group projects that share a common directory very simple because any files a user creates within the directory are owned by the group that owns the directory.
</div><div class="para">
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">
@@ -17,9 +17,11 @@
</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><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-users-tools-users-logout.html"><strong>Prev</strong>4.3.4. Enabling Automatic Logouts</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>4.4. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
+ Allow users in the group to create files within the directory and set the setgid bit:
+ </div><pre class="screen"><code class="command">chmod 2775 /opt/myproject</code></pre><div class="para">
+ 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 -ld /opt/myproject</code>
+drwxrwsr-x. 3 root myproject 4096 Mar 3 18:31 /opt/myproject
+</pre></li><li class="step"><div class="para">
+ Add users to the <code class="systemitem">myproject</code> group:
+ </div><pre class="screen"><code class="command">usermod -aG myproject <em class="replaceable"><code>username</code></em></code></pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-users-tools-users-logout.html"><strong>Prev</strong>4.3.4. Enabling Automatic Logouts</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-Users_and_Groups-Resources.html"><strong>Next</strong>4.4. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-users-tools-password-aging.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-users-tools-password-aging.html
index 8e601c4..fceab46 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-users-tools-password-aging.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-users-tools-password-aging.html
@@ -6,11 +6,11 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-users-tools.html" title="4.3. Using Command Line Tools" /><link rel="prev" href="s2-users-tools-groups-add.html" title="4.3.2. Adding a New Group" /><link rel="next" href="s2-users-tools-users-logout.html" title="4.3.4. Enabling Automatic Logouts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-users-tools-groups-add.html"><strong>Prev</strong></a></l
i><li class="next"><a accesskey="n" href="s2-users-tools-users-logout.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-users-tools-password-aging"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.3. Enabling Password Aging</h3></div></div></div><a id="idm225454466512" class="indexterm"></a><a id="idm225454465072" class="indexterm"></a><a id="idm225456247616" class="indexterm"></a><a id="idm225456246688" class="indexterm"></a><a id="idm225456244960" class="indexterm"></a><div class="para">
- For security reasons, it is advisable to require users to change their passwords periodically. This can either 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> application, or by using the <code class="command">chage</code> command.
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-users-tools.html" title="4.3. Using Command Line Tools" /><link rel="prev" href="s2-users-tools-groups-add.html" title="4.3.2. Adding a New Group" /><link rel="next" href="s2-users-tools-users-logout.html" title="4.3.4. Enabling Automatic Logouts" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-users-tools-groups-add.html"><strong>Prev</strong></a></l
i><li class="next"><a accesskey="n" href="s2-users-tools-users-logout.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-users-tools-password-aging"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">4.3.3. Enabling Password Aging</h3></div></div></div><a id="idm261725827360" class="indexterm"></a><a id="idm261725825920" class="indexterm"></a><a id="idm261725824480" class="indexterm"></a><a id="idm261787098976" class="indexterm"></a><a id="idm261787097248" class="indexterm"></a><div class="para">
+ For security reasons, it is advisable to require users to change their passwords periodically. This can be done by using the <code class="command">chage</code> command.
</div><div class="important"><div class="admonition_header"><h2>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="ch-Managing_Users_and_Groups.html#s2-users-groups-shadow-utilities">Section 4.1.2, “Shadow Passwords”</a>.
- </div></div></div><a id="idm225458666896" class="indexterm"></a><div class="para">
+ </div></div></div><a id="idm261738900560" class="indexterm"></a><div class="para">
To configure password expiration for a user from a shell prompt, run the following command as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">chage</code> [<span class="optional"><em class="replaceable"><code>options</code></em></span>] <em class="replaceable"><code>username</code></em></pre><div class="para">
…where <em class="replaceable"><code>options</code></em> are command line options as described in <a class="xref" href="s2-users-tools-password-aging.html#table-chage-options">Table 4.4, “chage command line options”</a>. When the <code class="command">chage</code> command is followed directly by a username (that is, when no command line options are specified), it displays the current password aging values and allows you to change them interactively.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-using_RELP.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-using_RELP.html
new file mode 100644
index 0000000..ab732df
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-using_RELP.html
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.4.4. Using RELP</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-using_rsyslog_modules.html" title="17.4. Using Rsyslog Modules" /><link rel="prev" href="s2-enabling_encrypted_transport.html" title="17.4.3. Enabling Encrypted Transport" /><link rel="next" href="s1-interaction_of_rsyslog_and_journal.html" title="17.5. Interaction of Rsyslog and Journal" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-enabling_encryp
ted_transport.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-interaction_of_rsyslog_and_journal.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-using_RELP"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.4.4. Using RELP</h3></div></div></div><div class="para">
+ <span class="emphasis"><em>Reliable Event Logging Protocol</em></span> (RELP) is a networking protocol for data logging in computer networks. It is designed to provide reliable delivery of event messages, which makes it useful in environments where message loss is not acceptable.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-enabling_encrypted_transport.html"><strong>Prev</strong>17.4.3. Enabling Encrypted Transport</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-interaction_of_rsyslog_and_journal.html"><strong>Next</strong>17.5. Interaction of Rsyslog and Journal</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-using_the_new_configuration_format.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-using_the_new_configuration_format.html
new file mode 100644
index 0000000..6ea5721
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s2-using_the_new_configuration_format.html
@@ -0,0 +1,26 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>17.2.6. Using the New Configuration Format</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-basic_configuration_of_rsyslog.html" title="17.2. Basic Configuration of Rsyslog" /><link rel="prev" href="s2-log_rotation.html" title="17.2.5. Log Rotation" /><link rel="next" href="s2-Rulesets.html" title="17.2.7. Rulesets" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-log_rotation.html"><strong>Prev</strong></a></li><li class="next"><a accesskey=
"n" href="s2-Rulesets.html"><strong>Next</strong></a></li></ul><div class="section" id="s2-using_the_new_configuration_format"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">17.2.6. Using the New Configuration Format</h3></div></div></div><div class="para">
+ In <span class="application"><strong>rsyslog</strong></span> version 6, a new configuration syntax has been introduced. This new configuration format aims to be more powerful, more intuitive, and to prevent common mistakes by not permitting certain invalid constructs. The syntax enhancement is enabled by the new configuration processor that relies on RainerScript. The legacy format is still fully supported and it is used by default in the <code class="filename">/etc/rsyslog.conf</code> configuration file.
+ </div><div class="para">
+ RainerScript is a scripting language designed for processing network events and configuring event processors such as <span class="application"><strong>rsyslog</strong></span>. RainerScript was primarily used to define expression-based filters, see <a class="xref" href="s1-basic_configuration_of_rsyslog.html#ex-expression-based_filters">Example 17.3, “Expression-based Filters”</a>. The newest version of RainerScript implements the <code class="function">input()</code> and <code class="function">ruleset()</code> statements, which permit the <code class="filename">/etc/rsyslog.conf</code> configuration file to be written in the new style only.
+ </div><div class="para">
+ In the following examples you can compare the configuration written with legacy-style parameters:
+ </div><pre class="screen">
+$InputFileName /tmp/inputfile
+$InputFileTag tag1:
+$InputFileStateFile inputfile-state
+$InputRunFileMonitor
+</pre><div class="para">
+ and the same configuration with use of the new format statement:
+ </div><pre class="screen">
+input(type="imfile" file="/tmp/inputfile" tag="tag1:" statefile="inputfile-state")
+</pre><div class="para">
+ This significantly reduces the number of parameters used in configuration, improves readability, and also provides higher execution speed. For more information on RainerScript statements and parameters see <a class="xref" href="s1-log-files-additional-resources.html#brid-Log_Files-Resources-Online">the section called “Online Documentation”</a>.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-log_rotation.html"><strong>Prev</strong>17.2.5. Log Rotation</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-Rulesets.html"><strong>Next</strong>17.2.7. Rulesets</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s3-ftp-vsftpd-conf.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s3-ftp-vsftpd-conf.html
index 8760f5d..a8012ed 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s3-ftp-vsftpd-conf.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s3-ftp-vsftpd-conf.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-FTP.html" title="12.2. FTP" /><link rel="prev" href="s2-ftp-servers.html" title="12.2.2. FTP Servers" /><link rel="next" href="s2-ftp-vsftpd-start.html" title="12.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"><strong>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">12.2.3. Files Installed with <code class="command">vsftpd</code> </h3></div></div></div><a id="idm225459987232" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s1-FTP.html" title="12.2. FTP" /><link rel="prev" href="s2-ftp-servers.html" title="12.2.2. FTP Servers" /><link rel="next" href="s2-ftp-vsftpd-start.html" title="12.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"><strong>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">12.2.3. Files Installed with <code class="command">vsftpd</code> </h3></div></div></div><a id="idm261758175888" class="indexterm"></a><div class="para">
The <code class="filename">vsftpd</code> RPM installs the daemon (<code class="filename">/usr/sbin/vsftpd</code>), its configuration and related files, as well as <code class="systemitem">FTP</code> directories onto the system. The following lists the files and directories related to <code class="command">vsftpd</code> configuration:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="filename">/etc/rc.d/init.d/vsftpd</code> — The <span class="emphasis"><em>initialization script</em></span> (<em class="firstterm">initscript</em>) used by the <code class="command">systemctl</code> command to start, stop, or reload <code class="command">vsftpd</code>. See <a class="xref" href="s2-ftp-vsftpd-start.html">Section 12.2.4, “Starting and Stopping <code class="command">vsftpd</code> ”</a> for more information about using this script.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s5-vnc-viewer.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s5-vnc-viewer.html
index f3fb304..3722840 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s5-vnc-viewer.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s5-vnc-viewer.html
@@ -9,7 +9,7 @@
</script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-TigerVNC.html" title="Chapter 8. TigerVNC" /><link rel="prev" href="ch-TigerVNC.html" title="Chapter 8. TigerVNC" /><link rel="next" href="s6-connecting-vnc-viewer.html" title="8.2.2. Connecting to VNC Server" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-TigerVNC.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s6-conne
cting-vnc-viewer.html"><strong>Next</strong></a></li></ul><div class="section" id="s5-vnc-viewer"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.2. VNC Viewer</h2></div></div></div><div class="para">
<code class="systemitem">vncviewer</code> is the program which shows the shared graphical user interfaces and controls the server.
</div><div class="para">
- For operating the <code class="systemitem">vncviewer</code>, there is a pop-up menu containing entries which perform various actions such as switching in and out of full-screen mode or quitting the viewer. Alternatively, you can operate <code class="systemitem">vncviewer</code> through the terminal; there is a list of parameters <code class="systemitem">vncviewer</code> can be used with which you obtain by typing <code class="command">vncviewer -h</code> on the command line.
+ For operating the <code class="systemitem">vncviewer</code>, there is a pop-up menu containing entries which perform various actions such as switching in and out of full-screen mode or quitting the viewer. Alternatively, you can operate <code class="systemitem">vncviewer</code> through the terminal. Enter <code class="command">vncviewer -h</code> on the command line to list <code class="systemitem">vncviewer</code>'s parameters.
</div><div class="section" id="installing-vncviewer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.2.1. Installing VNC Viewer</h3></div></div></div><div class="para">
- To install the TigerVNC client, referred to as <span class="application"><strong>vncviewer</strong></span>, issue the following command as <code class="systemitem">root</code>: <pre class="synopsis"><code class="command"><code class="computeroutput">~]# </code><strong class="userinput"><code>yum install tigervnc</code></strong></code></pre>
+ To install the <span class="application"><strong>TigerVNC</strong></span> client, <code class="command">vncviewer</code>>, issue the following command as <code class="systemitem">root</code>: <pre class="synopsis"><code class="command"><code class="computeroutput">~]# </code><strong class="userinput"><code>yum install tigervnc</code></strong></code></pre>
</div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-TigerVNC.html"><strong>Prev</strong>Chapter 8. TigerVNC</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="s6-connecting-vnc-viewer.html"><strong>Next</strong>8.2.2. Connecting to VNC Server</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s6-connecting-vnc-viewer.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s6-connecting-vnc-viewer.html
index 04e51c5..bc3f1a1 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s6-connecting-vnc-viewer.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s6-connecting-vnc-viewer.html
@@ -6,9 +6,9 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s5-vnc-viewer.html" title="8.2. VNC Viewer" /><link rel="prev" href="s5-vnc-viewer.html" title="8.2. VNC Viewer" /><link rel="next" href="s1-using_ssh.html" title="8.2.3. Connecting to VNC Server using SSH" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s5-vnc-viewer.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-using_ssh.h
tml"><strong>Next</strong></a></li></ul><div class="section" id="s6-connecting-vnc-viewer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.2.2. Connecting to VNC Server</h3></div></div></div><div class="para">
- Once the VNC server is configured, you can connect to it from any VNC viewer. In order to do so, issue the <code class="command">vncviewer</code> command in the following format: <pre class="synopsis">vncviewer <em class="replaceable"><code>IP_address</code></em>:<em class="replaceable"><code>port_number</code></em></pre>
- </div><div class="example" id="connecting-to-vncserver"><h6>Example 8.1. One Client Connecting to vncserver</h6><div class="example-contents"><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="s5-vnc-viewer.html" title="8.2. VNC Viewer" /><link rel="prev" href="s5-vnc-viewer.html" title="8.2. VNC Viewer" /><link rel="next" href="s1-using_ssh.html" title="8.2.3. Connecting to VNC Server Using SSH" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s5-vnc-viewer.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="s1-using_ssh.h
tml"><strong>Next</strong></a></li></ul><div class="section" id="s6-connecting-vnc-viewer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">8.2.2. Connecting to VNC Server</h3></div></div></div><div class="para">
+ Once the VNC server is configured, you can connect to it from any VNC viewer. In order to do so, issue the <code class="command">vncviewer</code> command in the following format: <pre class="synopsis">vncviewer <em class="replaceable"><code>address</code></em>:<em class="replaceable"><code>port_number</code></em></pre> Where <em class="replaceable"><code>address</code></em> is an <code class="systemitem">IP</code> or host name.
+ </div><div class="example" id="connecting-to-vncserver"><h6>Example 8.1. One Client Connecting to VNC Server</h6><div class="example-contents"><div class="para">
With the <code class="systemitem">IP</code> address <code class="systemitem">192.168.0.4</code> and display number <span class="emphasis"><em>3</em></span> the command looks as follows:
</div><pre class="programlisting">
<code class="command"><code class="computeroutput">~]$ </code><strong class="userinput"><code>vncviewer 192.168.0.4:3</code></strong></code></pre></div></div><br class="example-break" /><div class="section" id="sec-Configuring_the_Firewall_for_VNC"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">8.2.2.1. Configuring the Firewall for VNC</h4></div></div></div><div class="para">
@@ -39,7 +39,7 @@ public (default, active)
rich rules:
rule family="ipv4" source address="192.168.122.116" service name="vnc-server" accept</pre>
</div></li></ol></div><div class="para">
- To open a specific port or range of ports make use of the <code class="option">--list-ports</code> option to the <code class="command">firewall-cmd</code> command Line tool. For example, VNC display <code class="literal">4</code> requires port <code class="literal">5904</code> to be opened for <code class="systemitem">TCP</code> traffic.
+ To open a specific port or range of ports make use of the <code class="option">--add-port</code> option to the <code class="command">firewall-cmd</code> command Line tool. For example, VNC display <code class="literal">4</code> requires port <code class="literal">5904</code> to be opened for <code class="systemitem">TCP</code> traffic.
</div><div class="procedure" id="proc-Opening-Ports_in_firewalld"><h6>Procedure 8.3. Opening Ports in firewalld</h6><ol class="1"><li class="step"><div class="para">
To open a port for <code class="systemitem">TCP</code> traffic in the public zone, issue a command as <code class="systemitem">root</code> as follows:
<pre class="screen">~]# <code class="command">firewall-cmd --zone=public --add-port=5904/tcp</code>
@@ -52,4 +52,4 @@ success</pre>
A port can be removed using the <code class="command">firewall-cmd --zone=<em class="replaceable"><code>zone</code></em> --remove-port=<em class="replaceable"><code>number/protocol</code></em></code> command.
</div><div class="para">
For more information on opening and closing ports in <code class="systemitem">firewalld</code>, see the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Security_Guide/">Red Hat Enterprise Linux 7 Security Guide</a>.
- </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s5-vnc-viewer.html"><strong>Prev</strong>8.2. VNC Viewer</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-using_ssh.html"><strong>Next</strong>8.2.3. Connecting to VNC Server using SSH</a></li></ul></body></html>
\ No newline at end of file
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s5-vnc-viewer.html"><strong>Prev</strong>8.2. VNC Viewer</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-using_ssh.html"><strong>Next</strong>8.2.3. Connecting to VNC Server Using SSH</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s9-additional-sources.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s9-additional-sources.html
index effccfe..dff9b4f 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s9-additional-sources.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/s9-additional-sources.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-TigerVNC.html" title="Chapter 8. TigerVNC" /><link rel="prev" href="s1-using_ssh.html" title="8.2.3. Connecting to VNC Server using SSH" /><link rel="next" href="part-Servers.html" title="Part IV. 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-using_ssh.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="part-Server
s.html"><strong>Next</strong></a></li></ul><div class="section" id="s9-additional-sources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.3. Additional Resources</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-TigerVNC.html" title="Chapter 8. TigerVNC" /><link rel="prev" href="s1-using_ssh.html" title="8.2.3. Connecting to VNC Server Using SSH" /><link rel="next" href="part-Servers.html" title="Part IV. 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-using_ssh.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="part-Server
s.html"><strong>Next</strong></a></li></ul><div class="section" id="s9-additional-sources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">8.3. Additional Resources</h2></div></div></div><div class="para">
For more information about TigerVNC, see the resources listed below.
</div><h3 id="brid-TigerVNC-Resources-Installed">Installed Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="filename">vncserver(1)</code> — The <acronym class="acronym">VNC</acronym> server manual pages.
@@ -14,4 +14,4 @@
<code class="filename">vncviewer(1)</code> — The <acronym class="acronym">VNC</acronym> viewer manual pages.
</div></li><li class="listitem"><div class="para">
<code class="filename">vncpasswd(1)</code> — The <acronym class="acronym">VNC</acronym> password manual pages.
- </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-using_ssh.html"><strong>Prev</strong>8.2.3. Connecting to VNC Server using SSH</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 IV. Servers</a></li></ul></body></html>
\ No newline at end of file
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-using_ssh.html"><strong>Prev</strong>8.2.3. Connecting to VNC Server Using SSH</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 IV. Servers</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Adding_Other_Printer.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Adding_Other_Printer.html
index 7b4a885..6317492 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Adding_Other_Printer.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Adding_Other_Printer.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Printer_Configuration.html" title="12.3. Printer Configuration" /><link rel="prev" href="sec-Setting_Printer.html" title="12.3.2. Starting Printer Setup" /><link rel="next" href="s1-printing-jetdirect-printer.html" title="12.3.4. Adding an AppSocket/HP JetDirect printer" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Setting_Printer.html"><strong>P
rev</strong></a></li><li class="next"><a accesskey="n" href="s1-printing-jetdirect-printer.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Adding_Other_Printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.3. Adding a Local Printer</h3></div></div></div><a id="idm225476183344" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Printer_Configuration.html" title="12.3. Printer Configuration" /><link rel="prev" href="sec-Setting_Printer.html" title="12.3.2. Starting Printer Setup" /><link rel="next" href="s1-printing-jetdirect-printer.html" title="12.3.4. Adding an AppSocket/HP JetDirect printer" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Setting_Printer.html"><strong>P
rev</strong></a></li><li class="next"><a accesskey="n" href="s1-printing-jetdirect-printer.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Adding_Other_Printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.3. Adding a Local Printer</h3></div></div></div><a id="idm261726639296" class="indexterm"></a><div class="para">
Follow this procedure to add a local printer connected with other than a serial port:
</div><div class="procedure" id="proc-Adding_Other_Printer"><ol class="1"><li class="step"><div class="para">
Open the <code class="systemitem">Add a New Printer</code> dialog (refer to <a class="xref" href="sec-Setting_Printer.html">Section 12.3.2, “Starting Printer Setup”</a>).
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Adding_a_new_Entry.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Adding_a_new_Entry.html
new file mode 100644
index 0000000..ad6b0f5
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Adding_a_new_Entry.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.2.3. Adding a new Entry</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Customizing_GRUB_2_Menu.html" title="20.2. Customizing GRUB 2 Menu" /><link rel="prev" href="sec-Editing_an_Entry.html" title="20.2.2. Editing an Entry" /><link rel="next" href="sec-Using_only_a_Custom_Menu.html" title="20.2.4. Creating a Custom Menu" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Editing_an_Entry.html"><strong>Prev</strong></a></l
i><li class="next"><a accesskey="n" href="sec-Using_only_a_Custom_Menu.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Adding_a_new_Entry"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.2.3. Adding a new Entry</h3></div></div></div><div class="para">
+ When executing the <code class="command">grub2-mkconfig</code> command, GRUB 2 searches for Linux kernels and other operating systems based on the files located in the <code class="filename">/etc/grub.d/</code> directory. The <code class="filename">/etc/grub.d/10_linux</code> script searches for installed Linux kernels on the same partition. The <code class="filename">/etc/grub.d/30_os-prober</code> script searches for other operating systems. Menu entries are also automatically added to the boot menu when updating the kernel.
+ </div><div class="para">
+ The <code class="filename">40_custom</code> file located in the <code class="filename">/etc/grub.d/</code> directory is a template for custom entries and looks as follows:
+ </div><pre class="programlisting"><span class="perl_Comment">#!/bin/sh</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span><span class="perl_Reserved">exec</span> <span class="perl_BString">tail</span> -n +3 <span class="perl_Others">$0</span>
+<span class="perl_Comment"># This file provides an easy way to add custom menu entries. Simply type the</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span><span class="perl_Comment"># menu entries you want to add after this comment. Be careful not to change</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span><span class="perl_Comment"># the 'exec tail' line above.</span></pre><div class="para">
+ This file can be edited or copied. Note that as a minimum, a valid menu entry must include at least the following:
+ </div><pre class="screen"><span class="strong strong"><strong>menuentry</strong></span> "<Title>"<span class="strong strong"><strong>{</strong></span>
+<Data>
+<span class="strong strong"><strong>}</strong></span></pre></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Editing_an_Entry.html"><strong>Prev</strong>20.2.2. Editing an Entry</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_only_a_Custom_Menu.html"><strong>Next</strong>20.2.4. Creating a Custom Menu</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Additional_Resources.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Additional_Resources.html
index c290ce8..8f1ec85 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Additional_Resources.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Additional_Resources.html
@@ -6,6 +6,6 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-yum.html" title="Chapter 5. Yum" /><link rel="prev" href="sec-Plugin_Descriptions.html" title="5.4.3. Plug-in Descriptions" /><link rel="next" href="part-Infrastructure_Services.html" title="Part III. 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="sec-Plugin_Descriptions.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="sec-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.5. Additional Resources</h2></div></div></div><a id="idm225476094272" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a href="http://yum.baseurl.org/wiki/Guides">http://yum.baseurl.org/wiki/Guides</a> </span></dt><dd><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-yum.html" title="Chapter 5. Yum" /><link rel="prev" href="sec-Plugin_Descriptions.html" title="5.4.3. Plug-in Descriptions" /><link rel="next" href="part-Infrastructure_Services.html" title="Part III. 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="sec-Plugin_Descriptions.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="sec-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">5.5. Additional Resources</h2></div></div></div><a id="idm261743197968" class="indexterm"></a><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a href="http://yum.baseurl.org/wiki/Guides">http://yum.baseurl.org/wiki/Guides</a> </span></dt><dd><div class="para">
The <code class="literal">Yum Guides</code> section of the Yum 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>5.4.3. Plug-in 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="part-Infrastructure_Services.html"><strong>Next</strong>Part III. Infrastructure Services</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Booting_to_Emergency_Mode.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Booting_to_Emergency_Mode.html
new file mode 100644
index 0000000..ae15f68
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Booting_to_Emergency_Mode.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.6.2. Booting to Emergency Mode</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Terminal_Menu_Editing_During_Boot.html" title="20.6. Terminal Menu Editing During Boot" /><link rel="prev" href="sec-Terminal_Menu_Editing_During_Boot.html" title="20.6. Terminal Menu Editing During Boot" /><link rel="next" href="sec-Changing_and_Resetting_the_Root_Password.html" title="20.6.3. Changing and Resetting the Root Password" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="pr
evious"><a accesskey="p" href="sec-Terminal_Menu_Editing_During_Boot.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Changing_and_Resetting_the_Root_Password.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Booting_to_Emergency_Mode"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.6.2. Booting to Emergency Mode</h3></div></div></div><div class="para">
+ Emergency mode provides the most minimal environment possible and allows you to repair your system even in situations when the system is unable to enter rescue mode. In emergency mode, the system mounts the <code class="systemitem">root</code> file system only for reading, does not attempt to mount any other local file systems, does not activate network interfaces, and only starts few essential services. In Fedora, emergency mode requires the <code class="systemitem">root</code> password.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To enter emergency mode, on the GRUB 2 boot screen, press the <span class="keycap"><strong>e</strong></span> key for edit.
+ </div></li><li class="step"><div class="para">
+ Add the following parameter at the end of the <code class="literal">linux</code> line on 64-Bit IBM Power Series, the <code class="literal">linux16</code> line on x86-64 BIOS-based systems, or the <code class="literal">linuxefi</code> line on UEFI systems:
+ </div><pre class="screen">systemd.unit=emergency.target</pre><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>a</strong></span> and <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>e</strong></span> to jump to the start and end of the line, respectively. On some systems, <span class="keycap"><strong>Home</strong></span> and <span class="keycap"><strong>End</strong></span> might also work.
+ </div><div class="para">
+ Note that equivalent parameters, <em class="parameter"><code>emergency</code></em> and <em class="parameter"><code>-b</code></em>, can be passed to the kernel as well.
+ </div></li><li class="step"><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>x</strong></span> to boot the system with the parameter.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Terminal_Menu_Editing_During_Boot.html"><strong>Prev</strong>20.6. Terminal Menu Editing During Boot</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-Changing_and_Resetting_the_Root_Password.html"><strong>Next</strong>20.6.3. Changing and Resetting the Root Password</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Changing_and_Resetting_the_Root_Password.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Changing_and_Resetting_the_Root_Password.html
new file mode 100644
index 0000000..9a6b57b
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Changing_and_Resetting_the_Root_Password.html
@@ -0,0 +1,107 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.6.3. Changing and Resetting the Root Password</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Terminal_Menu_Editing_During_Boot.html" title="20.6. Terminal Menu Editing During Boot" /><link rel="prev" href="sec-Booting_to_Emergency_Mode.html" title="20.6.2. Booting to Emergency Mode" /><link rel="next" href="sec-UEFI_Secure_Boot.html" title="20.7. UEFI Secure Boot" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Booting_to_Emergency_Mode.htm
l"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-UEFI_Secure_Boot.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Changing_and_Resetting_the_Root_Password"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.6.3. Changing and Resetting the Root Password</h3></div></div></div><div class="para">
+ Setting up the <code class="systemitem">root</code> password is a mandatory part of the Fedora installation. If you forget or lose the <code class="systemitem">root</code> password it is possible to reset it, however users who are members of the wheel group can change the <code class="systemitem">root</code> password as follows:
+<pre class="screen">~]$ <code class="command">sudo passwd root</code></pre>
+
+ </div><div class="para">
+ Note that in GRUB 2, resetting the password is no longer performed in single-user mode as it was in GRUB included in Fedora 15 and Red Hat Enterprise Linux 6. The <code class="systemitem">root</code> password is now required to operate in <code class="literal">single-user</code> mode as well as in <code class="literal">emergency</code> mode.
+ </div><div class="para">
+ Two procedures for resetting the <code class="systemitem">root</code> password are shown here:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a class="xref" href="sec-Changing_and_Resetting_the_Root_Password.html#proc-Resetting_the_Root_Password_Using_an_Installation_Disk">Procedure 20.1, “Resetting the Root Password Using an Installation Disk”</a> takes you to a shell prompt, without having to edit the grub menu. It is the shorter of the two procedures and it is also the recommended method. You can use a server boot disk or a netinstall installation disk.
+ </div></li><li class="listitem"><div class="para">
+ <a class="xref" href="sec-Changing_and_Resetting_the_Root_Password.html#proc-Resetting_the_Root_Password_Using_rd.break">Procedure 20.2, “Resetting the Root Password Using rd.break”</a> makes use of <code class="command">rd.break</code> to interrupt the boot process before control is passed from <code class="systemitem">initramfs</code> to <code class="systemitem">systemd</code>. The disadvantage of this method is that it requires more steps, includes having to edit the GRUB menu, and involves choosing between a possibly time consuming SELinux file relabel or changing the SELinux enforcing mode and then restoring the SELinux security context for <code class="filename">/etc/shadow/</code> when the boot completes.
+ </div></li></ul></div><div class="procedure" id="proc-Resetting_the_Root_Password_Using_an_Installation_Disk"><h6>Procedure 20.1. Resetting the Root Password Using an Installation Disk</h6><ol class="1"><li class="step"><div class="para">
+ Start the system and when BIOS information is displayed, select the option for a boot menu and select to boot from the installation disk.
+ </div></li><li class="step"><div class="para">
+ Choose <span class="guimenuitem"><strong>Troubleshooting</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Choose <span class="guimenuitem"><strong>Rescue a Fedora-Server System</strong></span>.
+ </div></li><li class="step"><div class="para">
+ Choose <span class="guimenuitem"><strong>Continue</strong></span> which is the default option. At this point you will be promoted for a passphrase if an encrypted file system is found.
+ </div></li><li class="step"><div class="para">
+ Press <span class="keycap"><strong>OK</strong></span> to acknowledge the information displayed until the shell prompt appears.
+ </div></li><li class="step"><div class="para">
+ Change the file system <code class="systemitem">root</code> as follows:
+<pre class="screen">sh-4.2# <code class="command">chroot /mnt/sysimage</code></pre>
+
+ </div></li><li class="step"><div class="para">
+ Enter the <code class="command">passwd</code> command and follow the instructions displayed on the command line to change the <code class="systemitem">root</code> password.
+ </div></li><li class="step"><div class="para">
+ Remove the <code class="filename">autorelable</code> file to prevent a time consuming SELinux relabel of the disk:
+<pre class="screen">sh-4.2# <code class="command">rm -f /.autorelabel</code></pre>
+
+ </div></li><li class="step"><div class="para">
+ Enter the <code class="command">exit</code> command to exit the <code class="command">chroot</code> environment.
+ </div></li><li class="step"><div class="para">
+ Enter the <code class="command">exit</code> command again to resume the initialization and finish the system boot.
+ </div></li></ol></div><div class="procedure" id="proc-Resetting_the_Root_Password_Using_rd.break"><h6>Procedure 20.2. Resetting the Root Password Using rd.break</h6><ol class="1"><li class="step"><div class="para">
+ Start the system and, on the GRUB 2 boot screen, press the <span class="keycap"><strong>e</strong></span> key for edit.
+ </div></li><li class="step"><div class="para">
+ Remove the <code class="option">rhgb</code> and <code class="option">quiet</code> parameters from the end, or near the end, of the <code class="literal">linux16</code> line, or <code class="literal">linuxefi</code> on UEFI systems.
+ </div><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>a</strong></span> and <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>e</strong></span> to jump to the start and end of the line, respectively. On some systems, <span class="keycap"><strong>Home</strong></span> and <span class="keycap"><strong>End</strong></span> might also work.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ The <code class="option">rhgb</code> and <code class="option">quiet</code> parameters must be removed in order to enable system messages.
+ </div></div></div></li><li class="step"><div class="para">
+ Add the following parameters at the end of the <code class="literal">linux</code> line on 64-Bit IBM Power Series, the <code class="literal">linux16</code> line on x86-64 BIOS-based systems, or the <code class="literal">linuxefi</code> line on UEFI systems:
+<pre class="screen">rd.break enforcing=0</pre>
+ Adding the <code class="option">enforcing=0</code> option enables omitting the time consuming SELinux relabeling process.
+ </div><div class="para">
+ The <code class="systemitem">initramfs</code> will stop before passing control to the Linux <span class="package">kernel</span>, enabling you to work with the <code class="systemitem">root</code> file system.
+ </div><div class="para">
+ Note that the <code class="systemitem">initramfs</code> prompt will appear on the last console specified on the Linux line.
+ </div></li><li class="step"><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>x</strong></span> to boot the system with the changed parameters.
+ </div><div class="para">
+ With an encrypted file system, a password is required at this point. However the password prompt might not appear as it is obscured by logging messages. You can press the <span class="keycap"><strong>Backspace</strong></span> key to see the prompt. Release the key and enter the password for the encrypted file system, while ignoring the logging messages.
+ </div><div class="para">
+ The <code class="systemitem">initramfs</code> <code class="systemitem">switch_root</code> prompt appears.
+ </div></li><li class="step"><div class="para">
+ The file system is mounted read-only on <code class="filename">/sysroot/</code>. You will not be allowed to change the password if the file system is not writable.
+ </div><div class="para">
+ Remount the file system as writable:
+<pre class="screen">switch_root:/# <code class="command">mount -o remount,rw /sysroot</code></pre>
+
+ </div></li><li class="step"><div class="para">
+ The file system is remounted with write enabled.
+ </div><div class="para">
+ Change the file system's <code class="systemitem">root</code> as follows:
+<pre class="screen">switch_root:/# <code class="command">chroot /sysroot</code></pre>
+ The prompt changes to <code class="computeroutput">sh-4.2#</code>.
+ </div></li><li class="step"><div class="para">
+ Enter the <code class="command">passwd</code> command and follow the instructions displayed on the command line to change the <code class="systemitem">root</code> password.
+ </div><div class="para">
+ Note that if the system is not writable, the <span class="application"><strong>passwd</strong></span> tool fails with the following error:
+ </div><pre class="screen">Authentication token manipulation error</pre></li><li class="step"><div class="para">
+ Updating the password file results in a file with the incorrect SELinux security context. To relabel all files on next system boot, enter the following command:
+<pre class="screen">sh-4.2# <code class="command">touch /.autorelabel</code></pre>
+ Alternatively, to save the time it takes to relabel a large disk, you can omit this step provided you included the <code class="option">enforcing=0</code> option in step 3.
+ </div></li><li class="step"><div class="para">
+ Remount the file system as read only:
+<pre class="screen">sh-4.2# <code class="command">mount -o remount,ro /</code></pre>
+
+ </div></li><li class="step"><div class="para">
+ Enter the <code class="command">exit</code> command to exit the <code class="command">chroot</code> environment.
+ </div></li><li class="step"><div class="para">
+ Enter the <code class="command">exit</code> command again to resume the initialization and finish the system boot.
+ </div><div class="para">
+ With an encrypted file system, a pass word or phrase is required at this point. However the password prompt might not appear as it is obscured by logging messages. You can press and hold the <span class="keycap"><strong>Backspace</strong></span> key to see the prompt. Release the key and enter the password for the encrypted file system, while ignoring the logging messages.
+ </div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that the SELinux relabeling process can take a long time. A system reboot will occur automatically when the process is complete.
+ </div></div></div></li><li class="step"><div class="para">
+ If you added the <code class="option">enforcing=0</code> option in step 3 and omitted the <code class="command">touch /.autorelabel</code> command in step 8, enter the following command to restore the <code class="filename">/etc/shadow</code> file's SELinux security context:
+<pre class="screen">~]# <code class="command">restorcon /etc/shadow</code></pre>
+ Enter the following commands to turn SELinux policy enforcement back on and verify that it is on:
+<pre class="screen">~]# <code class="command">setenforce 1</code>
+~]# <code class="command">getenforce</code>
+Enforcing</pre>
+
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Booting_to_Emergency_Mode.html"><strong>Prev</strong>20.6.2. Booting to Emergency Mode</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-UEFI_Secure_Boot.html"><strong>Next</strong>20.7. UEFI Secure Boot</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Configuring_Yum_and_Yum_Repositories.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Configuring_Yum_and_Yum_Repositories.html
index 6dbeda1..0c32de3 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Configuring_Yum_and_Yum_Repositories.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Configuring_Yum_and_Yum_Repositories.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-yum.html" title="Chapter 5. Yum" /><link rel="prev" href="sec-Yum-Transaction_History.html" title="5.2.6. Working with Transaction History" /><link rel="next" href="sec-Setting_repository_Options.html" title="5.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-Yum-Transaction_History.html"><strong>Prev</strong></a></
li><li class="next"><a accesskey="n" href="sec-Setting_repository_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">5.3. Configuring Yum and Yum Repositories</h2></div></div></div><a id="idm225475982320" class="indexterm"></a><a id="idm225500903392" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-yum.html" title="Chapter 5. Yum" /><link rel="prev" href="sec-Yum-Transaction_History.html" title="5.2.6. Working with Transaction History" /><link rel="next" href="sec-Setting_repository_Options.html" title="5.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-Yum-Transaction_History.html"><strong>Prev</strong></a></
li><li class="next"><a accesskey="n" href="sec-Setting_repository_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">5.3. Configuring Yum and Yum Repositories</h2></div></div></div><a id="idm261748939712" class="indexterm"></a><a id="idm261748938304" class="indexterm"></a><div class="para">
The configuration file for <code class="command">yum</code> and related utilities is located at <code class="filename">/etc/yum.conf</code>. This file contains one mandatory <code class="literal">[main]</code> section, which allows you to set Yum options that have global effect, and may also contain one or more <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> sections, which allow you to set repository-specific options. However, 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. The values you define in the <code class="literal">[main]</code> section of the <code class="filename">/etc/yum.conf</code> file may override values set in individual <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> sections.
</div><div class="para">
This section shows you how to:
@@ -20,7 +20,7 @@
add, enable, and disable Yum repositories on the command line; and,
</div></li><li class="listitem"><div class="para">
set up your own custom Yum repository.
- </div></li></ul></div><div class="section" id="sec-Setting_main_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.3.1. Setting [main] Options</h3></div></div></div><a id="idm225477076464" class="indexterm"></a><div class="para">
+ </div></li></ul></div><div class="section" id="sec-Setting_main_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.3.1. Setting [main] Options</h3></div></div></div><a id="idm261740221904" 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, and while some of the key-value pairs in this section affect how <code class="command">yum</code> operates, others affect how Yum treats repositories. You can add many additional options under the <code class="literal">[main]</code> section heading in <code class="filename">/etc/yum.conf</code>.
</div><div class="para">
A sample <code class="filename">/etc/yum.conf</code> configuration file can look like this:
@@ -69,7 +69,7 @@ installonly_limit=3
</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="option">gpgcheck=<em class="replaceable"><code>value</code></em></code> for individual repositories instead; that is, you can enable GPG-checking on one repository while disabling it on another. Setting <code class="option">gpgcheck=<em class="replaceable"><code>value</code></em></code> for an individual repository in its corresponding <code class="filename">.repo</code> file overrides the default if it is present in <code class="filename">/etc/yum.conf</code>.
</div><div class="para">
- For more information on GPG signature-checking, refer to <a class="xref" href="s1-check-rpm-sig.html">Section A.3, “Checking a Package's Signature”</a>.
+ For more information on GPG signature-checking, refer to <a class="xref" href="s1-check-rpm-sig.html">Section A.3.2, “Checking Package Signatures”</a>.
</div></dd><dt class="varlistentry"><span class="term"><code class="option">groupremove_leaf_only</code>=<em class="replaceable"><code>value</code></em></span></dt><dd><div class="para">
…where <em class="replaceable"><code>value</code></em> is one of:
</div><div class="para">
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Configuring_timemaster_Options.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Configuring_timemaster_Options.html
new file mode 100644
index 0000000..ba809f9
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Configuring_timemaster_Options.html
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.9.3. Configuring timemaster Options</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html" title="15.9. Synchronize to PTP or NTP Time Using timemaster" /><link rel="prev" href="sec-Understanding_the_timemaster_Configuration_File.html" title="15.9.2. Understanding the timemaster Configuration File" /><link rel="next" href="sec-Improving_Accuracy.html" title="15.10. Improving Accuracy" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav">
<li class="previous"><a accesskey="p" href="sec-Understanding_the_timemaster_Configuration_File.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Improving_Accuracy.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Configuring_timemaster_Options"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.9.3. Configuring timemaster Options</h3></div></div></div><div class="procedure" id="proc-Editing_the_timemaster_Configuration_File"><h6>Procedure 15.1. Editing the timemaster Configuration File</h6><ol class="1"><li class="step"><div class="para">
+ To change the default configuration, open the <code class="filename">/etc/timemaster.conf</code> file for editing as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">vi /etc/timemaster.conf</code></pre>
+ </div></li><li class="step"><div class="para">
+ For each <code class="systemitem">NTP</code> server you want to control using <span class="application"><strong>timemaster</strong></span>, create <code class="computeroutput">[ntp_server <em class="replaceable"><code>address</code></em>]</code> sections . Note that the short polling values in the example section are not suitable for a public server, see <a class="xref" href="ch-Configuring_NTP_Using_ntpd.html">Chapter 14, <em>Configuring NTP Using ntpd</em></a> for an explanation of suitable <code class="option">minpoll</code> and <code class="option">maxpoll</code> values.
+ </div></li><li class="step"><div class="para">
+ To add interfaces that should be used in a domain, edit the <code class="computeroutput">#[ptp_domain 0]</code> section and add the interfaces. Create additional domains as required. For example:
+<pre class="screen">[ptp_domain 0]
+ interfaces eth0
+
+ [ptp_domain 1]
+ interfaces eth1</pre>
+ </div></li><li class="step"><div class="para">
+ If required to use <code class="systemitem">ntpd</code> as the <code class="systemitem">NTP</code> daemon on this system, change the default entry in the <code class="computeroutput">[timemaster]</code> section from <code class="systemitem">chronyd</code> to <code class="systemitem">ntpd</code>. See <a class="xref" href="ch-Configuring_NTP_Using_the_chrony_Suite.html">Chapter 13, <em>Configuring NTP Using the chrony Suite</em></a> for information on the differences between ntpd and chronyd.
+ </div></li><li class="step"><div class="para">
+ If using <code class="systemitem">chronyd</code> as the <code class="systemitem">NTP</code> server on this system, add any additional options below the default <code class="option">include /etc/chrony.conf</code> entry in the <code class="computeroutput">[chrony.conf]</code> section. Edit the default <code class="option">include</code> entry if the path to <code class="filename">/etc/chrony.conf</code> is known to have changed.
+ </div></li><li class="step"><div class="para">
+ If using <code class="systemitem">ntpd</code> as the <code class="systemitem">NTP</code> server on this system, add any additional options below the default <code class="option">include /etc/ntp.conf</code> entry in the <code class="computeroutput">[ntp.conf]</code> section. Edit the default <code class="option">include</code> entry if the path to <code class="filename">/etc/ntp.conf</code> is known to have changed.
+ </div></li><li class="step"><div class="para">
+ In the <code class="computeroutput">[ptp4l.conf]</code> section, add any options to be copied to the configuration file generated for <span class="application"><strong>ptp4l</strong></span>. This chapter documents common options and more information is available in the <code class="filename">ptp4l(8)</code> manual page.
+ </div></li><li class="step"><div class="para">
+ In the <code class="computeroutput">[chronyd]</code> section, add any command line options to be passed to <code class="systemitem">chronyd</code> when called by <span class="application"><strong>timemaster</strong></span>. See <a class="xref" href="ch-Configuring_NTP_Using_the_chrony_Suite.html">Chapter 13, <em>Configuring NTP Using the chrony Suite</em></a> for information on using <code class="systemitem">chronyd</code>.
+ </div></li><li class="step"><div class="para">
+ In the <code class="computeroutput">[ntpd]</code> section, add any command line options to be passed to <code class="systemitem">ntpd</code> when called by <span class="application"><strong>timemaster</strong></span>. See <a class="xref" href="ch-Configuring_NTP_Using_ntpd.html">Chapter 14, <em>Configuring NTP Using ntpd</em></a> for information on using <code class="systemitem">ntpd</code>.
+ </div></li><li class="step"><div class="para">
+ In the <code class="computeroutput">[phc2sys]</code> section, add any command line options to be passed to <span class="application"><strong>phc2sys</strong></span> when called by <span class="application"><strong>timemaster</strong></span>. This chapter documents common options and more information is available in the <code class="filename">phy2sys(8)</code> manual page.
+ </div></li><li class="step"><div class="para">
+ In the <code class="computeroutput">[ptp4l]</code> section, add any command line options to be passed to <span class="application"><strong>ptp4l</strong></span> when called by <span class="application"><strong>timemaster</strong></span>. This chapter documents common options and more information is available in the <code class="filename">ptp4l(8)</code> manual page.
+ </div></li><li class="step"><div class="para">
+ Save the configuration file and restart <span class="application"><strong>timemaster</strong></span> by issuing the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl restart timemaster</code></pre>
+
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Understanding_the_timemaster_Configuration_File.html"><strong>Prev</strong>15.9.2. Understanding the timemaster Configuratio...</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-Improving_Accuracy.html"><strong>Next</strong>15.10. Improving Accuracy</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Creating_a_Yum_Repository.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Creating_a_Yum_Repository.html
index de4e4b4..89ef5b6 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Creating_a_Yum_Repository.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Creating_a_Yum_Repository.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="5.3. Configuring Yum and Yum Repositories" /><link rel="prev" href="sec-Managing_Yum_Repositories.html" title="5.3.5. Adding, Enabling, and Disabling a Yum Repository" /><link rel="next" href="sec-Yum_Plugins.html" title="5.4. Yum Plug-ins" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Managing_Yum
_Repositories.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">5.3.6. Creating a Yum Repository</h3></div></div></div><a id="idm225475362160" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="5.3. Configuring Yum and Yum Repositories" /><link rel="prev" href="sec-Managing_Yum_Repositories.html" title="5.3.5. Adding, Enabling, and Disabling a Yum Repository" /><link rel="next" href="sec-Yum_Plugins.html" title="5.4. Yum Plug-ins" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Managing_Yum
_Repositories.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">5.3.6. Creating a Yum Repository</h3></div></div></div><a id="idm261717066304" class="indexterm"></a><div class="para">
To set up a Yum 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:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Customizing_GRUB_2_Menu.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Customizing_GRUB_2_Menu.html
new file mode 100644
index 0000000..487e166
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Customizing_GRUB_2_Menu.html
@@ -0,0 +1,57 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.2. Customizing GRUB 2 Menu</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="Chapter 20. Working with the GRUB 2 Boot Loader" /><link rel="prev" href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="Chapter 20. Working with the GRUB 2 Boot Loader" /><link rel="next" href="sec-Editing_an_Entry.html" title="20.2.2. Editing an Entry" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" hre
f="ch-Working_with_the_GRUB_2_Boot_Loader.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Editing_an_Entry.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Customizing_GRUB_2_Menu"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.2. Customizing GRUB 2 Menu</h2></div></div></div><div class="para">
+ GRUB 2 scripts search the user's computer and build a boot menu based on what operating systems the scripts find. To reflect the latest system boot options, the boot menu is rebuilt automatically when the kernel is updated or a new kernel is added.
+ </div><div class="para">
+ However, users may want to build a menu containing specific entries or to have the entries in a specific order. GRUB 2 allows basic customization of the boot menu to give users control of what actually appears on the screen.
+ </div><div class="para">
+ GRUB 2 uses a series of scripts to build the menu; these are located in the <code class="filename">/etc/grub.d/</code> directory. The following files are included:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">00_header</code>, which loads GRUB 2 settings from the <code class="filename">/etc/default/grub</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">01_users</code>, which is created only when a boot loader password is assigned in a <span class="application"><strong>kickstart</strong></span> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">10_linux</code>, which locates kernels in the default partition of Fedora.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">30_os-prober</code>, which builds entries for operating systems found on other partitions.
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">40_custom</code>, a template, which can be used to create additional menu entries.
+ </div></li></ul></div><div class="para">
+ Scripts from the <code class="filename">/etc/grub.d/</code> directory are read in alphabetical order and can be therefore renamed to change the boot order of specific menu entries.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ With the <code class="option">GRUB_TIMEOUT</code> key set to <code class="literal">0</code> in the <code class="filename">/etc/default/grub</code> file, GRUB 2 does not display the list of bootable kernels when the system starts up. In order to display this list when booting, press and hold any alphanumeric key when the BIOS information is displayed; GRUB 2 will present you with the GRUB menu.
+ </div></div></div><div class="section" id="sec-Changing_the_Default_Boot_Entry"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.2.1. Changing the Default Boot Entry</h3></div></div></div><div class="para">
+ By default, the key for the <code class="literal">GRUB_DEFAULT</code> directive in the <code class="filename">/etc/default/grub</code> file is the word <code class="literal">saved</code>. This instructs GRUB 2 to load the kernel specified by the <code class="option">saved_entry</code> directive in the GRUB 2 environment file, located at <code class="filename">/boot/grub2/grubenv</code>. You can set another GRUB record to be the default, using the <code class="command">grub2-set-default</code> command, which will update the GRUB 2 environment file.
+ </div><div class="para">
+ By default, the <code class="option">saved_entry</code> value is set to the name of latest installed kernel of package type <span class="package">kernel</span>. This is defined in <code class="filename">/etc/sysconfig/kernel</code> by the <code class="literal">UPDATEDEFAULT</code> and <code class="literal">DEFAULTKERNEL</code> directives. The file can be viewed by the <code class="systemitem">root</code> user as follows:
+<pre class="screen">~]# <code class="command">cat /etc/sysconfig/kernel</code>
+# UPDATEDEFAULT specifies if new-kernel-pkg should make
+# new kernels the default
+UPDATEDEFAULT=yes
+
+# DEFAULTKERNEL specifies the default kernel package type
+DEFAULTKERNEL=kernel-core</pre>
+ The <code class="literal">DEFAULTKERNEL</code> directive specifies what package type will be used as the default. Installing a package of type <span class="package">kernel-debug</span> will not change the default kernel while the <code class="literal">DEFAULTKERNEL</code> is set to package type <span class="package">kernel</span>.
+ </div><div class="para">
+ GRUB 2 supports using a numeric value as the key for the <code class="option">saved_entry</code> directive to change the default order in which the operating systems are loaded. To specify which operating system should be loaded first, pass its number to the <code class="command">grub2-set-default</code> command. For example:
+ </div><pre class="screen">~]# <code class="command">grub2-set-default</code> <code class="literal">2</code></pre><div class="para">
+ Note that the position of a menu entry in the list is denoted by a number starting with zero; therefore, in the example above, the third entry will be loaded. This value will be overwritten by the name of the next kernel to be installed.
+ </div><div class="para">
+ To force a system to always use a particular menu entry, use the menu entry name as the key to the <code class="literal">GRUB_DEFAULT</code> directive in the <code class="filename">/etc/default/grub</code> file. To list the available menu entries, run the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">awk -F\' '$1=="menuentry " {print $2}' /etc/grub2.cfg</code></pre>
+ Changes to <code class="filename">/etc/default/grub</code> require rebuilding the <code class="filename">grub.cfg</code> file as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div class="para">
+ On UEFI-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="ch-Working_with_the_GRUB_2_Boot_Loader.html"><strong>Prev</strong>Chapter 20. Working with the GRUB 2 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-Editing_an_Entry.html"><strong>Next</strong>20.2.2. Editing an Entry</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Displaying_Information_About_a_Module.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Displaying_Information_About_a_Module.html
index 86db599..cca430f 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Displaying_Information_About_a_Module.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Displaying_Information_About_a_Module.html
@@ -1,33 +1,33 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.2. Displaying Information About a Module</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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"><strong>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">21.2. Displaying Information About a Module</h2></div></div></div><a id="idm225446720256" class="indexterm"></a><a id="idm225446718336" class="indexterm"></a><a id="idm225455617232" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="prev" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="next" href="sec-Loading_a_Module.html" title="22.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"><strong>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">22.2. Displaying Information About a Module</h2></div></div></div><a id="idm261745722224" class="indexterm"></a><a id="idm261787980832" class="indexterm"></a><a id="idm261787978752" class="indexterm"></a><div class="para">
You can display detailed information about a kernel module by running the <code class="command">modinfo <em class="replaceable"><code>module_name</code></em></code> command.
</div><div class="note" id="note-Module_names_do_not_end_in_.ko"><div class="admonition_header"><h2>Module names do not end in .ko</h2></div><div class="admonition"><div class="para">
When entering the name of a kernel module as an argument to one of the <span class="application"><strong>kmod</strong></span> utilities, do not append a <code class="filename">.ko</code> extension to the end of the name. Kernel module names do not have extensions; their corresponding files do.
- </div></div></div><div class="example" id="ex-Listing_information_about_a_kernel_module_with_lsmod"><h6>Example 21.1. Listing information about a kernel module with lsmod</h6><div class="example-contents"><div class="para">
+ </div></div></div><div class="example" id="ex-Listing_information_about_a_kernel_module_with_lsmod"><h6>Example 22.1. Listing information about a kernel module with lsmod</h6><div class="example-contents"><div class="para">
To display information about the <code class="systemitem">e1000e</code> module, which is the Intel PRO/1000 network driver, run:
</div><pre class="screen">~]# <code class="command">modinfo e1000e</code>
-filename: /lib/modules/3.15.6-200.fc20.x86_64/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
+filename: /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko
version: 2.3.2-k
license: GPL
description: Intel(R) PRO/1000 Network Driver
author: Intel Corporation, <linux.nics at intel.com>
-srcversion: AB1D5F954DC03B1296E61BD
+srcversion: 2FBED3F5E2EF40112284D95
alias: pci:v00008086d00001503sv*sd*bc*sc*i*
alias: pci:v00008086d00001502sv*sd*bc*sc*i*
<em class="lineannotation"><span class="lineannotation">[some <code class="literal">alias</code> lines omitted]</span></em>
alias: pci:v00008086d0000105Esv*sd*bc*sc*i*
depends: ptp
intree: Y
-vermagic: 3.15.6-200.fc20.x86_64 SMP mod_unload
+vermagic: 3.17.4-302.fc21.x86_64 SMP mod_unload
signer: Fedora kernel signing key
-sig_key: 5B:F5:46:43:B9:B1:61:72:B2:43:6D:40:A5:6F:75:0A:D1:58:1D:80
+sig_key: 1F:C9:E6:8F:74:19:55:63:48:FD:EE:2F:DE:B7:FF:9D:A6:33:7B:BF
sig_hashalgo: sha256
parm: debug:Debug level (0=none,...,16=all) (int)
parm: copybreak:Maximum size of packet that is copied to a new buffer on receive (uint)
@@ -58,7 +58,7 @@ parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the
<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">
+ </div></li></ul></div><div class="example" id="ex-Listing_module_parameters"><h6>Example 22.2. Listing module parameters</h6><div class="example-contents"><div class="para">
You can list all parameters that the module supports by using the <code class="option">-p</code> option. However, because useful value type information is omitted from <code class="command">modinfo -p</code> output, it is more useful to run:
</div><pre class="screen">~]# <code class="command">modinfo e1000e | grep "^parm" | sort</code>
parm: copybreak:Maximum size of packet that is copied to a new buffer on receive (uint)
@@ -72,4 +72,4 @@ 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>
\ No newline at end of file
+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 22. 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>22.3. Loading a Module</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Displaying_Package_Information.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Displaying_Package_Information.html
index 4104f5f..f909288 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Displaying_Package_Information.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Displaying_Package_Information.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Packages_and_Package_Groups.html" title="5.2. Packages and Package Groups" /><link rel="prev" href="sec-Listing_Packages.html" title="5.2.2. Listing Packages" /><link rel="next" href="sec-Installing.html" title="5.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 accesskey="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">5.2.3. Displaying Package Information</h3></div></div></div><a id="idm225504743296" class="indexterm"></a><a id="idm225504741408" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Packages_and_Package_Groups.html" title="5.2. Packages and Package Groups" /><link rel="prev" href="sec-Listing_Packages.html" title="5.2.2. Listing Packages" /><link rel="next" href="sec-Installing.html" title="5.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 accesskey="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">5.2.3. Displaying Package Information</h3></div></div></div><a id="idm261741607728" class="indexterm"></a><a id="idm261741605840" class="indexterm"></a><div class="para">
To display information about one or more packages (glob expressions are valid here as well), use the following command:
</div><pre class="synopsis"><code class="command">yum</code> <code class="option">info</code> <em class="replaceable"><code>package_name</code></em>…</pre><div class="para">
For example, to display information about the <span class="package">abrt</span> package, type:
@@ -25,7 +25,7 @@ URL : https://fedorahosted.org/abrt/
License : GPLv2+
Description : abrt is a tool to help users to detect defects in applications and
: to create a bug report with all informations needed by maintainer
- : to fix it. It uses plugin system to extend its functionality.</pre><a id="idm225470612480" class="indexterm"></a><a id="idm225470610560" class="indexterm"></a><div class="para">
+ : to fix it. It uses plugin system to extend its functionality.</pre><a id="idm261714534960" class="indexterm"></a><a id="idm261714533040" class="indexterm"></a><div class="para">
The <code class="command">yum info <em class="replaceable"><code>package_name</code></em></code> command is similar to the <code class="command">rpm -q --info <em class="replaceable"><code>package_name</code></em></code> command, but provides as additional information the ID of the Yum repository the RPM package is found in (look for the <code class="computeroutput">From repo:</code> line in the output).
</div><div class="para">
You can also query the Yum database for alternative and useful information about a package by using the following command:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Editing_an_Entry.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Editing_an_Entry.html
new file mode 100644
index 0000000..327252d
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Editing_an_Entry.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.2.2. Editing an Entry</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Customizing_GRUB_2_Menu.html" title="20.2. Customizing GRUB 2 Menu" /><link rel="prev" href="sec-Customizing_GRUB_2_Menu.html" title="20.2. Customizing GRUB 2 Menu" /><link rel="next" href="sec-Adding_a_new_Entry.html" title="20.2.3. Adding a new Entry" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Customizing_GRUB_2_Menu.html"><strong>Prev</stron
g></a></li><li class="next"><a accesskey="n" href="sec-Adding_a_new_Entry.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Editing_an_Entry"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.2.2. Editing an Entry</h3></div></div></div><h4 id="idm261734448192">Kernel Parameters</h4><div class="para">
+ To use a kernel parameter only during a single boot process, when the GRUB 2 boot menu appears, move the cursor to the kernel you want to start, and press the <span class="keycap"><strong>e</strong></span> key to edit the kernel parameters. For example, to run the system in emergency mode, add the <span class="emphasis"><em>emergency</em></span> parameter at the end of the <code class="literal">linux16</code> line:
+ </div><pre class="screen">linux16 /vmlinuz-3.17.4-301.fc21.x86_64 root=/dev/mapper/fedora-root ro rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet LANG=en_US.UTF-8 emergency</pre><div class="para">
+ These settings are not persistent and apply only for a single boot. To make the settings persistent, edit values of the <code class="systemitem">GRUB_CMDLINE_LINUX</code> key in the <code class="filename">/etc/default/grub</code> file. For example, if you want to enable emergency mode for each boot, use:
+ </div><pre class="screen">GRUB_CMDLINE_LINUX="emergency"</pre><div class="para">
+ Note that you can specify multiple parameters for the <code class="systemitem">GRUB_CMDLINE_LINUX</code> key, similarly to adding the parameters in the GRUB 2 boot menu. For example: <pre class="synopsis">GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,9600n8"</pre> Where <code class="option">console=tty0</code> is the first virtual terminal and <code class="option">console=ttyS0</code> is the serial terminal to be used.
+ </div><div class="para">
+ Changes to <code class="filename">/etc/default/grub</code> require rebuilding the <code class="filename">grub.cfg</code> file as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div class="para">
+ On UEFI-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Customizing_GRUB_2_Menu.html"><strong>Prev</strong>20.2. Customizing GRUB 2 Menu</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-Adding_a_new_Entry.html"><strong>Next</strong>20.2.3. Adding a new Entry</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-GRUB_2_Password_Protection.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-GRUB_2_Password_Protection.html
new file mode 100644
index 0000000..a272dd9
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-GRUB_2_Password_Protection.html
@@ -0,0 +1,66 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.3. GRUB 2 Password Protection</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="Chapter 20. Working with the GRUB 2 Boot Loader" /><link rel="prev" href="sec-Using_only_a_Custom_Menu.html" title="20.2.4. Creating a Custom Menu" /><link rel="next" href="sec-Password_Encryption.html" title="20.3.2. Password Encryption" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_only_a_Cu
stom_Menu.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Password_Encryption.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-GRUB_2_Password_Protection"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.3. GRUB 2 Password Protection</h2></div></div></div><div class="para">
+ GRUB 2 supports both plain-text and encrypted passwords in the GRUB 2 template files. To enable the use of passwords, specify a superuser who can reach the protected entries. Other users can be specified to access these entries as well. Menu entries can be password-protected for booting by adding one or more users to the menu entry as described in <a class="xref" href="sec-GRUB_2_Password_Protection.html#sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries">Section 20.3.1, “Setting Up Users and Password Protection, Specifying Menu Entries”</a>. To use encrypted passwords, see <a class="xref" href="sec-Password_Encryption.html">Section 20.3.2, “Password Encryption”</a>.
+ </div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ If you do not use the correct format for the menu, or modify the configuration in an incorrect way, you might be unable to boot your system.
+ </div></div></div><div class="para">
+ All menu entries can be password-protected against changes by setting superusers, which can be done in the <code class="filename">/etc/grub.d/00_header</code> or the <code class="filename">/etc/grub.d/01_users</code> file. The <code class="filename">00_header</code> file is very complicated and, if possible, avoid making modifications in this file. Menu entries should be placed in the <code class="filename">/etc/grub.d/40_custom</code> and users in the <code class="filename">/etc/grub.d/01_users</code> file. The <code class="filename">01_users</code> file is generated by the installation application <span class="application"><strong>anaconda</strong></span> when a grub boot loader password is used in a <span class="application"><strong>kickstart</strong></span> template (but it should be created and used it if it does not exist). Examples in this section adopt this policy.
+ </div><div class="section" id="sec-Setting_Up_Users_and_Password_Protection_Specifying_Menu_Entries"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.3.1. Setting Up Users and Password Protection, Specifying Menu Entries</h3></div></div></div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To specify a superuser, add the following lines in the <code class="filename">/etc/grub.d/01_users</code> file, where <code class="systemitem">john</code> is the name of the user designated as the superuser, and <code class="literal">johnspassword</code> is the superuser's password:
+ </div><pre class="screen">cat <<EOF
+set superusers="john"
+password john johnspassword
+EOF</pre></li><li class="step"><div class="para">
+ To allow other users to access the menu entries, add additional lines per user at the end of the <code class="filename">/etc/grub.d/01_users</code> file.
+ </div><pre class="screen">cat <<EOF
+set superusers="john"
+password john johnspassword
+password jane janespassword
+EOF</pre></li><li class="step"><div class="para">
+ When the users and passwords are set up, specify the menu entries that should be password-protected in the <code class="filename">/etc/grub.d/40_custom</code> file in a similar fashion to the following:
+ </div><pre class="screen">
+menuentry 'Red Hat Enterprise Linux Server' --unrestricted {
+set root=(hd0,msdos1)
+linux /vmlinuz
+}
+
+menuentry 'Fedora' --users jane {
+set root=(hd0,msdos2)
+linux /vmlinuz
+}
+
+menuentry 'Red Hat Enterprise Linux Workstation' {
+set root=(hd0,msdos3)
+linux /vmlinuz
+}</pre></li></ol></div><div class="para">
+ In the above example:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">john</code> is the <code class="literal">superuser</code> and can therefore boot any menu entry, use the GRUB 2 command line, and edit items of the GRUB 2 menu during boot. In this case, <code class="systemitem">john</code> can access both Red Hat Enterprise Linux Server, Fedora, and Red Hat Enterprise Linux Workstation. Note that only <code class="systemitem">john</code> can access Red Hat Enterprise Linux Workstation because neither the <code class="option">--users</code> nor <code class="option">--unrestricted</code> options have been used.
+ </div></li><li class="listitem"><div class="para">
+ User <code class="systemitem">jane</code> can boot Fedora since she was granted the permission in the configuration.
+ </div></li><li class="listitem"><div class="para">
+ Anyone can boot Red Hat Enterprise Linux Server, because of the <code class="option">--unrestricted</code> option, but only <code class="systemitem">john</code> can edit the menu entry as a superuser has been defined. When a superuser is defined then all records are protected against unauthorized changes and all records are protected for booting if they do <span class="bold bold"><strong>not</strong></span> have the <code class="option">--unrestricted</code> parameter
+ </div></li></ul></div><div class="para">
+
+ </div><div class="para">
+ If you do not specify a user for a menu entry, or make use of the <code class="option">--unrestricted</code> option, then only the superuser will have access to the system.
+ </div><div class="para">
+ After you have made changes in the template file the GRUB 2 configuration file must be updated.
+ </div><div class="para">
+ Update the <code class="filename">grub.cfg</code> file by running the <code class="command">grub2-mkconfig <code class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div class="para">
+ On UEFI-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_only_a_Custom_Menu.html"><strong>Prev</strong>20.2.4. Creating a Custom Menu</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-Password_Encryption.html"><strong>Next</strong>20.3.2. Password Encryption</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-GRUB_2_over_Serial_Console.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-GRUB_2_over_Serial_Console.html
new file mode 100644
index 0000000..0a7975d
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-GRUB_2_over_Serial_Console.html
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.5. GRUB 2 over Serial Console</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="Chapter 20. Working with the GRUB 2 Boot Loader" /><link rel="prev" href="sec-Resetting_and_Reinstalling_GRUB_2.html" title="20.4.2. Resetting and Reinstalling GRUB 2" /><link rel="next" href="sec-Using_screen_to_Connect_to_the_Serial_Console.html" title="20.5.2. Using screen to Connect to the Serial Console" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class=
"docnav"><li class="previous"><a accesskey="p" href="sec-Resetting_and_Reinstalling_GRUB_2.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Using_screen_to_Connect_to_the_Serial_Console.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-GRUB_2_over_Serial_Console"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.5. GRUB 2 over Serial Console</h2></div></div></div><div class="para">
+ If you use computers with no display or keyboard, it can be very useful to control the machines through serial communications.
+ </div><div class="section" id="sec-Configuring_GRUB_2"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.5.1. Configuring GRUB 2</h3></div></div></div><div class="para">
+ In order to use GRUB 2 over a serial line, add the following two lines in the <code class="filename">/etc/default/grub</code> file:
+ </div><pre class="programlisting">
+GRUB_TERMINAL="serial"
+GRUB_SERIAL_COMMAND="serial --speed=9600 --unit=0 --word=8 --parity=no --stop=1"
+</pre><div class="para">
+ The first line disables the graphical terminal. Note that specifying the <code class="literal">GRUB_TERMINAL</code> key overrides values of <code class="literal">GRUB_TERMINAL_INPUT</code> and <code class="literal">GRUB_TERMINAL_OUTPUT</code>. On the second line, adjust the baud rate, parity, and other values to fit your environment and hardware. A much higher baud rate, for example <code class="literal">115200</code>, is preferable for tasks such as following log files. Once you have completed the changes in the <code class="filename">/etc/default/grub</code> file, it is necessary to update the GRUB 2 configuration file.
+ </div><div class="para">
+ Update the <code class="filename">grub.cfg</code> file by running the <code class="command">grub2-mkconfig <code class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div class="para">
+ On UEFI-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ In order to access the grub terminal over a serial connection an additional option must be added to a kernel definition to make that particular kernel monitor a serial connection. For example: <pre class="synopsis">console=<em class="replaceable"><code>ttyS0,9600n8</code></em></pre> Where <code class="option">console=ttyS0</code> is the serial terminal to be used, <code class="option">9600</code> is the baud rate, <code class="option">n</code> is for no parity, and <code class="option">8</code> is the word length in bits. A much higher baud rate, for example <code class="literal">115200</code>, is preferable for tasks such as following log files.
+ </div><div class="para">
+ For more information on adding kernel options, see <a class="xref" href="sec-Editing_an_Entry.html">Section 20.2.2, “Editing an Entry”</a>. For more information on serial console settings, see <a href="https://www.kernel.org/doc/Documentation/serial-console.txt">https://www.kernel.org/doc/Documentation/serial-console.txt</a>
+ </div></div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Resetting_and_Reinstalling_GRUB_2.html"><strong>Prev</strong>20.4.2. Resetting and Reinstalling GRUB 2</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_screen_to_Connect_to_the_Serial_Console.html"><strong>Next</strong>20.5.2. Using screen to Connect to the Serial Con...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Improving_Accuracy.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Improving_Accuracy.html
index 3ea655e..e353d5d 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Improving_Accuracy.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Improving_Accuracy.html
@@ -1,11 +1,17 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.9. Improving Accuracy</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.10. Improving Accuracy</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Configuring_PTP_Using_ptp4l.html" title="Chapter 15. Configuring PTP Using ptp4l" /><link rel="prev" href="sec-Serving_NTP_Time_with_PTP.html" title="15.8. Serving NTP Time with PTP" /><link rel="next" href="sec-PTP_additional_resources.html" title="15.10. 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-Serving_NTP_Time_with_PT
P.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-PTP_additional_resources.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Improving_Accuracy"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.9. Improving Accuracy</h2></div></div></div><div class="para">
- Test results indicate that disabling the tickless kernel capability can significantly improve the stability of the system clock, and thus improve the <code class="systemitem">PTP</code> synchronization accuracy (at the cost of increased power consumption). The kernel tickless mode can be disabled by adding <code class="option">nohz=off</code> to the kernel boot option parameters.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Serving_NTP_Time_with_PTP.html"><strong>Prev</strong>15.8. Serving NTP Time with PTP</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-PTP_additional_resources.html"><strong>Next</strong>15.10. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Configuring_PTP_Using_ptp4l.html" title="Chapter 15. Configuring PTP Using ptp4l" /><link rel="prev" href="sec-Configuring_timemaster_Options.html" title="15.9.3. Configuring timemaster Options" /><link rel="next" href="sec-PTP_additional_resources.html" title="15.11. Additional Resources" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_
timemaster_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-PTP_additional_resources.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Improving_Accuracy"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.10. Improving Accuracy</h2></div></div></div><div class="para">
+ Previously, test results indicated that disabling the tickless kernel capability could significantly improve the stability of the system clock, and thus improve the <code class="systemitem">PTP</code> synchronization accuracy (at the cost of increased power consumption). The kernel tickless mode can be disabled by adding <code class="option">nohz=off</code> to the kernel boot option parameters. However, recent improvements applied to <code class="filename">kernel-3.10.0-197.fc21</code> have greatly improved the stability of the system clock and the difference in stability of the clock with and without <code class="option">nohz=off</code> should be much smaller now for most users.
+ </div><div class="para">
+ The <span class="application"><strong>ptp4l</strong></span> and <span class="application"><strong>phc2sys</strong></span> applications can be configured to use a new adaptive servo. The advantage over the PI servo is that it does not require configuration of the PI constants to perform well. To make use of this for <span class="application"><strong>ptp4l</strong></span>, add the following line to the <code class="filename">/etc/ptp4l.conf</code> file: <pre class="synopsis">clock_servo linreg</pre> After making changes to <code class="filename">/etc/ptp4l.conf</code>, restart the <span class="application"><strong>ptp4l</strong></span> service from the command line by issuing the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl restart ptp4l</code></pre>
+ </div><div class="para">
+ To make use of this for <span class="application"><strong>phc2sys</strong></span>, add the following line to the <code class="filename">/etc/sysconfig/phc2sys</code> file: <pre class="synopsis">-E linreg</pre> After making changes to <code class="filename">/etc/sysconfig/phc2sys</code>, restart the <span class="application"><strong>phc2sys</strong></span> service from the command line by issuing the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl restart phc2sys</code></pre>
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Configuring_timemaster_Options.html"><strong>Prev</strong>15.9.3. Configuring timemaster 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-PTP_additional_resources.html"><strong>Next</strong>15.11. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Installing.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Installing.html
index 028f1f3..f82f8df 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Installing.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Installing.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Packages_and_Package_Groups.html" title="5.2. Packages and Package Groups" /><link rel="prev" href="sec-Displaying_Package_Information.html" title="5.2.3. Displaying Package Information" /><link rel="next" href="sec-Removing.html" title="5.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"><s
trong>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">5.2.4. Installing Packages</h3></div></div></div><a id="idm225455552720" class="indexterm"></a><a id="idm225455551280" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Packages_and_Package_Groups.html" title="5.2. Packages and Package Groups" /><link rel="prev" href="sec-Displaying_Package_Information.html" title="5.2.3. Displaying Package Information" /><link rel="next" href="sec-Removing.html" title="5.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"><s
trong>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">5.2.4. Installing Packages</h3></div></div></div><a id="idm261752561072" class="indexterm"></a><a id="idm261752559632" class="indexterm"></a><div class="para">
Yum allows you to install both a single package and multiple packages, as well as a package group of your choice.
</div><h4 id="bh-Installing_Individual_packages"> Installing Individual Packages </h4><div class="para">
To install a single package and all of its non-installed dependencies, enter a command in the following form:
@@ -30,7 +30,7 @@ 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 id="bh-Installing_a_Package_Group"> Installing a Package Group </h4><a id="idm225475020608" class="indexterm"></a><a id="idm225475019200" class="indexterm"></a><div class="para">
+ </div></div></div><h4 id="bh-Installing_a_Package_Group"> Installing a Package Group </h4><a id="idm261728638080" class="indexterm"></a><a id="idm261728636672" 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
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Listing_Packages.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Listing_Packages.html
index 4f74c22..cda20b9 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Listing_Packages.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Listing_Packages.html
@@ -6,11 +6,11 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Packages_and_Package_Groups.html" title="5.2. Packages and Package Groups" /><link rel="prev" href="sec-Packages_and_Package_Groups.html" title="5.2. Packages and Package Groups" /><link rel="next" href="sec-Displaying_Package_Information.html" title="5.2.3. Displaying Package Information" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Packages_and
_Package_Groups.html"><strong>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">5.2.2. Listing Packages</h3></div></div></div><a id="idm225462575696" class="indexterm"></a><a id="idm225462573808" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Packages_and_Package_Groups.html" title="5.2. Packages and Package Groups" /><link rel="prev" href="sec-Packages_and_Package_Groups.html" title="5.2. Packages and Package Groups" /><link rel="next" href="sec-Displaying_Package_Information.html" title="5.2.3. Displaying Package Information" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Packages_and
_Package_Groups.html"><strong>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">5.2.2. Listing Packages</h3></div></div></div><a id="idm261756126320" class="indexterm"></a><a id="idm261756124432" 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 Yum'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="idm225475318800" class="indexterm"></a><a id="idm225475316912" class="indexterm"></a><div class="para">
+ </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="idm261741462208" class="indexterm"></a><a id="idm261741460320" 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
@@ -33,8 +33,8 @@ 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="idm225479523952" class="indexterm"></a>
- <a id="idm225446226128" class="indexterm"></a>
+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="idm261761223680" class="indexterm"></a>
+ <a id="idm261726357872" 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 5.2. Listing all installed and available packages</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum list all</code>
@@ -50,8 +50,8 @@ 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="idm225453103856" class="indexterm"></a>
- <a id="idm225453101968" class="indexterm"></a>
+<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="idm261753426528" class="indexterm"></a>
+ <a id="idm261753424640" 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 5.3. Listing installed packages using a double-quoted glob expression</h6><div class="example-contents"><div class="para">
@@ -59,8 +59,8 @@ NetworkManager-openconnect.x86_64 0.8.1-9.git20110419.fc15 @fedora
</div><pre class="screen">~]# <code class="command">yum list installed "krb?-*"</code>
Loaded plugins: langpacks, presto, refresh-packagekit
Installed Packages
-krb5-libs.x86_64 1.9-7.fc15 @fedora</pre></div></div><br class="example-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225463723952" class="indexterm"></a>
- <a id="idm225463722064" class="indexterm"></a>
+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="idm261753086208" class="indexterm"></a>
+ <a id="idm261753084320" 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 5.4. Listing available packages using a single glob expression with escaped wildcard characters</h6><div class="example-contents"><div class="para">
@@ -80,8 +80,8 @@ 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="idm225457245456" class="indexterm"></a>
- <a id="idm225457243568" class="indexterm"></a>
+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="idm261744034496" class="indexterm"></a>
+ <a id="idm261746048016" 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 5.5. Listing all package groups</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum grouplist</code>
@@ -93,8 +93,8 @@ Installed Groups:
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="idm225462536416" class="indexterm"></a>
- <a id="idm225473987264" class="indexterm"></a>
+<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="idm261755610032" class="indexterm"></a>
+ <a id="idm261755608144" 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 5.6. Listing enabled repositories</h6><div class="example-contents"><pre class="screen">~]# <code class="command">yum repolist</code>
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Loading_a_Module.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Loading_a_Module.html
index 128e350..0fea8af 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Loading_a_Module.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Loading_a_Module.html
@@ -1,29 +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>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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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-Displayin
g_Information_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">21.3. Loading a Module</h2></div></div></div><a id="idm225445545488" class="indexterm"></a><a id="idm225463008832" class="indexterm"></a><a id="idm225463006752" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="prev" href="sec-Displaying_Information_About_a_Module.html" title="22.2. Displaying Information About a Module" /><link rel="next" href="sec-Unloading_a_Module.html" title="22.4. Unloading a Module" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Displayin
g_Information_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">22.3. Loading a Module</h2></div></div></div><a id="idm261724861680" class="indexterm"></a><a id="idm261724859760" class="indexterm"></a><a id="idm261745201040" 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="idm225463001632" class="indexterm"></a><div class="para">
+</pre><a id="idm261745195920" class="indexterm"></a><div class="para">
By default, <code class="command">modprobe</code> attempts to load the module from <code class="filename">/lib/modules/<em class="replaceable"><code>kernel_version</code></em>/kernel/drivers/</code>. In this directory, each type of module has its own subdirectory, such as <code class="filename">net/</code> and <code class="filename">scsi/</code>, for network and SCSI interface drivers respectively.
</div><div class="para">
Some modules have dependencies, which are other kernel modules that must be loaded before the module in question can be loaded. The <code class="command">modprobe</code> command always takes dependencies into account when performing operations. When you ask <code class="command">modprobe</code> to load a specific kernel module, it first examines the dependencies of that module, if there are any, and loads them if they are not already loaded into the kernel. <code class="command">modprobe</code> resolves dependencies recursively: it will load all dependencies of dependencies, and so on, if necessary, thus ensuring that all dependencies are always met.
</div><div class="para">
You can use the <code class="option">-v</code> (or <code class="option">--verbose</code>) option to cause <code class="command">modprobe</code> to display detailed information about what it is doing, which can include loading module dependencies.
- </div><div class="example" id="ex-modprobe_-v_shows_module_dependencies_as_they_are_loaded"><h6>Example 21.3. modprobe -v shows module dependencies as they are loaded</h6><div class="example-contents"><div class="para">
+ </div><div class="example" id="ex-modprobe_-v_shows_module_dependencies_as_they_are_loaded"><h6>Example 22.3. modprobe -v shows module dependencies as they are loaded</h6><div class="example-contents"><div class="para">
You can load the <code class="systemitem">Fibre Channel over Ethernet</code> module verbosely by typing the following at a shell prompt:
</div><pre class="screen">~]# <code class="command">modprobe -v fcoe</code>
-insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/scsi_tgt.ko
-insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/scsi_transport_fc.ko
-insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/libfc/libfc.ko
-insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/fcoe/libfcoe.ko
-insmod /lib/modules/3.16.6-200.fc20.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko</pre><div class="para">
+insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/scsi_transport_fc.ko.xz
+insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/libfc/libfc.ko.xz
+insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/fcoe/libfcoe.ko.xz
+insmod /lib/modules/3.17.4-302.fc21.x86_64/kernel/drivers/scsi/fcoe/fcoe.ko.xz</pre><div class="para">
In this example, you can see that <code class="command">modprobe</code> loaded the <code class="systemitem">scsi_tgt</code>, <code class="systemitem">scsi_transport_fc</code>, <code class="systemitem">libfc</code> and <code class="systemitem">libfcoe</code> modules as dependencies before finally loading <code class="systemitem">fcoe</code>. Also note that <code class="command">modprobe</code> used the more primitive <code class="command">insmod</code> command to insert the modules into the running kernel.
- </div></div></div><br class="example-break" /><a id="idm225477705136" class="indexterm"></a><a id="idm225477703056" 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">
+ </div></div></div><br class="example-break" /><a id="idm261750626384" class="indexterm"></a><a id="idm261750624304" 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>
\ No newline at end of file
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Displaying_Information_About_a_Module.html"><strong>Prev</strong>22.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>22.4. Unloading a Module</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Managing_Yum_Repositories.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Managing_Yum_Repositories.html
index 533fb05..b629886 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Managing_Yum_Repositories.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Managing_Yum_Repositories.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="5.3. Configuring Yum and Yum Repositories" /><link rel="prev" href="sec-Viewing_the_Current_Configuration.html" title="5.3.4. Viewing the Current Configuration" /><link rel="next" href="sec-Creating_a_Yum_Repository.html" title="5.3.6. 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-Viewing_the_Current_Configuration.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-Managing_Yum_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.3.5. Adding, Enabling, and Disabling a Yum Repository</h3></div></div></div><a id="idm225469297584" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="5.3. Configuring Yum and Yum Repositories" /><link rel="prev" href="sec-Viewing_the_Current_Configuration.html" title="5.3.4. Viewing the Current Configuration" /><link rel="next" href="sec-Creating_a_Yum_Repository.html" title="5.3.6. 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-Viewing_the_Current_Configuration.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-Managing_Yum_Repositories"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.3.5. Adding, Enabling, and Disabling a Yum Repository</h3></div></div></div><a id="idm261718015200" class="indexterm"></a><div class="para">
<a class="xref" href="sec-Setting_repository_Options.html">Section 5.3.2, “Setting [repository] Options”</a> described various options you can use to define a Yum repository. This section explains how to add, enable, and disable a repository by using the <code class="command">yum-config-manager</code> command.
</div><h4 id="bh-Managing_Yum_Repositories-Adding"> Adding a Yum Repository </h4><div class="para">
To define a new repository, you can either add a <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> section to the <code class="filename">/etc/yum.conf</code> file, or to a <code class="filename">.repo</code> file in the <code class="filename">/etc/yum.repos.d/</code> directory. All files with the <code class="filename">.repo</code> file extension in this directory are read by <code class="command">yum</code>, and best practice is to define your repositories here instead of in <code class="filename">/etc/yum.conf</code>.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-PTP_additional_resources.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-PTP_additional_resources.html
index ccb9ec7..72e2127 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-PTP_additional_resources.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-PTP_additional_resources.html
@@ -1,17 +1,19 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.10. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.11. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Configuring_PTP_Using_ptp4l.html" title="Chapter 15. Configuring PTP Using ptp4l" /><link rel="prev" href="sec-Improving_Accuracy.html" title="15.9. Improving Accuracy" /><link rel="next" href="sec-PTP_useful-websites.html" title="15.10.2. Useful Websites" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Improving_Accuracy.html"><strong>Prev</strong>
</a></li><li class="next"><a accesskey="n" href="sec-PTP_useful-websites.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-PTP_additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.10. Additional Resources</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Configuring_PTP_Using_ptp4l.html" title="Chapter 15. Configuring PTP Using ptp4l" /><link rel="prev" href="sec-Improving_Accuracy.html" title="15.10. Improving Accuracy" /><link rel="next" href="sec-PTP_useful-websites.html" title="15.11.2. Useful Websites" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Improving_Accuracy.html"><strong>Prev</strong
></a></li><li class="next"><a accesskey="n" href="sec-PTP_useful-websites.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-PTP_additional_resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.11. Additional Resources</h2></div></div></div><div class="para">
The following sources of information provide additional resources regarding <code class="systemitem">PTP</code> and the <span class="application"><strong>ptp4l</strong></span> tools.
- </div><div class="section" id="sec-PTP-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.10.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ </div><div class="section" id="sec-PTP-docs-inst"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.11.1. Installed Documentation</h3></div></div></div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="filename">ptp4l(8)</code> man page — Describes <span class="application"><strong>ptp4l</strong></span> options including the format of the configuration file.
</div></li><li class="listitem"><div class="para">
<code class="filename">pmc(8)</code> man page — Describes the <code class="systemitem">PTP</code> management client and its command options.
</div></li><li class="listitem"><div class="para">
<code class="filename">phc2sys(8)</code> man page — Describes a tool for synchronizing the system clock to a <code class="systemitem">PTP</code> hardware clock (PHC).
- </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Improving_Accuracy.html"><strong>Prev</strong>15.9. Improving Accuracy</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-PTP_useful-websites.html"><strong>Next</strong>15.10.2. Useful Websites</a></li></ul></body></html>
\ No newline at end of file
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">timemaster(8)</code> man page — Describes a program that uses <span class="application"><strong>ptp4l</strong></span> and <span class="application"><strong>phc2sys</strong></span> to synchronize the system clock using <code class="systemitem">chronyd</code> or <code class="systemitem">ntpd</code>.
+ </div></li></ul></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Improving_Accuracy.html"><strong>Prev</strong>15.10. Improving Accuracy</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-PTP_useful-websites.html"><strong>Next</strong>15.11.2. Useful Websites</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-PTP_useful-websites.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-PTP_useful-websites.html
index 4b23a4d..364ac57 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-PTP_useful-websites.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-PTP_useful-websites.html
@@ -1,16 +1,16 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.10.2. Useful Websites</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.11.2. Useful Websites</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-PTP_additional_resources.html" title="15.10. Additional Resources" /><link rel="prev" href="sec-PTP_additional_resources.html" title="15.10. Additional Resources" /><link rel="next" href="part-Monitoring_and_Automation.html" title="Part V. 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="sec-PTP_additional_resources.html"><str
ong>Prev</strong></a></li><li class="next"><a accesskey="n" href="part-Monitoring_and_Automation.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-PTP_useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.10.2. Useful Websites</h3></div></div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-PTP_additional_resources.html" title="15.11. Additional Resources" /><link rel="prev" href="sec-PTP_additional_resources.html" title="15.11. Additional Resources" /><link rel="next" href="part-Monitoring_and_Automation.html" title="Part V. 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="sec-PTP_additional_resources.html"><str
ong>Prev</strong></a></li><li class="next"><a accesskey="n" href="part-Monitoring_and_Automation.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-PTP_useful-websites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.11.2. Useful Websites</h3></div></div></div><div class="para">
<div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><a href="http://linuxptp.sourceforge.net/">http://linuxptp.sourceforge.net/</a></span></dt><dd><div class="para">
The Linux PTP project.
</div></dd><dt class="varlistentry"><span class="term"><a href="http://www.nist.gov/el/isd/ieee/ieee1588.cfm">http://www.nist.gov/el/isd/ieee/ieee1588.cfm</a></span></dt><dd><div class="para">
The IEEE 1588 Standard.
</div></dd></dl></div>
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-PTP_additional_resources.html"><strong>Prev</strong>15.10. 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-Monitoring_and_Automation.html"><strong>Next</strong>Part V. Monitoring and Automation</a></li></ul></body></html>
\ No newline at end of file
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-PTP_additional_resources.html"><strong>Prev</strong>15.11. 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-Monitoring_and_Automation.html"><strong>Next</strong>Part V. Monitoring and Automation</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Packages_and_Package_Groups.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Packages_and_Package_Groups.html
index c7aee66..f1ca77b 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Packages_and_Package_Groups.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Packages_and_Package_Groups.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-yum.html" title="Chapter 5. Yum" /><link rel="prev" href="ch-yum.html" title="Chapter 5. Yum" /><link rel="next" href="sec-Listing_Packages.html" title="5.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</stro
ng></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">5.2. Packages and Package Groups</h2></div></div></div><a id="idm225467854112" class="indexterm"></a><a id="idm225475263776" class="indexterm"></a><div class="section" id="sec-Searching_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.1. Searching Packages</h3></div></div></div><a id="idm225475261312" class="indexterm"></a><a id="idm225475259424" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-yum.html" title="Chapter 5. Yum" /><link rel="prev" href="ch-yum.html" title="Chapter 5. Yum" /><link rel="next" href="sec-Listing_Packages.html" title="5.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</stro
ng></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">5.2. Packages and Package Groups</h2></div></div></div><a id="idm261741655344" class="indexterm"></a><a id="idm261741653936" class="indexterm"></a><div class="section" id="sec-Searching_Packages"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">5.2.1. Searching Packages</h3></div></div></div><a id="idm261784612720" class="indexterm"></a><a id="idm261784610832" class="indexterm"></a><div class="para">
You can search all <acronym class="acronym">RPM</acronym> package names, descriptions and summaries by using the following command:
</div><pre class="synopsis"><code class="command">yum</code> <code class="option">search</code> <em class="replaceable"><code>term</code></em>…</pre><div class="para">
This command displays the list of matches for each term. For example, to list all packages that match <span class="quote">“<span class="quote">meld</span>”</span> or <span class="quote">“<span class="quote">kompare</span>”</span>, type:
@@ -19,6 +19,6 @@ python-meld3.x86_64 : HTML/XML templating system for Python
============================= N/S Matched: kompare =============================
komparator.x86_64 : Kompare and merge two folders
- Name and summary matches only, use "search all" for everything.</pre><a id="idm225463388000" class="indexterm"></a><a id="idm225463386112" class="indexterm"></a><div class="para">
+ Name and summary matches only, use "search all" for everything.</pre><a id="idm261727957968" class="indexterm"></a><a id="idm261727956080" class="indexterm"></a><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 5. 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>5.2.2. Listing Packages</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Password_Encryption.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Password_Encryption.html
new file mode 100644
index 0000000..da5b8bf
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Password_Encryption.html
@@ -0,0 +1,27 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.3.2. Password Encryption</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-GRUB_2_Password_Protection.html" title="20.3. GRUB 2 Password Protection" /><link rel="prev" href="sec-GRUB_2_Password_Protection.html" title="20.3. GRUB 2 Password Protection" /><link rel="next" href="sec-Reinstalling_GRUB_2.html" title="20.4. Reinstalling GRUB 2" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-GRUB_2_Password_Protection.html"><str
ong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Reinstalling_GRUB_2.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Password_Encryption"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.3.2. Password Encryption</h3></div></div></div><div class="para">
+ By default, passwords are saved in plain text in GRUB 2 scripts. Although the files cannot be accessed on boot without the correct password, security can be improved by encrypting the password using the <code class="command">grub2-mkpasswd-pbkdf2</code> command. This command converts a desired password into a long hash, which is placed in the GRUB 2 scripts instead of the plain-text password.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To generate an encrypted password, run the <code class="command">grub2-mkpasswd-pbkdf2</code> command on the command line as <code class="systemitem">root</code>.
+ </div></li><li class="step"><div class="para">
+ Enter the desired password when prompted and repeat it. The command then outputs your password in an encrypted form.
+ </div></li><li class="step"><div class="para">
+ Copy the hash, and paste it in the template file where you configured the users, that is, either in <code class="filename">/etc/grub.d/01_users</code> or <code class="filename">/etc/grub.d/40_custom</code>.
+ </div><div class="para">
+ The following format applies for the <code class="filename">01_users</code> file:
+<pre class="screen">cat <<EOF
+set superusers="john"
+password_pbkdf2 john grub.pbkdf2.sha512.10000.19074739ED80F115963D984BDCB35AA671C24325755377C3E9B014D862DA6ACC77BC110EED41822800A87FD3700C037320E51E9326188D53247EC0722DDF15FC.C56EC0738911AD86CEA55546139FEBC366A393DF9785A8F44D3E51BF09DB980BAFEF85281CBBC56778D8B19DC94833EA8342F7D73E3A1AA30B205091F1015A85
+EOF</pre>
+ </div><div class="para">
+ The following format applies for the <code class="filename">40_custom</code> file:
+<pre class="screen">set superusers="john"
+password_pbkdf2 john grub.pbkdf2.sha512.10000.19074739ED80F115963D984BDCB35AA671C24325755377C3E9B014D862DA6ACC77BC110EED41822800A87FD3700C037320E51E9326188D53247EC0722DDF15FC.C56EC0738911AD86CEA55546139FEBC366A393DF9785A8F44D3E51BF09DB980BAFEF85281CBBC56778D8B19DC94833EA8342F7D73E3A1AA30B205091F1015A85</pre>
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-GRUB_2_Password_Protection.html"><strong>Prev</strong>20.3. GRUB 2 Password Protection</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-Reinstalling_GRUB_2.html"><strong>Next</strong>20.4. Reinstalling GRUB 2</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Persistent_Module_Loading.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Persistent_Module_Loading.html
index 05e51e9..711a1c5 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Persistent_Module_Loading.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Persistent_Module_Loading.html
@@ -1,16 +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.6. Persistent Module Loading</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.6. Persistent Module Loading</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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="s1-kernel-modules-additional-resources.html" title="21.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="sec-Setting_Module_
Parameters.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-Persistent_Module_Loading"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">21.6. Persistent Module Loading</h2></div></div></div><a id="idm225451338304" class="indexterm"></a><a id="idm225451336384" 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 the <code class="systemitem">systemd-modules-load.service</code> daemon by creating a <code class="filename"><em class="replaceable"><code>program</code></em>.conf</code> file in the <code class="filename">/etc/modules-load.d/</code> directory, where <em class="replaceable"><code>program</code></em> is any descriptive name of your choice. The files in <code class="filename">/etc/modules-load.d/</code> are text files that list the modules to be loaded, one per line.
- </div><div class="example" id="ex-A_Text_File_to_Load_a_Module"><h6>Example 21.6. A Text File to Load a Module</h6><div class="example-contents"><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="prev" href="sec-Setting_Module_Parameters.html" title="22.5. Setting Module Parameters" /><link rel="next" href="sect-signing-kernel-modules-for-secure-boot.html" title="22.7. Signing Kernel Modules for Secure Boot" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" hr
ef="sec-Setting_Module_Parameters.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-signing-kernel-modules-for-secure-boot.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">22.6. Persistent Module Loading</h2></div></div></div><a id="idm261742364272" class="indexterm"></a><a id="idm261742362352" 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 22.1, “Listing information about a kernel module with lsmod”</a>, many kernel modules are loaded automatically at boot time. You can specify additional modules to be loaded by the <code class="systemitem">systemd-modules-load.service</code> daemon by creating a <code class="filename"><em class="replaceable"><code>program</code></em>.conf</code> file in the <code class="filename">/etc/modules-load.d/</code> directory, where <em class="replaceable"><code>program</code></em> is any descriptive name of your choice. The files in <code class="filename">/etc/modules-load.d/</code> are text files that list the modules to be loaded, one per line.
+ </div><div class="example" id="ex-A_Text_File_to_Load_a_Module"><h6>Example 22.6. A Text File to Load a Module</h6><div class="example-contents"><div class="para">
To create a file to load the <code class="filename">virtio-net.ko</code> module, create a file <code class="filename">/etc/modules-load.d/virtio-net.conf</code> with the following content:
</div><pre class="screen"># Load virtio-net.ko at boot
virtio-net</pre></div></div><br class="example-break" /><div class="para">
See the <code class="filename">modules-load.d(5)</code> and <code class="filename">systemd-modules-load.service(8)</code> man pages for more information.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Setting_Module_Parameters.html"><strong>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="s1-kernel-modules-additional-resources.html"><strong>Next</strong>21.7. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Setting_Module_Parameters.html"><strong>Prev</strong>22.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="sect-signing-kernel-modules-for-secure-boot.html"><strong>Next</strong>22.7. Signing Kernel Modules for Secure Boot</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Plugin_Descriptions.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Plugin_Descriptions.html
index 4e2e752..99666ac 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Plugin_Descriptions.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Plugin_Descriptions.html
@@ -8,7 +8,7 @@
addID('Fedora.21.System_Administrators_Guide');
</script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Yum_Plugins.html" title="5.4. Yum Plug-ins" /><link rel="prev" href="sec-Installing_More_Yum_Plugins.html" title="5.4.2. Installing Additional Yum Plug-ins" /><link rel="next" href="sec-Additional_Resources.html" title="5.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 class="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">5.4.3. Plug-in Descriptions</h3></div></div></div><div class="para">
The following list provides descriptions of a few useful Yum plug-ins:
- </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm225457395520" class="indexterm"></a>
+ </div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"> <a id="idm261757536640" class="indexterm"></a>
<span class="application"><strong>fs-snapshot</strong></span> (<span class="package">yum-plugin-fs-snapshot</span>) </span></dt><dd><div class="para">
The <span class="application"><strong>fs-snapshot</strong></span> plug-in extends Yum to create a snapshot of a file system before proceeding with a transaction such as a system update or package removal. When a user decides that the changes made by the transaction are unwanted, this mechanism allows the user to roll back to the changes that are stored in a snapshot.
</div><div class="para">
@@ -99,20 +99,20 @@
<code class="option">lvcreate_size_args</code>=<em class="replaceable"><code>value</code></em>
</td><td class="">
Allows you to specify the size of a logical volume snapshot. The <em class="replaceable"><code>value</code></em> must be the <code class="option">-l</code> or <code class="option">-L</code> command line option for the <span class="application"><strong>lvcreate</strong></span> utility followed by a valid argument (for example, <code class="literal">-l 80%ORIGIN</code>).
- </td></tr></tbody></table></div></div><br class="table-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm225468452432" class="indexterm"></a>
+ </td></tr></tbody></table></div></div><br class="table-break" /></dd><dt class="varlistentry"><span class="term"> <a id="idm261744054992" 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> plug-in adds support to Yum 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> plug-in 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="idm225445622512" class="indexterm"></a>
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261741794112" 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> plug-in 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> plug-in is installed by default.
- </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225437953632" class="indexterm"></a>
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261747787952" 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">
See the <span class="bold bold"><strong>rhnplugin</strong></span>(8) manual page for more information about the plug-in.
- </div></dd><dt class="varlistentry"><span class="term"> <a id="idm225475393856" class="indexterm"></a>
+ </div></dd><dt class="varlistentry"><span class="term"> <a id="idm261752394816" 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 Yum provides the <span class="application"><strong>security</strong></span> plug-in, which extends <code class="command">yum</code> with a set of highly-useful security-related commands, subcommands and options.
</div><div class="para">
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Printer_Configuration.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Printer_Configuration.html
index c74e5d9..64f59d4 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Printer_Configuration.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Printer_Configuration.html
@@ -6,18 +6,18 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-File_and_Print_Servers.html" title="Chapter 12. File and Print Servers" /><link rel="prev" href="s2-ftp-resources.html" title="12.2.6. Additional Resources" /><link rel="next" href="sec-Setting_Printer.html" title="12.3.2. Starting Printer Setup" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ftp-resources.html"><strong>Prev</strong></a></li><li cla
ss="next"><a accesskey="n" href="sec-Setting_Printer.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="sec-Printer_Configuration" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.3. Printer Configuration</h2></div></div></div><a id="idm225453339248" class="indexterm"></a><a id="idm225453337808" class="indexterm"></a><div class="para">
- The <span class="application"><strong>Printer</strong></span> configuration tool serves for printer configuring, maintenance of printer configuration files, print spool directories and print filters, and printer classes management.
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-File_and_Print_Servers.html" title="Chapter 12. File and Print Servers" /><link rel="prev" href="s2-ftp-resources.html" title="12.2.6. Additional Resources" /><link rel="next" href="sec-Setting_Printer.html" title="12.3.2. Starting Printer Setup" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ftp-resources.html"><strong>Prev</strong></a></li><li cla
ss="next"><a accesskey="n" href="sec-Setting_Printer.html"><strong>Next</strong></a></li></ul><div xml:lang="en-US" class="section" id="sec-Printer_Configuration" lang="en-US"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">12.3. Printer Configuration</h2></div></div></div><a id="idm261715812784" class="indexterm"></a><a id="idm261715811344" class="indexterm"></a><div class="para">
+ The <span class="application"><strong>Printers</strong></span> configuration tool serves for printer configuring, maintenance of printer configuration files, print spool directories and print filters, and printer classes management.
</div><div class="para">
The tool is based on the Common Unix Printing System (<acronym class="acronym">CUPS</acronym>). If you upgraded the system from a previous Fedora version that used CUPS, the upgrade process preserved the configured printers.
- </div><div class="note"><div class="admonition_header"><h2>Using the CUPS web application or command line tools</h2></div><div class="admonition"><a id="idm225478718976" class="indexterm"></a><div class="para">
+ </div><div class="note"><div class="admonition_header"><h2>Using the CUPS web application or command-line tools</h2></div><div class="admonition"><a id="idm261750649104" class="indexterm"></a><div class="para">
You can perform the same and additional operations on printers directly from the CUPS web application or command line. To access the application, in a web browser, go to <a href="http://localhost:631/">http://localhost:631/</a>. For CUPS manuals refer to the links on the <span class="guilabel"><strong>Home</strong></span> tab of the web site.
- </div></div></div><div class="section" id="sec-Starting_Printer_Config"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.1. Starting the Printer Configuration Tool</h3></div></div></div><div class="para">
- With the <span class="application"><strong>Printer</strong></span> configuration configuration tool you can perform various operations on existing printers and set up new printers. You can also use CUPS directly (go to <a href="http://localhost:631/">http://localhost:631/</a> to access the CUPS web application).
+ </div></div></div><div class="section" id="sec-Starting_Printer_Config"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.1. Starting the Printers Configuration Tool</h3></div></div></div><div class="para">
+ With the <span class="application"><strong>Printers</strong></span> configuration tool you can perform various operations on existing printers and set up new printers. You can also use CUPS directly (go to <a href="http://localhost:631/">http://localhost:631/</a> to access the CUPS web application).
</div><div class="para">
- To start the <span class="application"><strong>Printer</strong></span> configuration tool if using the GNOME desktop, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">Printer</code>, select the icon, and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Printer</strong></span> configuration tool appears. The <span class="keycap"><strong>Super</strong></span> key appears in a variety of guises, depending on the keyboard and other hardware, but often as either the Windows or Command key, and typically to the left of the <span class="keycap"><strong>Spacebar</strong></span>.
+ To start the <span class="application"><strong>Printers</strong></span> configuration tool if using the GNOME desktop, press the <span class="keycap"><strong>Super</strong></span> key to enter the Activities Overview, type <code class="command">Printers</code>, and then press <span class="keycap"><strong>Enter</strong></span>. The <span class="application"><strong>Printers</strong></span> configuration tool appears. The <span class="keycap"><strong>Super</strong></span> key appears in a variety of guises, depending on the keyboard and other hardware, but often as either the Windows or Command key, and typically to the left of the <span class="keycap"><strong>Spacebar</strong></span>.
</div><div class="para">
- The <span class="guilabel"><strong>Printer Configuration</strong></span> window depicted in <a class="xref" href="sec-Printer_Configuration.html#fig-printconf-main">Figure 12.2, “Printer Configuration window”</a> appears.
- </div><div class="figure" id="fig-printconf-main"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-main.png" alt="Printer Configuration window" /><div class="longdesc"><div class="para">
- Printer Configuration window
- </div></div></div></div><h6>Figure 12.2. Printer Configuration window</h6></div><br class="figure-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ftp-resources.html"><strong>Prev</strong>12.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="sec-Setting_Printer.html"><strong>Next</strong>12.3.2. Starting Printer Setup</a></li></ul></body></html>
\ No newline at end of file
+ The <span class="guilabel"><strong>Printers</strong></span> window depicted in <a class="xref" href="sec-Printer_Configuration.html#fig-printconf-main">Figure 12.2, “Printers Configuration window”</a> appears.
+ </div><div class="figure" id="fig-printconf-main"><div class="figure-contents"><div class="mediaobject"><img src="images/printconf-main.png" alt="Printers Configuration window" /><div class="longdesc"><div class="para">
+ Printers Configuration window
+ </div></div></div></div><h6>Figure 12.2. Printers Configuration window</h6></div><br class="figure-break" /></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-ftp-resources.html"><strong>Prev</strong>12.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="sec-Setting_Printer.html"><strong>Next</strong>12.3.2. Starting Printer Setup</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Reinstalling_GRUB_2.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Reinstalling_GRUB_2.html
new file mode 100644
index 0000000..3773420
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Reinstalling_GRUB_2.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.4. Reinstalling GRUB 2</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="Chapter 20. Working with the GRUB 2 Boot Loader" /><link rel="prev" href="sec-Password_Encryption.html" title="20.3.2. Password Encryption" /><link rel="next" href="sec-Resetting_and_Reinstalling_GRUB_2.html" title="20.4.2. Resetting and Reinstalling GRUB 2" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href=
"sec-Password_Encryption.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Resetting_and_Reinstalling_GRUB_2.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Reinstalling_GRUB_2"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.4. Reinstalling GRUB 2</h2></div></div></div><div class="para">
+ Reinstalling GRUB 2 is a convenient way to fix certain problems usually caused by an incorrect installation of GRUB 2, missing files, or a broken system. Other reasons to reinstall GRUB 2 include the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ Upgrading from the previous version of GRUB.
+ </div></li><li class="listitem"><div class="para">
+ The user requires the GRUB 2 boot loader to control installed operating systems. However, some operating systems are installed with their own boot loaders. Reinstalling GRUB 2 returns control to the desired operating system.
+ </div></li><li class="listitem"><div class="para">
+ Adding the boot information to another drive.
+ </div></li></ul></div><div class="section" id="sec-Using_the_grub2-install_Command"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.4.1. Using the grub2-install Command</h3></div></div></div><div class="para">
+ When using the <code class="command">grub2-install</code> command, the boot information is updated and missing files are restored. Note that the files are restored only if they are not corrupted. If the <code class="filename">/boot/grub2/</code> directory is missing, it will be recreated.
+ </div><div class="para">
+ Use the <code class="command">grub2-install <device></code> command to reinstall GRUB 2 if the system is operating normally. For example:
+ </div><pre class="screen">~]# <code class="command">grub2-install</code> <code class="filename">/dev/sda</code></pre></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Password_Encryption.html"><strong>Prev</strong>20.3.2. Password Encryption</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-Resetting_and_Reinstalling_GRUB_2.html"><strong>Next</strong>20.4.2. Resetting and Reinstalling GRUB 2</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Removing.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Removing.html
index 21cda5d..0dd91cb 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Removing.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Removing.html
@@ -6,9 +6,9 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Packages_and_Package_Groups.html" title="5.2. Packages and Package Groups" /><link rel="prev" href="sec-Installing.html" title="5.2.4. Installing Packages" /><link rel="next" href="sec-Yum-Transaction_History.html" title="5.2.6. Working with Transaction History" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing.html"><strong>Prev</strong></
a></li><li class="next"><a accesskey="n" href="sec-Yum-Transaction_History.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">5.2.5. Removing Packages</h3></div></div></div><a id="idm225454436128" class="indexterm"></a><a id="idm225498398848" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Packages_and_Package_Groups.html" title="5.2. Packages and Package Groups" /><link rel="prev" href="sec-Installing.html" title="5.2.4. Installing Packages" /><link rel="next" href="sec-Yum-Transaction_History.html" title="5.2.6. Working with Transaction History" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing.html"><strong>Prev</strong></
a></li><li class="next"><a accesskey="n" href="sec-Yum-Transaction_History.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">5.2.5. Removing Packages</h3></div></div></div><a id="idm261716792672" class="indexterm"></a><a id="idm261716791264" class="indexterm"></a><div class="para">
Similarly to package installation, Yum allows you to uninstall (remove in <span class="application"><strong>RPM</strong></span> and Yum terminology) both individual packages and a package group.
- </div><h4 id="bh-Removing_Individual_Packages"> Removing Individual Packages </h4><a id="idm225498395856" class="indexterm"></a><a id="idm225498393968" class="indexterm"></a><div class="para">
+ </div><h4 id="bh-Removing_Individual_Packages"> Removing Individual Packages </h4><a id="idm261716788272" class="indexterm"></a><a id="idm261716786384" class="indexterm"></a><div class="para">
To uninstall a particular package, as well as any packages that depend on it, run the following command as <code class="systemitem">root</code>:
</div><pre class="synopsis"><code class="command">yum</code> <code class="option">remove</code> <em class="replaceable"><code>package_name</code></em>…</pre><div class="para">
As when you install multiple packages, you can remove several at once by adding more package names to the command. For example, to remove <span class="package">totem</span>, <span class="package">rhythmbox</span>, and <span class="package">sound-juicer</span>, type the following at a shell prompt:
@@ -23,13 +23,13 @@
</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">
- Yum 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.
+ Yum 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.2, “Uninstalling Packages”</a> in the <span class="application"><strong>RPM</strong></span> chapter.
</div></div></div><h4 id="bh-Removing_a_Package_Group"> Removing a Package Group </h4><div class="para">
You can remove a package group using syntax congruent with the <code class="command">install</code> syntax:
</div><pre class="synopsis"><code class="command">yum</code> <code class="option">groupremove</code> <em class="replaceable"><code>group</code></em></pre><pre class="synopsis"><code class="command">yum</code> <code class="option">remove</code> @<em class="replaceable"><code>group</code></em></pre><div class="para">
The following are alternative but equivalent ways of removing the <code class="literal">KDE Desktop</code> group:
</div><pre class="screen">~]# <code class="command">yum groupremove "KDE Desktop"</code>
~]# <code class="command">yum groupremove kde-desktop</code>
-~]# <code class="command">yum remove @kde-desktop</code></pre><div class="important" id="important-Package_Group_Removal"><div class="admonition_header"><h2>Intelligent package group removal</h2></div><div class="admonition"><a id="idm225453696912" class="indexterm"></a><a id="idm225438947552" class="indexterm"></a><div class="para">
+~]# <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="idm261718689136" class="indexterm"></a><a id="idm261718687728" 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 5.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>5.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-Yum-Transaction_History.html"><strong>Next</strong>5.2.6. Working with Transaction History</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Resetting_and_Reinstalling_GRUB_2.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Resetting_and_Reinstalling_GRUB_2.html
new file mode 100644
index 0000000..8073f4e
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Resetting_and_Reinstalling_GRUB_2.html
@@ -0,0 +1,31 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.4.2. Resetting and Reinstalling GRUB 2</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Reinstalling_GRUB_2.html" title="20.4. Reinstalling GRUB 2" /><link rel="prev" href="sec-Reinstalling_GRUB_2.html" title="20.4. Reinstalling GRUB 2" /><link rel="next" href="sec-GRUB_2_over_Serial_Console.html" title="20.5. GRUB 2 over Serial Console" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Reinstalling_GRUB_2.html"><strong>Prev</strong></a>
</li><li class="next"><a accesskey="n" href="sec-GRUB_2_over_Serial_Console.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Resetting_and_Reinstalling_GRUB_2"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.4.2. Resetting and Reinstalling GRUB 2</h3></div></div></div><div class="para">
+ This method completely removes all GRUB 2 configuration files and system settings. Apply this method to reset all configuration settings to their default values. Removing of the configuration files and subsequent reinstalling of GRUB 2 fixes failures caused by corrupted files and incorrect configuration. To do so, as <code class="systemitem">root</code>, follow these steps:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Run the <code class="command">rm /etc/grub.d/*</code> command;
+ </div></li><li class="step"><div class="para">
+ Run the <code class="command">rm /etc/sysconfig/grub</code> command;
+ </div></li><li class="step"><div class="para">
+ For EFI systems <span class="bold bold"><strong>only</strong></span>, run the following command:
+<pre class="screen">~]# <code class="command">yum reinstall grub2-efi shim</code></pre>
+
+ </div></li><li class="step"><div class="para">
+ Update the <code class="filename">grub.cfg</code> file by running the <code class="command">grub2-mkconfig <code class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div class="para">
+ On UEFI-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></li><li class="step"><div class="para">
+ Now follow the procedure in <a class="xref" href="sec-Reinstalling_GRUB_2.html#sec-Using_the_grub2-install_Command">Section 20.4.1, “Using the grub2-install Command”</a> to restore GRUB2 on the <code class="filename">/boot/</code> partition.
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Reinstalling_GRUB_2.html"><strong>Prev</strong>20.4. Reinstalling GRUB 2</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-GRUB_2_over_Serial_Console.html"><strong>Next</strong>20.5. GRUB 2 over Serial Console</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Serving_NTP_Time_with_PTP.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Serving_NTP_Time_with_PTP.html
index 00387c6..613e605 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Serving_NTP_Time_with_PTP.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Serving_NTP_Time_with_PTP.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Configuring_PTP_Using_ptp4l.html" title="Chapter 15. Configuring PTP Using ptp4l" /><link rel="prev" href="sec-Serving_PTP_Time_with_NTP.html" title="15.7. Serving PTP Time with NTP" /><link rel="next" href="sec-Improving_Accuracy.html" title="15.9. Improving Accuracy" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Serving_PTP_Time_with_NTP.html"><
strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Improving_Accuracy.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Serving_NTP_Time_with_PTP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.8. Serving NTP Time with PTP</h2></div></div></div><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Configuring_PTP_Using_ptp4l.html" title="Chapter 15. Configuring PTP Using ptp4l" /><link rel="prev" href="sec-Serving_PTP_Time_with_NTP.html" title="15.7. Serving PTP Time with NTP" /><link rel="next" href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html" title="15.9. Synchronize to PTP or NTP Time Using timemaster" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a
accesskey="p" href="sec-Serving_PTP_Time_with_NTP.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Serving_NTP_Time_with_PTP"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.8. Serving NTP Time with PTP</h2></div></div></div><div class="para">
<code class="systemitem">NTP</code> to <code class="systemitem">PTP</code> synchronization in the opposite direction is also possible. When <code class="systemitem">ntpd</code> is used to synchronize the system clock, <span class="application"><strong>ptp4l</strong></span> can be configured with the <code class="option">priority1</code> option (or other clock options included in the best master clock algorithm) to be the grandmaster clock and distribute the time from the system clock via <code class="systemitem">PTP</code>:
<pre class="screen">~]# <code class="command">cat /etc/ptp4l.conf</code>
[global]
@@ -14,11 +14,13 @@ priority1 127
[em3]
# ptp4l -f /etc/ptp4l.conf</pre>
</div><div class="para">
- With hardware time stamping, <span class="application"><strong>phc2sys</strong></span> needs to be used to synchronize the <code class="systemitem">PTP</code> hardware clock to the system clock:
-<pre class="screen">~]# <code class="command">phc2sys -c <em class="replaceable"><code>em3</code></em> -s CLOCK_REALTIME -w</code></pre>
-
+ With hardware time stamping, <span class="application"><strong>phc2sys</strong></span> needs to be used to synchronize the <code class="systemitem">PTP</code> hardware clock to the system clock. If running <span class="application"><strong>phc2sys</strong></span> as a service, edit the <code class="filename">/etc/sysconfig/phc2sys</code> configuration file. The default setting in the <code class="filename">/etc/sysconfig/phc2sys</code> file is as follows: <pre class="synopsis">OPTIONS="-a -r"</pre> As <code class="systemitem">root</code>, edit that line as follows:
+<pre class="screen">~]# <code class="command">vi /etc/sysconfig/phc2sys</code>
+OPTIONS="-a -r -r"</pre>
+ The <code class="option">-r</code> option is used twice here to allow synchronization of the <code class="systemitem">PTP</code> hardware clock on the NIC from the system clock. Restart the <span class="application"><strong>phc2sys</strong></span> service for the changes to take effect:
+<pre class="screen">~]# <code class="command">systemctl restart phc2sys</code></pre>
</div><div class="para">
- To prevent quick changes in the <code class="systemitem">PTP</code> clock's frequency, the synchronization to the system clock can be loosened by using smaller <code class="option">P</code> (proportional) and <code class="option">I</code> (integral) constants of the PI servo:
-<pre class="screen">~]# <code class="command">phc2sys -c <em class="replaceable"><code>em3</code></em> -s CLOCK_REALTIME -w -P 0.01 -I 0.0001</code></pre>
+ To prevent quick changes in the <code class="systemitem">PTP</code> clock's frequency, the synchronization to the system clock can be loosened by using smaller <code class="option">P</code> (proportional) and <code class="option">I</code> (integral) constants for the PI servo:
+<pre class="screen">~]# <code class="command">phc2sys -a -r -r -P 0.01 -I 0.0001</code></pre>
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Serving_PTP_Time_with_NTP.html"><strong>Prev</strong>15.7. Serving PTP Time with NTP</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-Improving_Accuracy.html"><strong>Next</strong>15.9. Improving Accuracy</a></li></ul></body></html>
\ No newline at end of file
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Serving_PTP_Time_with_NTP.html"><strong>Prev</strong>15.7. Serving PTP Time with NTP</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-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html"><strong>Next</strong>15.9. Synchronize to PTP or NTP Time Using timema...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Setting_Module_Parameters.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Setting_Module_Parameters.html
index 984e364..c2bf1c1 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Setting_Module_Parameters.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Setting_Module_Parameters.html
@@ -1,18 +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>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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.5. Setting Module Parameters</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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">21.5. Setting Module Parameters</h2></div></div></div><a id="idm225464473072" class="indexterm"></a><a id="idm225477664944" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="prev" href="sec-Unloading_a_Module.html" title="22.4. Unloading a Module" /><link rel="next" href="sec-Persistent_Module_Loading.html" title="22.6. Persistent Module Loading" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Unloading_a_Module.html"><strong>
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">22.5. Setting Module Parameters</h2></div></div></div><a id="idm261785237392" class="indexterm"></a><a id="idm261785235952" 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="example" id="ex-Supplying_optional_parameters_when_loading_a_kernel_module"><h6>Example 21.5. Supplying optional parameters when loading a kernel module</h6><div class="example-contents"><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 22.6, “Persistent Module Loading”</a>, though the following information is a prerequisite.
+ </div></li></ol></div><div class="example" id="ex-Supplying_optional_parameters_when_loading_a_kernel_module"><h6>Example 22.5. Supplying optional parameters when loading a kernel module</h6><div class="example-contents"><div class="para">
You can use <code class="command">modprobe</code> to load a kernel module with custom parameters using the following command line format:
</div><pre class="screen">~]# <code class="command">modprobe <em class="replaceable"><code>module_name</code></em> [<span class="optional"><em class="replaceable"><code>parameter</code></em>=<em class="replaceable"><code>value</code></em></span>] </code>
</pre></div></div><br class="example-break" /><div class="para">
@@ -31,14 +31,14 @@
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">
+ </div><div class="procedure" id="proc-Loading_a_Kernel_Module_with_Custom_Parameters"><h6>Procedure 22.1. Loading a Kernel Module with Custom Parameters</h6><ol class="1"><li class="step" id="proc-step1-Loading_a_Kernel_Module_with_Custom_Parameters"><div class="para">
First, ensure the module is not already loaded into the kernel:
</div><pre class="screen">~]# <code class="command">lsmod |grep e1000e</code>
~]# </pre><div class="para">
- Output would indicate that the module is already loaded into the kernel, in which case you must first unload it before proceeding. See <a class="xref" href="sec-Unloading_a_Module.html">Section 21.4, “Unloading a Module”</a> for instructions on safely unloading it.
+ Output would indicate that the module is already loaded into the kernel, in which case you must first unload it before proceeding. See <a class="xref" href="sec-Unloading_a_Module.html">Section 22.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 turn on debug, you would run, as <code class="systemitem">root</code>:
</div><pre class="screen">~]# <code class="command">modprobe e1000e InterruptThrottleRate=3000,3000,3000 debug=1</code>
</pre><div class="para">
This example illustrates passing multiple values to a single parameter by separating them with commas and omitting any spaces between them.
- </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Unloading_a_Module.html"><strong>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>
\ No newline at end of file
+ </div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Unloading_a_Module.html"><strong>Prev</strong>22.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>22.6. Persistent Module Loading</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Setting_Printer.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Setting_Printer.html
index 6b21ee3..dcd460d 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Setting_Printer.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Setting_Printer.html
@@ -6,16 +6,16 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Printer_Configuration.html" title="12.3. Printer Configuration" /><link rel="prev" href="sec-Printer_Configuration.html" title="12.3. Printer Configuration" /><link rel="next" href="sec-Adding_Other_Printer.html" title="12.3.3. Adding a Local Printer" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Printer_Configuration.html"><strong>Prev</strong></
a></li><li class="next"><a accesskey="n" href="sec-Adding_Other_Printer.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Setting_Printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.2. Starting Printer Setup</h3></div></div></div><a id="idm225463446688" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Printer_Configuration.html" title="12.3. Printer Configuration" /><link rel="prev" href="sec-Printer_Configuration.html" title="12.3. Printer Configuration" /><link rel="next" href="sec-Adding_Other_Printer.html" title="12.3.3. Adding a Local Printer" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Printer_Configuration.html"><strong>Prev</strong></
a></li><li class="next"><a accesskey="n" href="sec-Adding_Other_Printer.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Setting_Printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.2. Starting Printer Setup</h3></div></div></div><a id="idm261746487728" class="indexterm"></a><div class="para">
Printer setup process varies depending on the printer queue type.
</div><div class="para">
- If you are setting up a local printer connected with USB, the printer is discovered and added automatically. You will be prompted to confirm the packages to be installed and provide the <code class="systemitem">root</code> password. Local printers connected with other port types and network printers need to be set up manually.
+ If you are setting up a local printer connected with USB, the printer is discovered and added automatically. You will be prompted to confirm the packages to be installed and provide an administrator or the <code class="systemitem">root</code> user password. Local printers connected with other port types and network printers need to be set up manually.
</div><div class="procedure" id="proc-Setting_up_Printer"><div class="para">
Follow this procedure to start a manual printer setup:
</div><ol class="1"><li class="step"><div class="para">
- Start the Printer configuration tool (refer to <a class="xref" href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">Section 12.3.1, “Starting the Printer Configuration Tool”</a>).
+ Start the Printers configuration tool (refer to <a class="xref" href="sec-Printer_Configuration.html#sec-Starting_Printer_Config">Section 12.3.1, “Starting the Printers Configuration Tool”</a>).
</div></li><li class="step"><div class="para">
- In the <span class="guilabel"><strong>Authentication Required</strong></span> box, type the root user password and confirm.
+ Select <span class="guimenuitem"><strong>Unlock</strong></span> to enable changes to be made. In the <span class="guilabel"><strong>Authentication Required</strong></span> box, type an administrator or the <code class="systemitem">root</code> user password and confirm.
</div></li><li class="step"><div class="para">
Select the plus sign to open the <span class="guimenuitem"><strong>Add a New Printer</strong></span> dialog. Select the printer from the list or enter its address below.
</div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Printer_Configuration.html"><strong>Prev</strong>12.3. Printer 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="sec-Adding_Other_Printer.html"><strong>Next</strong>12.3.3. Adding a Local Printer</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Setting_repository_Options.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Setting_repository_Options.html
index 546a6a5..ba5fc71 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Setting_repository_Options.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Setting_repository_Options.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="5.3. Configuring Yum and Yum Repositories" /><link rel="prev" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="5.3. Configuring Yum and Yum Repositories" /><link rel="next" href="sec-Using_Yum_Variables.html" title="5.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="se
c-Configuring_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">5.3.2. Setting [repository] Options</h3></div></div></div><a id="idm225453353424" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="5.3. Configuring Yum and Yum Repositories" /><link rel="prev" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="5.3. Configuring Yum and Yum Repositories" /><link rel="next" href="sec-Using_Yum_Variables.html" title="5.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="se
c-Configuring_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">5.3.2. Setting [repository] Options</h3></div></div></div><a id="idm261739836608" class="indexterm"></a><div class="para">
The <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> sections, where <em class="replaceable"><code>repository</code></em> is a unique repository ID such as <code class="literal">my_personal_repo</code> (spaces are not permitted), allow you to define individual Yum repositories.
</div><div class="para">
The following is a bare-minimum example of the form a <code class="literal">[<em class="replaceable"><code>repository</code></em>]</code> section takes:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Starting_ptp4l.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Starting_ptp4l.html
index 005cb7e..f0e03c7 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Starting_ptp4l.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Starting_ptp4l.html
@@ -7,6 +7,12 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
</script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Using_PTP.html" title="15.2. Using PTP" /><link rel="prev" href="sec-Installing_PTP.html" title="15.2.2. Installing PTP" /><link rel="next" href="sec-Specifying_a_Configuration_File.html" title="15.3. Specifying a Configuration File" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Installing_PTP.html"><strong>Prev</strong></a></li><li class="next"><
a accesskey="n" href="sec-Specifying_a_Configuration_File.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Starting_ptp4l"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.2.3. Starting ptp4l</h3></div></div></div><div class="para">
+ The <span class="application"><strong>ptp4l</strong></span> program can be started from the command line or it can be started as a service. When running as a service, options are specified in the <code class="filename">/etc/sysconfig/ptp4l</code> file. Options required for use both by the service and on the command line should be specified in the <code class="filename">/etc/ptp4l.conf</code> file. The <code class="filename">/etc/sysconfig/ptp4l</code> file includes the <code class="command">-f /etc/ptp4l.conf</code> command line option, which causes the <code class="systemitem">ptp4l</code> program to read the <code class="filename">/etc/ptp4l.conf</code> file and process the options it contains. The use of the <code class="filename">/etc/ptp4l.conf</code> is explained in <a class="xref" href="sec-Specifying_a_Configuration_File.html">Section 15.3, “Specifying a Configuration File”</a>. More information on the different <span class="application"><strong>ptp4l</stron
g></span> options and the configuration file settings can be found in the <code class="filename">ptp4l(8)</code> man page.
+ </div><h4 id="bh-Starting_ptp4l_as_a_Service">Starting ptp4l as a Service</h4><div class="para">
+ To start <span class="application"><strong>ptp4l</strong></span> as a service, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl start ptp4l</code></pre>
+
+ </div><h4 id="bh-Using_ptp4l_From_The_Command_Line">Using ptp4l From The Command Line</h4><div class="para">
The <span class="application"><strong>ptp4l</strong></span> program tries to use hardware time stamping by default. To use <span class="application"><strong>ptp4l</strong></span> with hardware time stamping capable drivers and NICs, you must provide the network interface to use with the <code class="option">-i</code> option. Enter the following command as <code class="systemitem">root</code>:
<pre class="screen">~]# <code class="command">ptp4l -i <em class="replaceable"><code>em3</code></em> -m</code></pre>
Where <em class="replaceable"><code>em3</code></em> is the interface you want to configure. Below is example output from <span class="application"><strong>ptp4l</strong></span> when the <code class="systemitem">PTP</code> clock on the NIC is synchronized to a master:
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html
new file mode 100644
index 0000000..134e077
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.9. Synchronize to PTP or NTP Time Using timemaster</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Configuring_PTP_Using_ptp4l.html" title="Chapter 15. Configuring PTP Using ptp4l" /><link rel="prev" href="sec-Serving_NTP_Time_with_PTP.html" title="15.8. Serving NTP Time with PTP" /><link rel="next" href="sec-Understanding_the_timemaster_Configuration_File.html" title="15.9.2. Understanding the timemaster Configuration File" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous">
<a accesskey="p" href="sec-Serving_NTP_Time_with_PTP.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Understanding_the_timemaster_Configuration_File.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.9. Synchronize to PTP or NTP Time Using timemaster</h2></div></div></div><div class="para">
+ When there are multiple <code class="systemitem">PTP</code> domains available on the network, or fallback to <code class="systemitem">NTP</code> is needed, the <span class="application"><strong>timemaster</strong></span> program can be used to synchronize the system clock to all available time sources. The <code class="systemitem">PTP</code> time is provided by <span class="application"><strong>phc2sys</strong></span> and <span class="application"><strong>ptp4l</strong></span> via <em class="firstterm">shared memory driver</em> (<acronym class="acronym">SHM</acronym> reference clocks to <code class="systemitem">chronyd</code> or <code class="systemitem">ntpd</code> (depending on the <code class="systemitem">NTP</code> daemon that has been configured on the system). The <code class="systemitem">NTP</code> daemon can then compare all time sources, both <code class="systemitem">PTP</code> and <code class="systemitem">NTP</code>, and use the best sources to synchronize the sy
stem clock.
+ </div><div class="para">
+ On start, <span class="application"><strong>timemaster</strong></span> reads a configuration file that specifies the <code class="systemitem">NTP</code> and <code class="systemitem">PTP</code> time sources, checks which network interfaces have their own or share a <code class="systemitem">PTP</code> hardware clock (PHC), generates configuration files for <span class="application"><strong>ptp4l</strong></span> and <code class="systemitem">chronyd</code> or <code class="systemitem">ntpd</code>, and starts the <span class="application"><strong>ptp4l</strong></span>, <span class="application"><strong>phc2sys</strong></span>, and <code class="systemitem">chronyd</code> or <code class="systemitem">ntpd</code> processes as needed. It will remove the generated configuration files on exit. It writes configuration files for <code class="systemitem">chronyd</code>, <code class="systemitem">ntpd</code>, and <span class="application"><strong>ptp4l</strong></span> to <code class="filen
ame">/var/run/timemaster/</code>.
+ </div><div class="section" id="sec-Starting_timemaster_as_a_Service"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.9.1. Starting timemaster as a Service</h3></div></div></div><div class="para">
+ To start <span class="application"><strong>timemaster</strong></span> as a service, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl start timemaster</code></pre>
+ This will read the options in <code class="filename"> /etc/timemaster.conf</code>.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Serving_NTP_Time_with_PTP.html"><strong>Prev</strong>15.8. Serving NTP Time with PTP</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-Understanding_the_timemaster_Configuration_File.html"><strong>Next</strong>15.9.2. Understanding the timemaster Configuratio...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Synchronizing_the_Clocks.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Synchronizing_the_Clocks.html
index 88ba6b4..1dc8f65 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Synchronizing_the_Clocks.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Synchronizing_the_Clocks.html
@@ -7,7 +7,17 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
</script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Configuring_PTP_Using_ptp4l.html" title="Chapter 15. Configuring PTP Using ptp4l" /><link rel="prev" href="sec-Using_the_PTP_Management_Client.html" title="15.4. Using the PTP Management Client" /><link rel="next" href="sec-Verifying_Time_Synchronization.html" title="15.6. Verifying Time Synchronization" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s
ec-Using_the_PTP_Management_Client.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Verifying_Time_Synchronization.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Synchronizing_the_Clocks"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">15.5. Synchronizing the Clocks</h2></div></div></div><div class="para">
- The <span class="application"><strong>phc2sys</strong></span> program is used to synchronize the system clock to the <code class="systemitem">PTP</code> hardware clock (<acronym class="acronym">PHC</acronym>) on the NIC. To start <span class="application"><strong>phc2sys</strong></span>, where <em class="replaceable"><code>em3</code></em> is the interface with the <code class="systemitem">PTP</code> hardware clock, enter the following command as <code class="systemitem">root</code>:
+ The <span class="application"><strong>phc2sys</strong></span> program is used to synchronize the system clock to the <code class="systemitem">PTP</code> hardware clock (<acronym class="acronym">PHC</acronym>) on the NIC. The <span class="application"><strong>phc2sys</strong></span> service is configured in the <code class="filename">/etc/sysconfig/phc2sys</code> configuration file. The default setting in the <code class="filename">/etc/sysconfig/phc2sys</code> file is as follows: <pre class="synopsis">OPTIONS="-a -r"</pre> The <code class="option">-a</code> option causes <span class="application"><strong>phc2sys</strong></span> to read the clocks to be synchronized from the <span class="application"><strong>ptp4l</strong></span> application. It will follow changes in the <code class="systemitem">PTP</code> port states, adjusting the synchronization between the NIC hardware clocks accordingly. The system clock is not synchronized, unless the <code class="option">-r</code>
option is also specified. If you want the system clock to be eligible to become a time source, specify the <code class="option">-r</code> option twice.
+ </div><div class="para">
+ After making changes to <code class="filename">/etc/sysconfig/phc2sys</code>, restart the <span class="application"><strong>phc2sys</strong></span> service from the command line by issuing a command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">systemctl restart phc2sys</code></pre>
+ Under normal circumstances, use <code class="command">systemctl</code> commands to start, stop, and restart the <span class="application"><strong>phc2sys</strong></span> service.
+ </div><div class="para">
+ When you do not want to start <span class="application"><strong>phc2sys</strong></span> as a service, you can start it from the command line. For example, enter the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">phc2sys -a -r</code></pre>
+ The <code class="option">-a</code> option causes <span class="application"><strong>phc2sys</strong></span> to read the clocks to be synchronized from the <span class="application"><strong>ptp4l</strong></span> application. If you want the system clock to be eligible to become a time source, specify the <code class="option">-r</code> option twice.
+ </div><div class="para">
+ Alternately, use the <code class="option">-s</code> option to synchronize the system clock to a specific interface's <code class="systemitem">PTP</code> hardware clock. For example:
<pre class="screen">~]# <code class="command">phc2sys -s <em class="replaceable"><code>em3</code></em> -w</code></pre>
The <code class="option">-w</code> option waits for the running <span class="application"><strong>ptp4l</strong></span> application to synchronize the <code class="systemitem">PTP</code> clock and then retrieves the <acronym class="acronym">TAI</acronym> to <acronym class="acronym">UTC</acronym> offset from <span class="application"><strong>ptp4l</strong></span>.
</div><div class="para">
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Terminal_Menu_Editing_During_Boot.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Terminal_Menu_Editing_During_Boot.html
new file mode 100644
index 0000000..d6b5519
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Terminal_Menu_Editing_During_Boot.html
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.6. Terminal Menu Editing During Boot</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="Chapter 20. Working with the GRUB 2 Boot Loader" /><link rel="prev" href="sec-Using_screen_to_Connect_to_the_Serial_Console.html" title="20.5.2. Using screen to Connect to the Serial Console" /><link rel="next" href="sec-Booting_to_Emergency_Mode.html" title="20.6.2. Booting to Emergency Mode" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li cla
ss="previous"><a accesskey="p" href="sec-Using_screen_to_Connect_to_the_Serial_Console.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Booting_to_Emergency_Mode.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Terminal_Menu_Editing_During_Boot"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.6. Terminal Menu Editing During Boot</h2></div></div></div><div class="para">
+ Menu entries can be modified and arguments passed to the kernel on boot. This is done using the menu entry editor interface, which is triggered when pressing the <span class="keycap"><strong>e</strong></span> key on a selected menu entry in the boot loader menu. The <span class="keycap"><strong>Esc</strong></span> key discards any changes and reloads the standard menu interface. The <span class="keycap"><strong>c</strong></span> key loads the command line interface.
+ </div><div class="para">
+ The command line interface is the most basic GRUB interface, but it is also the one that grants the most control. The command line makes it possible to type any relevant GRUB commands followed by the <span class="keycap"><strong>Enter</strong></span> key to execute them. This interface features some advanced features similar to <span class="application"><strong>shell</strong></span>, including <span class="keycap"><strong>Tab</strong></span> key completion based on context, and <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>a</strong></span> to move to the beginning of a line and <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>e</strong></span> to move to the end of a line. In addition, the <span class="keycap"><strong>arrow</strong></span>, <span class="keycap"><strong>Home</strong></span>, <span class="keycap"><strong>End</strong></span>, and <span class="keycap"><strong>Delete</strong></span> keys work as t
hey do in the bash shell.
+ </div><div class="section" id="sec-Booting_to_Rescue_Mode"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.6.1. Booting to Rescue Mode</h3></div></div></div><div class="para">
+ Rescue mode provides a convenient single-user environment and allows you to repair your system in situations when it is unable to complete a normal booting process. In rescue mode, the system attempts to mount all local file systems and start some important system services, but it does not activate network interfaces or allow more users to be logged into the system at the same time. In Fedora, rescue mode is equivalent to single user mode and requires the <code class="systemitem">root</code> password.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ To enter rescue mode during boot, on the GRUB 2 boot screen, press the <span class="keycap"><strong>e</strong></span> key for edit.
+ </div></li><li class="step"><div class="para">
+ Add the following parameter at the end of the <code class="literal">linux</code> line on 64-Bit IBM Power Series, the <code class="literal">linux16</code> line on x86-64 BIOS-based systems, or the <code class="literal">linuxefi</code> line on UEFI systems:
+ </div><pre class="screen">systemd.unit=rescue.target</pre><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>a</strong></span> and <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>e</strong></span> to jump to the start and end of the line, respectively. On some systems, <span class="keycap"><strong>Home</strong></span> and <span class="keycap"><strong>End</strong></span> might also work.
+ </div><div class="para">
+ Note that equivalent parameters, <em class="parameter"><code>1</code></em>, <em class="parameter"><code>s</code></em>, and <em class="parameter"><code>single</code></em>, can be passed to the kernel as well.
+ </div></li><li class="step"><div class="para">
+ Press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>x</strong></span> to boot the system with the parameter.
+ </div></li></ol></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Using_screen_to_Connect_to_the_Serial_Console.html"><strong>Prev</strong>20.5.2. Using screen to Connect to the Serial Con...</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-Booting_to_Emergency_Mode.html"><strong>Next</strong>20.6.2. Booting to Emergency Mode</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-UEFI_Secure_Boot.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-UEFI_Secure_Boot.html
new file mode 100644
index 0000000..4690003
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-UEFI_Secure_Boot.html
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.7. UEFI Secure Boot</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="Chapter 20. Working with the GRUB 2 Boot Loader" /><link rel="prev" href="sec-Changing_and_Resetting_the_Root_Password.html" title="20.6.3. Changing and Resetting the Root Password" /><link rel="next" href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html" title="20.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="d
ocnav"><li class="previous"><a accesskey="p" href="sec-Changing_and_Resetting_the_Root_Password.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-UEFI_Secure_Boot"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.7. UEFI Secure Boot</h2></div></div></div><div class="para">
+ The Secure Boot technology ensures that the system firmware checks whether the system boot loader is signed with a cryptographic key authorized by a database contained in the firmware. With signature verification in the next-stage boot loader, kernel, and, potentially, user space, it is possible to prevent the execution of unsigned code.
+ </div><div class="para">
+ Secure Boot is the boot path validation component of the Unified Extensible Firmware Interface (UEFI) specification. The specification defines:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ a programming interface for cryptographically protected UEFI variables in non-volatile storage,
+ </div></li><li class="listitem"><div class="para">
+ how the trusted X.509 root certificates are stored in UEFI variables,
+ </div></li><li class="listitem"><div class="para">
+ validation of UEFI applications like boot loaders and drivers,
+ </div></li><li class="listitem"><div class="para">
+ procedures to revoke known-bad certificates and application hashes.
+ </div></li></ul></div><div class="para">
+ UEFI Secure Boot does not prevent the installation or removal of second-stage boot loaders, nor require explicit user confirmation of such changes. Signatures are verified during booting, not when the boot loader is installed or updated. Therefore, UEFI Secure Boot does not stop boot path manipulations, it simplifies the detection of changes and prevents the system from executing a modified boot path once such a modification has occurred.
+ </div><div class="section" id="sec-UEFI_Secure_Boot_Support_in_Fedora"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.7.1. UEFI Secure Boot Support in Fedora</h3></div></div></div><div class="para">
+ Fedora includes support for the UEFI Secure Boot feature, which means that Fedora can be installed and run on systems where UEFI Secure Boot is enabled. On UEFI-based systems with the Secure Boot technology enabled, all drivers that are loaded must be signed with a valid certificate, otherwise the system will not accept them. All drivers provided by Red Hat are signed by the UEFI CA certificate.
+ </div><div class="para">
+ If you want to load externally built drivers — drivers that are not provided on the Fedora Linux DVD — you must make sure these drivers are signed as well.
+ </div><div class="para">
+
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Changing_and_Resetting_the_Root_Password.html"><strong>Prev</strong>20.6.3. Changing and Resetting the Root Password</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-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html"><strong>Next</strong>20.8. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Understanding_the_timemaster_Configuration_File.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Understanding_the_timemaster_Configuration_File.html
new file mode 100644
index 0000000..790be03
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Understanding_the_timemaster_Configuration_File.html
@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>15.9.2. Understanding the timemaster Configuration File</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html" title="15.9. Synchronize to PTP or NTP Time Using timemaster" /><link rel="prev" href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html" title="15.9. Synchronize to PTP or NTP Time Using timemaster" /><link rel="next" href="sec-Configuring_timemaster_Options.html" title="15.9.3. Configuring timemaster Options" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a>
</p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Configuring_timemaster_Options.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Understanding_the_timemaster_Configuration_File"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">15.9.2. Understanding the timemaster Configuration File</h3></div></div></div><div class="para">
+ Fedora provides a default <code class="filename">/etc/timemaster.conf</code> file with a number of sections containing default options. The section headings are enclosed in brackets.
+ </div><div class="para">
+ To view the default configuration, issue a command as follows:
+<pre class="screen">~]$ <code class="command">less /etc/timemaster.conf</code>
+# Configuration file for timemaster
+
+#[ntp_server ntp-server.local]
+#minpoll 4
+#maxpoll 4
+
+#[ptp_domain 0]
+#interfaces eth0
+
+[timemaster]
+ntp_program chronyd
+
+[chrony.conf]
+include /etc/chrony.conf
+
+[ntp.conf]
+includefile /etc/ntp.conf
+
+[ptp4l.conf]
+
+[chronyd]
+path /usr/sbin/chronyd
+options -u chrony
+
+[ntpd]
+path /usr/sbin/ntpd
+options -u ntp:ntp -g
+
+[phc2sys]
+path /usr/sbin/phc2sys
+
+[ptp4l]
+path /usr/sbin/ptp4l</pre>
+ </div><div class="para">
+ Notice the section named as follows: <pre class="synopsis">[ntp_server <em class="replaceable"><code>address</code></em>]</pre> This is an example of an <code class="systemitem">NTP</code> server section, <span class="quote">“<span class="quote">ntp-server.local</span>”</span> is an example of a host name for an <code class="systemitem">NTP</code> server on the local LAN. Add more sections as required using a host name or <code class="systemitem">IP</code> address as part of the section name. Note that the short polling values in that example section are not suitable for a public server, see <a class="xref" href="ch-Configuring_NTP_Using_ntpd.html">Chapter 14, <em>Configuring NTP Using ntpd</em></a> for an explanation of suitable <code class="option">minpoll</code> and <code class="option">maxpoll</code> values.
+ </div><div class="para">
+ Notice the section named as follows: <pre class="synopsis">[ptp_domain <em class="replaceable"><code>number</code></em>]</pre> A <span class="quote">“<span class="quote">PTP domain</span>”</span> is a group of one or more <code class="systemitem">PTP</code> clocks that synchronize to each other. They may or may not be synchronized to clocks in another domain. Clocks that are configured with the same domain number make up the domain. This includes a <code class="systemitem">PTP</code> grandmaster clock. The domain number in each <span class="quote">“<span class="quote">PTP domain</span>”</span> section needs to correspond to one of the <code class="systemitem">PTP</code> domains configured on the network.
+ </div><div class="para">
+ An instance of <span class="application"><strong>ptp4l</strong></span> is started for every interface which has its own <code class="systemitem">PTP</code> clock and hardware time stamping is enabled automatically. Interfaces that support hardware time stamping have a <code class="systemitem">PTP</code> clock (PHC) attached, however it is possible for a group of interfaces on a NIC to share a PHC. A separate <span class="application"><strong>ptp4l</strong></span> instance will be started for each group of interfaces sharing the same PHC and for each interface that supports only software time stamping. All <span class="application"><strong>ptp4l</strong></span> instances are configured to run as a slave. If an interface with hardware time stamping is specified in more than one <code class="systemitem">PTP</code> domain, then only the first <span class="application"><strong>ptp4l</strong></span> instance created will have hardware time stamping enabled.
+ </div><div class="para">
+ Notice the section named as follows: <pre class="synopsis">[timemaster]</pre> The default <span class="application"><strong>timemaster</strong></span> configuration includes the system <code class="systemitem">ntpd</code> and chrony configuration (<code class="filename">/etc/ntp.conf</code> or <code class="filename">/etc/chronyd.conf</code>) in order to include the configuration of access restrictions and authentication keys. That means any <code class="systemitem">NTP</code> servers specified there will be used with <span class="application"><strong>timemaster</strong></span> too.
+ </div><div class="para">
+ The section headings are as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="option">[ntp_server ntp-server.local]</code> — Specify polling intervals for this server. Create additional sections as required. Include the host name or <code class="systemitem">IP</code> address in the section heading.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[ptp_domain 0]</code> — Specify interfaces that have <code class="systemitem">PTP</code> clocks configured for this domain. Create additional sections with, the appropriate domain number, as required.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[timemaster]</code> — Specify the <code class="systemitem">NTP</code> daemon to be used. Possible values are <code class="systemitem">chronyd</code> and <code class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[chrony.conf]</code> — Specify any additional settings to be copied to the configuration file generated for <code class="systemitem">chronyd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[ntp.conf]</code> — Specify any additional settings to be copied to the configuration file generated for <code class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[ptp4l.conf]</code> — Specify options to be copied to the configuration file generated for <span class="application"><strong>ptp4l</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[chronyd]</code> — Specify any additional settings to be passed on the command line to <code class="systemitem">chronyd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[ntpd]</code> — Specify any additional settings to be passed on the command line to <code class="systemitem">ntpd</code>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[phc2sys]</code> — Specify any additional settings to be passed on the command line to <span class="application"><strong>phc2sys</strong></span>.
+ </div></li><li class="listitem"><div class="para">
+ <code class="option">[ptp4l]</code> — Specify any additional settings to be passed on the command line to all instances of <span class="application"><strong>ptp4l</strong></span>.
+ </div></li></ul></div><div class="para">
+ The section headings and there contents are explained in detail in the <code class="filename">timemaster(8)</code> manual page.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Synchronize_to_PTP_or_NTP_Time_Using_timemaster.html"><strong>Prev</strong>15.9. Synchronize to PTP or NTP Time Using timema...</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_timemaster_Options.html"><strong>Next</strong>15.9.3. Configuring timemaster Options</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Unloading_a_Module.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Unloading_a_Module.html
index 3ebe1bd..a880439 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Unloading_a_Module.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Unloading_a_Module.html
@@ -1,12 +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.4. Unloading a Module</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.4. Unloading a Module</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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">21.4. Unloading a Module</h2></div></div></div><a id="idm225468318048" class="indexterm"></a><a id="idm225468316608" class="indexterm"></a><a id="idm225468314528" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="prev" href="sec-Loading_a_Module.html" title="22.3. Loading a Module" /><link rel="next" href="sec-Setting_Module_Parameters.html" title="22.5. Setting Module Parameters" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Loading_a_Module.html"><strong>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">22.4. Unloading a Module</h2></div></div></div><a id="idm261750618384" class="indexterm"></a><a id="idm261750616944" class="indexterm"></a><a id="idm261737069088" 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">
@@ -18,8 +18,8 @@
</div></li><li class="listitem"><div class="para">
any module that <code class="systemitem">wacom</code>, through the dependency tree, depends on indirectly.
</div></li></ul></div><div class="para">
- See <a class="xref" href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">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">
+ See <a class="xref" href="ch-Working_with_Kernel_Modules.html#sec-Listing_Currently-Loaded_Modules">Section 22.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 22.4. Unloading a kernel module</h6><div class="example-contents"><div class="para">
For example, if you want to unload the <code class="systemitem">firewire_ohci</code> module, your terminal session might look similar to this:
</div><pre class="screen">~]# <code class="command">modinfo -F depends firewire_ohci</code>
firewire-core
@@ -36,6 +36,6 @@ rmmod firewire_ohci
rmmod firewire_core
rmmod crc_itu_t</pre><div class="para">
The output shows that modules are unloaded in the reverse order that they are loaded, given that no processes depend on any of the modules being unloaded.
- </div></div></div><br class="example-break" /><a id="idm225464480336" class="indexterm"></a><a id="idm225464478256" 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">
+ </div></div></div><br class="example-break" /><a id="idm261752405584" class="indexterm"></a><a id="idm261785242576" 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>
\ No newline at end of file
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Loading_a_Module.html"><strong>Prev</strong>22.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>22.5. Setting Module Parameters</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Using_PTP.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Using_PTP.html
index 1aab9c8..59a4a52 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Using_PTP.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Using_PTP.html
@@ -26,7 +26,7 @@ Hardware Transmit Timestamp Modes:
Hardware Receive Filter Modes:
none (HWTSTAMP_FILTER_NONE)
all (HWTSTAMP_FILTER_ALL)</pre>
- Where <em class="replaceable"><code>eth3</code></em> is the interface you want to check.
+ Where <em class="replaceable"><code>em3</code></em> is the interface you want to check.
</div><div class="para">
For software time stamping support, the parameters list should include:
<div class="itemizedlist"><ul><li class="listitem"><div class="para">
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Using_Yum_Variables.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Using_Yum_Variables.html
index f8bc2e1..8ffc63d 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Using_Yum_Variables.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Using_Yum_Variables.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="5.3. Configuring Yum and Yum Repositories" /><link rel="prev" href="sec-Setting_repository_Options.html" title="5.3.2. Setting [repository] Options" /><link rel="next" href="sec-Viewing_the_Current_Configuration.html" title="5.3.4. Viewing the Current Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey=
"p" href="sec-Setting_repository_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Viewing_the_Current_Configuration.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">5.3.3. Using Yum Variables</h3></div></div></div><a id="idm225505594016" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Configuring_Yum_and_Yum_Repositories.html" title="5.3. Configuring Yum and Yum Repositories" /><link rel="prev" href="sec-Setting_repository_Options.html" title="5.3.2. Setting [repository] Options" /><link rel="next" href="sec-Viewing_the_Current_Configuration.html" title="5.3.4. Viewing the Current Configuration" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey=
"p" href="sec-Setting_repository_Options.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Viewing_the_Current_Configuration.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">5.3.3. Using Yum Variables</h3></div></div></div><a id="idm261726697632" 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 Yum 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 class="variablelist"><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. Yum 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.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Using_only_a_Custom_Menu.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Using_only_a_Custom_Menu.html
new file mode 100644
index 0000000..81d9fd4
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Using_only_a_Custom_Menu.html
@@ -0,0 +1,79 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.2.4. Creating a Custom Menu</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Customizing_GRUB_2_Menu.html" title="20.2. Customizing GRUB 2 Menu" /><link rel="prev" href="sec-Adding_a_new_Entry.html" title="20.2.3. Adding a new Entry" /><link rel="next" href="sec-GRUB_2_Password_Protection.html" title="20.3. GRUB 2 Password Protection" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Adding_a_new_Entry.html"><strong>Prev</stro
ng></a></li><li class="next"><a accesskey="n" href="sec-GRUB_2_Password_Protection.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Using_only_a_Custom_Menu"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.2.4. Creating a Custom Menu</h3></div></div></div><div class="para">
+ If you do not want menu entries to be updated automatically, you can create a custom menu.
+ </div><div class="important"><div class="admonition_header"><h2>Important</h2></div><div class="admonition"><div class="para">
+ Before proceeding, back up the contents of the <code class="filename">/etc/grub.d/</code> directory in case you need to revert the changes later.
+ </div></div></div><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that modifying the <code class="filename">/etc/default/grub</code> file does not have any effect on creating custom menus.
+ </div></div></div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ On BIOS-based machines, copy the contents of <code class="filename">/boot/grub2/grub.cfg</code>, or, on UEFI machines, copy the contents of <code class="filename">/boot/efi/EFI/redhat/grub.cfg</code>. Put the content of the <code class="filename">grub.cfg</code> into the <code class="filename">/etc/grub.d/40_custom</code> file below the existing header lines. The executable part of the <code class="filename">40_custom</code> script has to be preserved.
+ </div></li><li class="step"><div class="para">
+ From the content put into the <code class="filename">/etc/grub.d/40_custom</code> file, only the <code class="literal">menuentry</code> blocks are needed to create the custom menu. The <code class="filename">/boot/grub2/grub.cfg</code> and <code class="filename">/boot/efi/EFI/redhat/grub.cfg</code> files might contain function specifications and other content above and below the <code class="literal">menuentry</code> blocks. If you put these unnecessary lines into the <code class="filename">40_custom</code> file in the previous step, erase them.
+ </div><div class="para">
+ This is an example of a custom <code class="filename">40_custom</code> script:
+ </div><pre class="programlisting"><span class="perl_Comment">#!/bin/sh</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span><span class="perl_Reserved">exec</span> <span class="perl_BString">tail</span> -n +3 <span class="perl_Others">$0</span>
+<span class="perl_Comment"># This file provides an easy way to add custom menu entries. Simply type the</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span><span class="perl_Comment"># menu entries you want to add after this comment. Be careful not to change</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span><span class="perl_Comment"># the 'exec tail' line above.</span><span class="perl_Comment"></span>
+<span class="perl_Comment"></span>
+menuentry <span class="perl_String">'First custom entry'</span> --class <span class="perl_BString">red</span> --class gnu-linux --class gnu --class os <span class="perl_Others">$menuentry_id_option</span> <span class="perl_String">'gnulinux-3.10.0-67.el7.x86_64-advanced-32782dd0-4b47-4d56-a740-2076ab5e5976'</span> <span class="perl_Keyword">{</span>
+ load_video
+ <span class="perl_Keyword">set</span> <span class="perl_Others">gfxpayload=</span>keep
+ insmod gzio
+ insmod part_msdos
+ insmod xfs
+ <span class="perl_Keyword">set</span> <span class="perl_Others">root=</span><span class="perl_String">'hd0,msdos1'</span>
+ <span class="perl_Keyword">if</span><span class="perl_Reserved"> [</span> x<span class="perl_Others">$feature_platform_search_hint</span> = xy<span class="perl_Reserved"> ]</span>; <span class="perl_Keyword">then</span>
+ search --no-floppy --fs-uuid --set=root --hint=<span class="perl_String">'hd0,msdos1'</span> 7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">else</span>
+ search --no-floppy --fs-uuid --set=root 7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">fi</span>
+ linux16 /vmlinuz-3.10.0-67.el7.x86_64 <span class="perl_Others">root=</span>/dev/mapper/rhel-root ro rd.lvm.<span class="perl_Others">lv=</span>rhel/root vconsole.<span class="perl_Others">font=</span>latarcyrheb-sun16 rd.lvm.<span class="perl_Others">lv=</span>rhel/swap vconsole.<span class="perl_Others">keymap=</span>us <span class="perl_Others">crashkernel=</span>auto rhgb quiet <span class="perl_Others">LANG=</span>en_US.UTF-8
+ initrd16 /initramfs-3.10.0-67.el7.x86_64.img
+<span class="perl_Keyword">}</span>
+menuentry <span class="perl_String">'Second custom entry'</span> --class <span class="perl_BString">red</span> --class gnu-linux --class gnu --class os <span class="perl_Others">$menuentry_id_option</span> <span class="perl_String">'gnulinux-0-rescue-07f43f20a54c4ce8ada8b70d33fd001c-advanced-32782dd0-4b47-4d56-a740-2076ab5e5976'</span> <span class="perl_Keyword">{</span>
+ load_video
+ insmod gzio
+ insmod part_msdos
+ insmod xfs
+ <span class="perl_Keyword">set</span> <span class="perl_Others">root=</span><span class="perl_String">'hd0,msdos1'</span>
+ <span class="perl_Keyword">if</span><span class="perl_Reserved"> [</span> x<span class="perl_Others">$feature_platform_search_hint</span> = xy<span class="perl_Reserved"> ]</span>; <span class="perl_Keyword">then</span>
+ search --no-floppy --fs-uuid --set=root --hint=<span class="perl_String">'hd0,msdos1'</span> 7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">else</span>
+ search --no-floppy --fs-uuid --set=root 7885bba1-8aa7-4e5d-a7ad-821f4f52170a
+ <span class="perl_Keyword">fi</span>
+ linux16 /vmlinuz-0-rescue-07f43f20a54c4ce8ada8b70d33fd001c <span class="perl_Others">root=</span>/dev/mapper/rhel-root ro rd.lvm.<span class="perl_Others">lv=</span>rhel/root vconsole.<span class="perl_Others">font=</span>latarcyrheb-sun16 rd.lvm.<span class="perl_Others">lv=</span>rhel/swap vconsole.<span class="perl_Others">keymap=</span>us <span class="perl_Others">crashkernel=</span>auto rhgb quiet
+ initrd16 /initramfs-0-rescue-07f43f20a54c4ce8ada8b70d33fd001c.img
+<span class="perl_Keyword">}</span></pre></li><li class="step"><div class="para">
+ Remove all files from the <code class="filename">/etc/grub.d</code> directory except the following:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">00_header</code>,
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">40_custom</code>,
+ </div></li><li class="listitem"><div class="para">
+ <code class="filename">01_users</code> (if it exists),
+ </div></li><li class="listitem"><div class="para">
+ and <code class="filename">README</code>.
+ </div></li></ul></div><div class="para">
+ Alternatively, if you want to keep the files in the <code class="filename">/etc/grub2.d/</code> directory, make them unexecutable by running the <code class="command">chmod <code class="option">a-x</code> <file_name></code> command.
+ </div></li><li class="step"><div class="para">
+ Edit, add, or remove menu entries in the <code class="filename">40_custom</code> file as desired.
+ </div></li><li class="step"><div class="para">
+ Update the <code class="filename">grub.cfg</code> file by running the <code class="command">grub2-mkconfig <code class="option">-o</code></code> command as follows:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ On BIOS-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/grub2/grub.cfg</code></pre>
+
+ </div></li><li class="listitem"><div class="para">
+ On UEFI-based machines, issue the following command as <code class="systemitem">root</code>:
+<pre class="screen">~]# <code class="command">grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg</code></pre>
+
+ </div></li></ul></div></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Adding_a_new_Entry.html"><strong>Prev</strong>20.2.3. Adding a new Entry</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-GRUB_2_Password_Protection.html"><strong>Next</strong>20.3. GRUB 2 Password Protection</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Using_screen_to_Connect_to_the_Serial_Console.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Using_screen_to_Connect_to_the_Serial_Console.html
new file mode 100644
index 0000000..8db7aa9
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Using_screen_to_Connect_to_the_Serial_Console.html
@@ -0,0 +1,19 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.5.2. Using screen to Connect to the Serial Console</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-GRUB_2_over_Serial_Console.html" title="20.5. GRUB 2 over Serial Console" /><link rel="prev" href="sec-GRUB_2_over_Serial_Console.html" title="20.5. GRUB 2 over Serial Console" /><link rel="next" href="sec-Terminal_Menu_Editing_During_Boot.html" title="20.6. Terminal Menu Editing During Boot" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-GRUB_2_ov
er_Serial_Console.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sec-Terminal_Menu_Editing_During_Boot.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-Using_screen_to_Connect_to_the_Serial_Console"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">20.5.2. Using screen to Connect to the Serial Console</h3></div></div></div><div class="para">
+ The <span class="application"><strong>screen</strong></span> tool serves as a capable serial terminal. To install it, run as <code class="systemitem">root</code>:
+ </div><pre class="screen">~]# <code class="command">yum install screen</code></pre><div class="para">
+ To connect to your machine using the serial console, run the following command:
+ </div><pre class="screen">~]$ <code class="command">screen</code> <code class="filename">/dev/<console_port></code></pre><div class="para">
+ By default, if no option is specified, <span class="application"><strong>screen</strong></span> uses the standard 9600 baud rate. To set a different baud rate, run:
+ </div><pre class="screen">~]$ <code class="command">screen</code> <code class="filename">/dev/<console_port></code> <code class="option">115200</code></pre><div class="para">
+ To end the session in <span class="application"><strong>screen</strong></span>, press <span class="keycap"><strong>Ctrl</strong></span>+<span class="keycap"><strong>a</strong></span>, type <code class="literal">:quit</code> and press <span class="keycap"><strong>Enter</strong></span>.
+ </div><div class="para">
+ See the <code class="filename">screen(1)</code> manual page for additional options and detailed information.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-GRUB_2_over_Serial_Console.html"><strong>Prev</strong>20.5. GRUB 2 over Serial Console</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-Terminal_Menu_Editing_During_Boot.html"><strong>Next</strong>20.6. Terminal Menu Editing During Boot</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html
index a8bd73b..e8f83ec 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Verifying_the_Initial_RAM_Disk_Image.html
@@ -1,48 +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>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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/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. 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.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
addID('Fedora');
addID('Fedora.21');
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's 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"><s
trong>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">20.5. Verifying the Initial RAM Disk Image</h2></div></div></div><a id="idm225496635952" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 21. Manually Upgrading the Kernel" /><link rel="prev" href="s1-kernel-perform-upgrade.html" title="21.4. Performing the Upgrade" /><link rel="next" href="s1-kernel-boot-loader.html" title="21.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"><s
trong>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">21.5. Verifying the Initial RAM Disk Image</h2></div></div></div><a id="idm261756189456" 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 21 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">the section called “ Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i ”</a>), you can create an <code class="systemitem">initramfs</code> by running the <code class="command">dracut</code> command. However, you usually don't need to create an <code class="systemitem">initramfs</code> manually: this step is automatically performed if the kernel and its associated packages are installed or upgraded from RPM packages distributed by The Fedora Project.
</div><div class="para">
On architectures that use the GRUB 2 boot loader, you can verify that an <code class="systemitem">initramfs</code> corresponding to your current kernel version exists and is specified correctly in the <code class="filename">/boot/grub2/grub.cfg</code> configuration file by following this procedure:
- </div><div class="procedure" id="procedure-Verifying_the_Initial_RAM_Disk_Image"><h6>Procedure 20.1. Verifying the Initial RAM Disk Image</h6><ol class="1"><li class="step"><div class="para">
+ </div><div class="procedure" id="procedure-Verifying_the_Initial_RAM_Disk_Image"><h6>Procedure 21.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><div class="example" id="ex-Ensuring_that_the_kernel_and_initramfs_versions_match"><h6>Example 20.1. Ensuring that the kernel and initramfs versions match</h6><div class="example-contents"><pre class="screen">~]# <code class="command">ls /boot/</code>
-config-3.16.7-200.fc20.x86_64
-config-3.17.2-200.fc20.x86_64
-config-3.17.3-200.fc20.x86_64
+ </div><div class="example" id="ex-Ensuring_that_the_kernel_and_initramfs_versions_match"><h6>Example 21.1. Ensuring that the kernel and initramfs versions match</h6><div class="example-contents"><pre class="screen">~]# <code class="command">ls /boot/</code>
+config-3.17.4-302.fc21.x86_64
+config-3.17.6-300.fc21.x86_64
+config-3.17.7-300.fc21.x86_64
efi
elf-memtest86+-5.01
extlinux
grub2
-initramfs-0-rescue-d54d78fd40ab445a9556279010454c22.img
-initramfs-3.16.7-200.fc20.x86_64.img
-initramfs-3.17.2-200.fc20.x86_64.img
-initramfs-3.17.3-200.fc20.x86_64.img
+initramfs-0-rescue-db90b4e3715b42daa871351439343ca4.img
+initramfs-3.17.4-302.fc21.x86_64.img
+initramfs-3.17.6-300.fc21.x86_64.img
+initramfs-3.17.7-300.fc21.x86_64.img
initrd-plymouth.img
lost+found
memtest86+-5.01
-System.map-3.16.7-200.fc20.x86_64
-System.map-3.17.2-200.fc20.x86_64
-System.map-3.17.3-200.fc20.x86_64
-vmlinuz-0-rescue-d54d78fd40ab445a9556279010454c22
-vmlinuz-3.16.7-200.fc20.x86_64
-vmlinuz-3.17.2-200.fc20.x86_64
-vmlinuz-3.17.3-200.fc20.x86_64</pre></div></div><br class="example-break" /><div class="para">
- <a class="xref" href="sec-Verifying_the_Initial_RAM_Disk_Image.html#ex-Ensuring_that_the_kernel_and_initramfs_versions_match">Example 20.1, “Ensuring that the kernel and initramfs versions match”</a> shows that:
+System.map-3.17.4-302.fc21.x86_64
+System.map-3.17.6-300.fc21.x86_64
+System.map-3.17.7-300.fc21.x86_64
+vmlinuz-0-rescue-db90b4e3715b42daa871351439343ca4
+vmlinuz-3.17.4-302.fc21.x86_64
+vmlinuz-3.17.6-300.fc21.x86_64
+vmlinuz-3.17.7-300.fc21.x86_64</pre></div></div><br class="example-break" /><div class="para">
+ <a class="xref" href="sec-Verifying_the_Initial_RAM_Disk_Image.html#ex-Ensuring_that_the_kernel_and_initramfs_versions_match">Example 21.1, “Ensuring that the kernel and initramfs versions match”</a> shows that:
</div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
we have three kernels installed (or, more correctly, three kernel files are present in the <code class="filename">/boot/</code> directory),
</div></li><li class="listitem"><div class="para">
- the latest kernel is <code class="filename">vmlinuz-3.17.3-200.fc20.x86_64</code>, and
+ the latest kernel is <code class="filename">vmlinuz-3.17.7-300.fc21.x86_64</code>, and
</div></li><li class="listitem"><div class="para">
- an <code class="systemitem">initramfs</code> file matching our kernel version, <code class="filename">initramfs-3.17.3-200.fc20.x86_64.img</code>, also exists.
+ an <code class="systemitem">initramfs</code> file matching our kernel version, <code class="filename">initramfs-3.17.7-300.fc21.x86_64.img</code>, also exists.
</div></li></ul></div><div class="important" id="important-initrd_files_in_the__boot_directory_are_not_the_same_as_initramfs_files"><div class="admonition_header"><h2>initrd files in the /boot/ directory are not the same as initramfs files</h2></div><div class="admonition"><div class="para">
In the <code class="filename">/boot/</code> directory you might find several <code class="filename">initrd-<em class="replaceable"><code>kernel_version</code></em>kdump.img</code> files. These are special files created by the <code class="systemitem">kdump</code> mechanism for kernel debugging purposes, are not used to boot the system, and can safely be ignored. For more information on <code class="systemitem">kdump</code>, see the <a href="https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Kernel_Crash_Dump_Guide/">Red Hat Enterprise Linux 7 Kernel Crash Dump Guide</a>.
</div></div></div></li><li class="step"><div class="para">
@@ -50,26 +50,26 @@ vmlinuz-3.17.3-200.fc20.x86_64</pre></div></div><br class="example-break" /><div
</div><pre class="screen">~]# <code class="command">dracut</code></pre><div class="para">
You must use the <code class="option">--force</code> option if you want <code class="command">dracut</code> to overwrite an existing <code class="filename">initramfs</code> (for example, if your <code class="filename">initramfs</code> has become corrupt). Otherwise <code class="command">dracut</code> will refuse to overwrite the existing <code class="filename">initramfs</code> file:
</div><pre class="screen">~]# <code class="command">dracut</code>
-F: Will not override existing initramfs (/boot/initramfs-3.17.3-200.fc20.x86_64.img) without --force</pre><div class="para">
+F: Will not override existing initramfs (/boot/initramfs-3.17.7-300.fc21.x86_64.img) without --force</pre><div class="para">
You can create an initramfs in the current directory by calling <code class="command">dracut <em class="replaceable"><code>initramfs_name</code></em> <em class="replaceable"><code>kernel_version</code></em></code>, for example:
</div><pre class="screen">~]# <code class="command">dracut "initramfs-$(uname -r).img" $(uname -r)</code></pre><div class="para">
If you need to specify specific kernel modules to be preloaded, add the names of those modules (minus any file name suffixes such as <code class="filename">.ko</code>) inside the parentheses of the <code class="computeroutput">add_dracutmodules="<em class="replaceable"><code>module</code></em> [<span class="optional"><em class="replaceable"><code>more_modules</code></em></span>]"</code> directive of the <code class="filename">/etc/dracut.conf</code> configuration file. You can list the file contents of an <code class="filename">initramfs</code> image file created by dracut by using the <code class="command">lsinitrd <em class="replaceable"><code>initramfs_file</code></em></code> command:
- </div><pre class="screen">~]# <code class="command">lsinitrd /boot/initramfs-3.17.3-200.fc20.x86_64.img</code>
-Image: /boot/initramfs-3.17.3-200.fc20.x86_64.img: 18M
+ </div><pre class="screen">~]# <code class="command">lsinitrd /boot/initramfs-3.17.7-300.fc21.x86_64.img</code>
+Image: /boot/initramfs-3.17.7-300.fc21.x86_64.img: 18M
========================================================================
-Version: dracut-037-11.git20140402.fc20
+Version: dracut-038-31.git20141204.fc21
<em class="lineannotation"><span class="lineannotation">[output truncated]</span></em></pre><div class="para">
See <code class="command">man dracut</code> and <code class="command">man dracut.conf</code> for more information on options and usage.
</div></li><li class="step"><div class="para">
Examine the <code class="filename">/boot/grub2/grub.cfg</code> configuration file to ensure that an <code class="computeroutput"><code class="filename">initramfs-<em class="replaceable"><code>kernel_version</code></em>.img</code></code> file exists for the kernel version you are booting. For example:
</div><pre class="screen">~]# <code class="command">grep initramfs /boot/grub2/grub.cfg</code>
- initrd /initramfs-3.17.3-200.fc20.x86_64.img
- initrd /initramfs-3.17.2-200.fc20.x86_64.img
- initrd /initramfs-3.16.7-200.fc20.x86_64.img
- initrd /initramfs-0-rescue-d54d78fd40ab445a9556279010454c22.img</pre><div class="para">
- See <a class="xref" href="s1-kernel-boot-loader.html">Section 20.6, “Verifying the Boot Loader”</a> for more information on how to read and update the <code class="filename">/boot/grub2/grub.cfg</code> file.
- </div></li></ol></div><h3 id="bh-Verifying_the_Initial_RAM_Disk_Image_and_Kernel_on_IBM_eServer_System_i"> Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i </h3><a id="idm225462258528" class="indexterm"></a><div class="para">
+ initrd16 /initramfs-3.17.7-300.fc21.x86_64.img
+ initrd16 /initramfs-3.17.6-300.fc21.x86_64.img
+ initrd16 /initramfs-3.17.4-302.fc21.x86_64.img
+ initrd16 /initramfs-0-rescue-db90b4e3715b42daa871351439343ca4.img</pre><div class="para">
+ See <a class="xref" href="s1-kernel-boot-loader.html">Section 21.6, “Verifying the Boot Loader”</a> for more information on how to read and update the <code class="filename">/boot/grub2/grub.cfg</code> file.
+ </div></li></ol></div><h3 id="bh-Verifying_the_Initial_RAM_Disk_Image_and_Kernel_on_IBM_eServer_System_i"> Verifying the Initial RAM Disk Image and Kernel on IBM eServer System i </h3><a id="idm261754999968" class="indexterm"></a><div class="para">
On IBM eServer System i machines, the initial RAM disk and kernel files are combined into a single file, which is created with the <code class="command">addRamDisk</code> command. This step is performed automatically if the kernel and its associated packages are installed or upgraded from the RPM packages distributed by The Fedora Project; thus, it does not need to be executed manually. To verify that it was created, run the following command as <code class="systemitem">root</code> to make sure the <code class="filename">/boot/vmlinitrd-<em class="replaceable"><code>kernel_version</code></em></code> file already exists:
- </div><pre class="screen"><code class="command">ls -l /boot</code></pre><div class="para">
+ </div><pre class="screen"><code class="command">ls -l /boot/</code></pre><div class="para">
The <em class="replaceable"><code>kernel_version</code></em> should match the version of the kernel just installed.
- </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-perform-upgrade.html"><strong>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>
\ No newline at end of file
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-kernel-perform-upgrade.html"><strong>Prev</strong>21.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>21.6. Verifying the Boot Loader</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html
new file mode 100644
index 0000000..5ce3e17
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources.html
@@ -0,0 +1,17 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>20.8. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Working_with_the_GRUB_2_Boot_Loader.html" title="Chapter 20. Working with the GRUB 2 Boot Loader" /><link rel="prev" href="sec-UEFI_Secure_Boot.html" title="20.7. UEFI Secure Boot" /><link rel="next" href="ch-Manually_Upgrading_the_Kernel.html" title="Chapter 21. 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="sec-UEFI_Se
cure_Boot.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="section" id="sec-Working_with_the_GRUB_2_Boot_Loader-Additional_Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">20.8. Additional Resources</h2></div></div></div><div class="para">
+ Please see the following resources for more information on the GRUB 2 boot loader:
+ </div><h3 id="bh-Working_with_the_GRUB_2_Boot_Loader-Installed_Documentation">Installed Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="filename">/usr/share/doc/grub2-tools-<version-number></code> — This directory contains information about using and configuring GRUB 2. <code class="literal"><version-number></code> corresponds to the version of the GRUB 2 package installed.
+ </div></li><li class="listitem"><div class="para">
+ <code class="command">info grub2</code> — The GRUB 2 info page contains a tutorial, a user reference manual, a programmer reference manual, and a FAQ document about GRUB 2 and its usage.
+ </div></li></ul></div><h3 id="bh-Working_with_the_GRUB_2_Boot_Loader-External_Documentation">External Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <a href="http://docs.fedoraproject.org/install-guide"> Fedora Installation Guide</a> — The Installation Guide provides basic information on GRUB 2, for example, installation, terminology, interfaces, and commands.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-UEFI_Secure_Boot.html"><strong>Prev</strong>20.7. UEFI Secure Boot</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 21. Manually Upgrading the Kernel</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Yum_Plugins.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Yum_Plugins.html
index 44b6520..578f550 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Yum_Plugins.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-Yum_Plugins.html
@@ -6,13 +6,13 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-yum.html" title="Chapter 5. Yum" /><link rel="prev" href="sec-Creating_a_Yum_Repository.html" title="5.3.6. Creating a Yum Repository" /><link rel="next" href="sec-Installing_More_Yum_Plugins.html" title="5.4.2. Installing Additional Yum Plug-ins" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 class="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">5.4. Yum Plug-ins</h2></div></div></div><a id="idm225455978224" class="indexterm"></a><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-yum.html" title="Chapter 5. Yum" /><link rel="prev" href="sec-Creating_a_Yum_Repository.html" title="5.3.6. Creating a Yum Repository" /><link rel="next" href="sec-Installing_More_Yum_Plugins.html" title="5.4.2. Installing Additional Yum Plug-ins" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.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 class="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">5.4. Yum Plug-ins</h2></div></div></div><a id="idm261747880752" class="indexterm"></a><div class="para">
Yum provides plug-ins that extend and enhance its operations. Certain plug-ins are installed by default. Yum always informs you which plug-ins, if any, are loaded and active whenever you call any <code class="command">yum</code> command. For example:
</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 plug-in names which follow <code class="command">Loaded plugins</code> are the names you can provide to the <code class="option">--disableplugin=<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">5.4.1. Enabling, Configuring, and Disabling Yum Plug-ins</h3></div></div></div><a id="idm225474674688" class="indexterm"></a><a id="idm225474673248" class="indexterm"></a><a id="idm225475556224" class="indexterm"></a><div class="para">
+ </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">5.4.1. Enabling, Configuring, and Disabling Yum Plug-ins</h3></div></div></div><a id="idm261749001984" class="indexterm"></a><a id="idm261749000544" class="indexterm"></a><a id="idm261749989968" class="indexterm"></a><div class="para">
To enable Yum plug-ins, 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="literal">1</code>:
</div><pre class="programlisting">plugins=1</pre><div class="para">
You can disable all plug-ins by changing this line to <code class="command">plugins=0</code>.
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-printing-LPDLPR-printer.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-printing-LPDLPR-printer.html
index 80fee4c..935f2f9 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-printing-LPDLPR-printer.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sec-printing-LPDLPR-printer.html
@@ -6,7 +6,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
- </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Printer_Configuration.html" title="12.3. Printer Configuration" /><link rel="prev" href="s1-printing-ipp-printer.html" title="12.3.5. Adding an IPP Printer" /><link rel="next" href="s1-printing-smb-printer.html" title="12.3.7. Adding a Samba (SMB) printer" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-printing-ipp-printer.html"><strong>Prev</strong
></a></li><li class="next"><a accesskey="n" href="s1-printing-smb-printer.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-printing-LPDLPR-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.6. Adding an LPD/LPR Host or Printer</h3></div></div></div><a id="idm225458997312" class="indexterm"></a><div class="procedure" id="proc-Adding_HTTPS_Printer"><div class="para">
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sec-Printer_Configuration.html" title="12.3. Printer Configuration" /><link rel="prev" href="s1-printing-ipp-printer.html" title="12.3.5. Adding an IPP Printer" /><link rel="next" href="s1-printing-smb-printer.html" title="12.3.7. Adding a Samba (SMB) printer" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="s1-printing-ipp-printer.html"><strong>Prev</strong
></a></li><li class="next"><a accesskey="n" href="s1-printing-smb-printer.html"><strong>Next</strong></a></li></ul><div class="section" id="sec-printing-LPDLPR-printer"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">12.3.6. Adding an LPD/LPR Host or Printer</h3></div></div></div><a id="idm261723115728" class="indexterm"></a><div class="procedure" id="proc-Adding_HTTPS_Printer"><div class="para">
Follow this procedure to add an LPD/LPR host or printer:
</div><ol class="1"><li class="step"><div class="para">
Open the <code class="systemitem">New Printer</code> dialog (refer to <a class="xref" href="sec-Setting_Printer.html">Section 12.3.2, “Starting Printer Setup”</a>).
@@ -15,7 +15,7 @@
</div></li><li class="step"><div class="para">
On the right, enter the connection settings:
</div><div class="variablelist"><dl class="variablelist"><dt class="varlistentry"><span class="term"><span class="guilabel"><strong>Host</strong></span></span></dt><dd><div class="para">
- The hostname of the LPD/LPR printer or host.
+ The host name of the LPD/LPR printer or host.
</div><div class="para">
Optionally, click <span class="guibutton"><strong>Probe</strong></span> to find queues on the LPD host.
</div></dd><dt class="varlistentry"><span class="term"><span class="guilabel"><strong>Queue</strong></span></span></dt><dd><div class="para">
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-Keyboard_Configuration-Resources.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-Keyboard_Configuration-Resources.html
index 7b12d96..1595187 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-Keyboard_Configuration-Resources.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-Keyboard_Configuration-Resources.html
@@ -7,7 +7,7 @@
addID('Fedora.21.books');
addID('Fedora.21.System_Administrators_Guide');
</script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-System_Locale_and_Keyboard_Configuration.html" title="Chapter 2. System Locale and Keyboard Configuration" /><link rel="prev" href="s2-Setting_the_Keymap.html" title="2.2.3. Setting the Keymap" /><link rel="next" href="ch-Configuring_the_Date_and_Time.html" title="Chapter 3. Configuring the Date and Time" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href=
"s2-Setting_the_Keymap.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="ch-Configuring_the_Date_and_Time.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Keyboard_Configuration-Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">2.3. Additional Resources</h2></div></div></div><div class="para">
- For more information on how to configure the keyboard layout on Red Hat Enterprise Linux, see the resources listed below:
+ For more information on how to configure the keyboard layout on Fedora, see the resources listed below:
</div><h3 id="brid-Keyboard_Configuration-Resources-Installed">Installed Documentation</h3><div class="itemizedlist"><ul><li class="listitem"><div class="para">
<code class="systemitem">localectl</code>(1) — The manual page for the <code class="command">localectl</code> command line utility documents how to use this tool to configure the system locale and keyboard layout.
</div></li><li class="listitem"><div class="para">
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-Preface-Book_Organization.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-Preface-Book_Organization.html
index d4376ee..7f0e6ce 100644
--- a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-Preface-Book_Organization.html
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-Preface-Book_Organization.html
@@ -55,9 +55,9 @@
</div></dd><dt class="varlistentry"><span class="term"><a class="xref" href="part-Kernel_Module_and_Driver_Configuration.html">Part VI, “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 on 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.
+ <a class="xref" href="ch-Manually_Upgrading_the_Kernel.html">Chapter 21, <em>Manually Upgrading the Kernel</em></a> provides important information on how to manually update a kernel package using the <code class="command">rpm</code> command instead of <code class="command">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.
+ <a class="xref" href="ch-Working_with_Kernel_Modules.html">Chapter 22, <em>Working with Kernel Modules</em></a> explains how to display, query, load, and unload kernel modules and their dependencies, and how to set module parameters. Additionally, it covers specific kernel module capabilities such as using multiple Ethernet cards and using channel bonding. Read this chapter if you need to work with kernel modules.
</div></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></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>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-Users_and_Groups-Resources.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-Users_and_Groups-Resources.html
new file mode 100644
index 0000000..07f0ae5
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-Users_and_Groups-Resources.html
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>4.4. Additional Resources</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Managing_Users_and_Groups.html" title="Chapter 4. Managing Users and Groups" /><link rel="prev" href="s2-users-tools-groups-directories.html" title="4.3.5. Creating Group Directories" /><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="s2-users-tools-groups-directori
es.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="part-Package_Management.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-Users_and_Groups-Resources"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">4.4. Additional Resources</h2></div></div></div><a id="idm261756182480" class="indexterm"></a><a id="idm261756181040" class="indexterm"></a><div class="para">
+ For more information on how to manage users and groups on Fedora, see the resources listed below.
+ </div><h3 id="sect-Users_and_Groups-Resources-Installed">Installed Documentation</h3><a id="idm261756178272" class="indexterm"></a><a id="idm261756176352" class="indexterm"></a><div class="para">
+ For information about various utilities for managing users and groups, see the following manual pages:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">useradd</code>(8) — The manual page for the <code class="command">useradd</code> command documents how to use it to create new users.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">userdel</code>(8) — The manual page for the <code class="command">userdel</code> command documents how to use it to delete users.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">usermod</code>(8) — The manual page for the <code class="command">usermod</code> command documents how to use it to modify users.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">groupadd</code>(8) — The manual page for the <code class="command">groupadd</code> command documents how to use it to create new groups.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">groupdel</code>(8) — The manual page for the <code class="command">groupdel</code> command documents how to use it to delete groups.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">groupmod</code>(8) — The manual page for the <code class="command">groupmod</code> command documents how to use it to modify group membership.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">gpasswd</code>(1) — The manual page for the <code class="command">gpasswd</code> command documents how to manage the <code class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">grpck</code>(8) — The manual page for the <code class="command">grpck</code> command documents how to use it to verify the integrity of the <code class="filename">/etc/group</code> file.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">pwck</code>(8) — The manual page for the <code class="command">pwck</code> command documents how to use it to verify the integrity of the <code class="filename">/etc/passwd</code> and <code class="filename">/etc/shadow</code> files.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">pwconv</code>(8) — The manual page for the <code class="command">pwconv</code>, <code class="command">pwunconv</code>, <code class="command">grpconv</code>, and <code class="command">grpunconv</code> commands documents how to convert shadowed information for passwords and groups.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">id</code>(1) — The manual page for the <code class="command">id</code> command documents how to display user and group IDs.
+ </div></li></ul></div><div class="para">
+ For information about related configuration files, see:
+ </div><div class="itemizedlist"><ul><li class="listitem"><div class="para">
+ <code class="systemitem">group</code>(5) — The manual page for the <code class="filename">/etc/group</code> file documents how to use this file to define system groups.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">passwd</code>(5) — The manual page for the <code class="filename">/etc/passwd</code> file documents how to use this file to define user information.
+ </div></li><li class="listitem"><div class="para">
+ <code class="systemitem">shadow</code>(5) — The manual page for the <code class="filename">/etc/shadow</code> file documents how to use this file to set passwords and account expiration information for the system.
+ </div></li></ul></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="s2-users-tools-groups-directories.html"><strong>Prev</strong>4.3.5. Creating Group Directories</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>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-enrolling-public-key-on-target-system.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-enrolling-public-key-on-target-system.html
new file mode 100644
index 0000000..a4e95c7
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-enrolling-public-key-on-target-system.html
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.7.4. Enrolling Public Key on Target System</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sect-signing-kernel-modules-for-secure-boot.html" title="22.7. Signing Kernel Modules for Secure Boot" /><link rel="prev" href="sect-generating-a-public-private-x509-key-pair.html" title="22.7.3. Generating a Public and Private X.509 Key Pair" /><link rel="next" href="sect-signing-kernel-module-with-the-private-key.html" title="22.7.5. Signing Kernel Module with the Private Key" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" />
</a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-generating-a-public-private-x509-key-pair.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-signing-kernel-module-with-the-private-key.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-enrolling-public-key-on-target-system"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.4. Enrolling Public Key on Target System</h3></div></div></div><div class="para">
+ When Fedora boots on a UEFI-based system with Secure Boot enabled, all keys that are in the Secure Boot db key database, but not in the dbx database of revoked keys, are loaded onto the system keyring by the kernel. The system keyring is used to authenticate kernel modules.
+ </div><div class="section" id="sect-factory-firmware-image-including-public-key"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">22.7.4.1. Factory Firmware Image Including Public Key</h4></div></div></div><div class="para">
+ To facilitate authentication of your kernel module on your systems, consider requesting your system vendor to incorporate your public key into the UEFI Secure Boot key database in their factory firmware image.
+ </div></div><div class="section" id="sect-executable-key-enrollment-image-adding-public-key"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">22.7.4.2. Executable Key Enrollment Image Adding Public Key</h4></div></div></div><div class="para">
+ It is possible to add a key to an existing populated and active Secure Boot key database. This can be done by writing and providing an EFI executable <span class="emphasis"><em>enrollment</em></span> image. Such an enrollment image contains a properly formed request to append a key to the Secure Boot key database. This request must include data that is properly signed by the private key that corresponds to a public key that is already in the system's Secure Boot Key Exchange Key (KEK) database. Additionally, this EFI image must be signed by a private key that corresponds to a public key that is already in the key database.
+ </div><div class="para">
+ It is also possible to write an enrollment image that runs under Fedora. However, the Fedora image must be properly signed by a private key that corresponds to a public key that is already in the KEK database.
+ </div><div class="para">
+ The construction of either type of key enrollment images requires assistance from the platform vendor.
+ </div></div><div class="section" id="sect-system-administrator-manually-adding-public-key-to-the-mok-list"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">22.7.4.3. System Administrator Manually Adding Public Key to the MOK List</h4></div></div></div><div class="para">
+ The Machine Owner Key (MOK) facility is a feature that is supported by Fedora and can be used to augment the UEFI Secure Boot key database. When Fedora boots on a UEFI-enabled system with Secure Boot enabled, the keys on the MOK list are also added to the system keyring in addition to the keys from the key database. The MOK list keys are also stored persistently and securely in the same fashion as the Secure Boot key database keys, but these are two separate facilities. The MOK facility is supported by shim.efi, MokManager.efi, grubx64.efi, and the Fedora <code class="command">mokutil</code> utility.
+ </div><div class="para">
+ The major capability provided by the MOK facility is the ability to add public keys to the MOK list without needing to have the key chain back to another key that is already in the KEK database. However, enrolling a MOK key requires manual interaction by a <span class="emphasis"><em>physically present</em></span> user at the UEFI system console on each target system. Nevertheless, the MOK facility provides an excellent method for testing newly generated key pairs and testing kernel modules signed with them.
+ </div><div class="para">
+ Follow these steps to add your public key to the MOK list:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Request addition of your public key to the MOK list using a Fedora userspace utility:
+ </div><pre class="screen">~]# <code class="command">mokutil <code class="option">--import</code> <code class="filename">my_signing_key_pub.der</code></code></pre><div class="para">
+ You will be asked to enter and confirm a password for this MOK enrollment request.
+ </div></li><li class="step"><div class="para">
+ Reboot the machine.
+ </div></li><li class="step"><div class="para">
+ The pending MOK key enrollment request will be noticed by <code class="systemitem">shim.efi</code> and it will launch <code class="systemitem">MokManager.efi</code> to allow you to complete the enrollment from the UEFI console. You will need to enter the password you previously associated with this request and confirm the enrollment. Your public key is added to the MOK list, which is persistent.
+ </div></li></ol></div><div class="para">
+ Once a key is on the MOK list, it will be automatically propagated to the system key ring on this and subsequent boots when UEFI Secure Boot is enabled.
+ </div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-generating-a-public-private-x509-key-pair.html"><strong>Prev</strong>22.7.3. Generating a Public and Private X.509 Key...</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-signing-kernel-module-with-the-private-key.html"><strong>Next</strong>22.7.5. Signing Kernel Module with the Private Key</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-generating-a-public-private-x509-key-pair.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-generating-a-public-private-x509-key-pair.html
new file mode 100644
index 0000000..30940f1
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-generating-a-public-private-x509-key-pair.html
@@ -0,0 +1,37 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.7.3. Generating a Public and Private X.509 Key Pair</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sect-signing-kernel-modules-for-secure-boot.html" title="22.7. Signing Kernel Modules for Secure Boot" /><link rel="prev" href="sect-kernel-module-authentication.html" title="22.7.2. Kernel Module Authentication" /><link rel="next" href="sect-enrolling-public-key-on-target-system.html" title="22.7.4. Enrolling Public Key on Target System" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="pre
vious"><a accesskey="p" href="sect-kernel-module-authentication.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-enrolling-public-key-on-target-system.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-generating-a-public-private-x509-key-pair"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.3. Generating a Public and Private X.509 Key Pair</h3></div></div></div><div class="para">
+ You need to generate a public and private X.509 key pair that will be used to sign a kernel module after it has been built. The corresponding public key will be used to authenticate the kernel module when it is loaded.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ The <code class="command">openssl</code> tool can be used to generate a key pair that satisfies the requirements for kernel module signing in Fedora. Some of the parameters for this key generation request are best specified with a configuration file; follow the example below to create your own configuration file.
+ </div><pre class="screen">~]# <code class="command">cat << EOF > <em class="replaceable"><code>configuration_file</code></em>.config</code>
+[ req ]
+default_bits = 4096
+distinguished_name = req_distinguished_name
+prompt = no
+string_mask = utf8only
+x509_extensions = myexts
+
+[ req_distinguished_name ]
+O = <em class="replaceable"><code>Organization</code></em>
+CN = <em class="replaceable"><code>Organization signing key</code></em>
+emailAddress = <em class="replaceable"><code>E-mail address</code></em>
+
+[ myexts ]
+basicConstraints=critical,CA:FALSE
+keyUsage=digitalSignature
+subjectKeyIdentifier=hash
+authorityKeyIdentifier=keyid
+EOF</pre></li><li class="step"><div class="para">
+ After you have created the configuration file, you can create an X.509 public and private key pair. The public key will be written to the <code class="filename"><em class="replaceable"><code>public_key</code></em>.der</code> file and the private key will be written to the <code class="filename"><em class="replaceable"><code>private_key</code></em>.priv</code> file.
+ </div><pre class="screen">~]# <code class="command">openssl req -x509 -new -nodes -utf8 -sha256 -days 36500 \ > -batch -config <em class="replaceable"><code>configuration_file</code></em>.config -outform DER \ > -out <em class="replaceable"><code>public_key</code></em>.der \ > -keyout <em class="replaceable"><code>private_key</code></em>.priv</code></pre></li><li class="step"><div class="para">
+ Enroll your public key on all systems where you want to authenticate and load your kernel module.
+ </div></li></ol></div><div class="warning"><div class="admonition_header"><h2>Warning</h2></div><div class="admonition"><div class="para">
+ Take proper care to guard the contents of your private key. In the wrong hands, the key could be used to compromise any system which has your public key.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-kernel-module-authentication.html"><strong>Prev</strong>22.7.2. Kernel Module 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-enrolling-public-key-on-target-system.html"><strong>Next</strong>22.7.4. Enrolling Public Key on Target System</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-kernel-module-authentication.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-kernel-module-authentication.html
new file mode 100644
index 0000000..b7057af
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-kernel-module-authentication.html
@@ -0,0 +1,198 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.7.2. Kernel Module Authentication</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sect-signing-kernel-modules-for-secure-boot.html" title="22.7. Signing Kernel Modules for Secure Boot" /><link rel="prev" href="sect-signing-kernel-modules-for-secure-boot.html" title="22.7. Signing Kernel Modules for Secure Boot" /><link rel="next" href="sect-generating-a-public-private-x509-key-pair.html" title="22.7.3. Generating a Public and Private X.509 Key Pair" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><u
l class="docnav"><li class="previous"><a accesskey="p" href="sect-signing-kernel-modules-for-secure-boot.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-generating-a-public-private-x509-key-pair.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-kernel-module-authentication"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.2. Kernel Module Authentication</h3></div></div></div><div class="para">
+ In Fedora, when a kernel module is loaded, the module's signature is checked using the public X.509 keys on the kernel's system key ring, excluding those keys that are on the kernel's system black list key ring.
+ </div><div class="section" id="sect-sources-for-public-keys-used-to-authenticate-kernel-modules"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">22.7.2.1. Sources For Public Keys Used To Authenticate Kernel Modules</h4></div></div></div><div class="para">
+ During boot, the kernel loads X.509 keys into the system key ring or the system black list key ring from a set of persistent key stores as shown in <a class="xref" href="sect-kernel-module-authentication.html#table-sources-for-system-key-rings">Table 22.2, “Sources For System Key Rings”</a>
+ </div><div class="table" id="table-sources-for-system-key-rings"><h6>Table 22.2. Sources For System Key Rings</h6><div class="table-contents"><table summary="Sources For System Key Rings" border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><thead><tr><th class="" align="left">
+ Source of X.509 Keys
+ </th><th class="" align="left">
+ User Ability to Add Keys
+ </th><th class="" align="left">
+ UEFI Secure Boot State
+ </th><th class="" align="left">
+ Keys Loaded During Boot
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ Embedded in kernel
+ </td><td class="" align="left">
+ No
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2" align="left">
+ UEFI Secure Boot "db"
+ </td><td class="" rowspan="2" align="left">
+ Limited
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2" align="left">
+ UEFI Secure Boot "dbx"
+ </td><td class="" rowspan="2" align="left">
+ Limited
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2" align="left">
+ Embedded in <code class="systemitem">shim.efi</code> boot loader
+ </td><td class="" rowspan="2" align="left">
+ No
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr><tr><td class="" rowspan="2" align="left">
+ Machine Owner Key (MOK) list
+ </td><td class="" rowspan="2" align="left">
+ Yes
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ <code class="systemitem">.system_keyring</code>
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Note that if the system is not UEFI-based or if UEFI Secure Boot is not enabled, then only the keys that are embedded in the kernel are loaded onto the system key ring and you have no ability to augment that set of keys without rebuilding the kernel. The system black list key ring is a list of X.509 keys which have been revoked. If your module is signed by a key on the black list then it will fail authentication even if your public key is in the system key ring.
+ </div><div class="para">
+ You can display information about the keys on the system key rings using the <code class="command">keyctl</code> utility. The following is abbreviated example output from a Fedora system where UEFI Secure Boot is not enabled.
+ </div><pre class="screen">~]# <code class="command">keyctl list %:.system_keyring</code>
+1 key in keyring:
+ 61139991: ---lswrv 0 0 asymmetric: Fedora kernel signing key: 1fc9e68f7419556348fdee2fdeb7ff9da6337b</pre><div class="para">
+ The following is abbreviated example output from a Fedora system where UEFI Secure Boot is enabled.
+ </div><pre class="screen">~]# <code class="command">keyctl list %:.system_keyring</code>
+6 keys in keyring:
+...asymmetric: Red Hat Enterprise Linux Driver Update Program (key 3): bf57f3e87...
+...asymmetric: Red Hat Secure Boot (CA key 1): 4016841644ce3a810408050766e8f8a29...
+...asymmetric: Microsoft Corporation UEFI CA 2011: 13adbf4309bd82709c8cd54f316ed...
+...asymmetric: Microsoft Windows Production PCA 2011: a92902398e16c49778cd90f99e...
+...asymmetric: Red Hat Enterprise Linux kernel signing key: 4249689eefc77e95880b...
+...asymmetric: Red Hat Enterprise Linux kpatch signing key: 4d38fd864ebe18c5f0b7...</pre><div class="para">
+ The above output shows the addition of two keys from the UEFI Secure Boot "db" keys plus the <code class="computeroutput">Red Hat Secure Boot (CA key 1)</code> which is embedded in the <code class="systemitem">shim.efi</code> boot loader. You can also look for the kernel console messages that identify the keys with an UEFI Secure Boot related source, that is UEFI Secure Boot db, embedded shim, and MOK list.
+ </div><pre class="screen">~]# <code class="command">dmesg | grep 'EFI: Loaded cert'</code>
+[5.160660] EFI: Loaded cert 'Microsoft Windows Production PCA 2011: a9290239...
+[5.160674] EFI: Loaded cert 'Microsoft Corporation UEFI CA 2011: 13adbf4309b...
+[5.165794] EFI: Loaded cert 'Red Hat Secure Boot (CA key 1): 4016841644ce3a8...</pre></div><div class="section" id="sect-kernel-module-authentication-requirements"><div class="titlepage"><div><div keep-together.within-column="always"><h4 class="title">22.7.2.2. Kernel Module Authentication Requirements </h4></div></div></div><div class="para">
+ If UEFI Secure Boot is enabled or if the <code class="option">module.sig_enforce</code> kernel parameter has been specified, then only signed kernel modules that are authenticated using a key on the system key ring can be successfully loaded.<a href="#ftn.idm261714310592" class="footnote"><sup class="footnote" id="idm261714310592">[4]</sup></a> If UEFI Secure Boot is disabled and if the <code class="option">module.sig_enforce</code> kernel parameter has not been specified, then unsigned kernel modules and signed kernel modules without a public key can be successfully loaded. This is summarized in <a class="xref" href="sect-kernel-module-authentication.html#table-kernel-module-authentication-requirements-for-loading">Table 22.3, “Kernel Module Authentication Requirements for Loading”</a>.
+ </div><div class="table" id="table-kernel-module-authentication-requirements-for-loading"><h6>Table 22.3. Kernel Module Authentication Requirements for Loading</h6><div class="table-contents"><table summary="Kernel Module Authentication Requirements for Loading" border="1"><colgroup><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /><col width="17%" /></colgroup><thead><tr><th class="" align="left">
+ Module Signed
+ </th><th class="" align="left">
+ Public Key Found and Signature Valid
+ </th><th class="" align="left">
+ UEFI Secure Boot State
+ </th><th class="" align="left">
+ module.sig_enforce
+ </th><th class="" align="left">
+ Module Load
+ </th><th class="" align="left">
+ Kernel Tainted
+ </th></tr></thead><tbody><tr><td class="" rowspan="3" align="left">
+ Unsigned
+ </td><td class="" rowspan="3" align="left">
+ -
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ </td></tr><tr><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ -
+ </td></tr><tr><td class="" rowspan="3" align="left">
+ Signed
+ </td><td class="" rowspan="3" align="left">
+ No
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ Yes
+ </td></tr><tr><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ -
+ </td></tr><tr><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ Fails
+ </td><td class="" align="left">
+ -
+ </td></tr><tr><td class="" rowspan="3" align="left">
+ Signed
+ </td><td class="" rowspan="3" align="left">
+ Yes
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class="" align="left">
+ Not enabled
+ </td><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ No
+ </td></tr><tr><td class="" align="left">
+ Enabled
+ </td><td class="" align="left">
+ -
+ </td><td class="" align="left">
+ Succeeds
+ </td><td class="" align="left">
+ No
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="para">
+ Subsequent sections will describe how to generate a public and private X.509 key pair, how to use the private key to sign a kernel module, and how to enroll the public key into a source for the system key ring.
+ </div></div><div class="footnotes"><br /><hr /><div id="ftn.idm261714310592" class="footnote"><div class="para"><a href="#idm261714310592" class="para"><sup class="para">[4] </sup></a>
+ Provided that the public key is not on the system black list key ring.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-signing-kernel-modules-for-secure-boot.html"><strong>Prev</strong>22.7. Signing Kernel Modules for Secure Boot</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-generating-a-public-private-x509-key-pair.html"><strong>Next</strong>22.7.3. Generating a Public and Private X.509 Key...</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-loading-signed-kernel-module.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-loading-signed-kernel-module.html
new file mode 100644
index 0000000..bfba7d5
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-loading-signed-kernel-module.html
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.7.6. Loading Signed Kernel Module</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sect-signing-kernel-modules-for-secure-boot.html" title="22.7. Signing Kernel Modules for Secure Boot" /><link rel="prev" href="sect-signing-kernel-module-with-the-private-key.html" title="22.7.5. Signing Kernel Module with the Private Key" /><link rel="next" href="s1-kernel-modules-additional-resources.html" title="22.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="sect-signing-kernel-module-with-the-private-key.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="sect-loading-signed-kernel-module"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.6. Loading Signed Kernel Module</h3></div></div></div><div class="para">
+ Once your public key is enrolled and is in the system keyring, the normal kernel module loading mechanisms will work transparently. In the following example, you will use <code class="command">mokutil</code> to add your public key to the MOK list and you will manually load your kernel module with <code class="command">modprobe</code>.
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Optionally, you can verify that your kernel module will not load before you have enrolled your public key. First, verify what keys have been added to the system key ring on the current boot by running the <code class="command">keyctl list %:.system_keyring</code> as root. Since your public key has not been enrolled yet, it should not be displayed in the output of the command.
+ </div></li><li class="step"><div class="para">
+ Request enrollment of your public key.
+ </div><pre class="screen">~]# <code class="command">mokutil --import <em class="replaceable"><code>my_signing_key_pub</code></em>.der</code></pre></li><li class="step"><div class="para">
+ Reboot, and complete the enrollment at the UEFI console.
+ </div><pre class="screen">~]# <code class="command">reboot</code></pre></li><li class="step"><div class="para">
+ After the system reboots, verify the keys on the system key ring again.
+ </div><pre class="screen">~]# <code class="command">keyctl list %:.system_keyring</code></pre></li><li class="step"><div class="para">
+ You should now be able to load your kernel module successfully.
+ </div><pre class="screen">~]# <code class="command">modprobe -v <em class="replaceable"><code>my_module</code></em></code>
+insmod /lib/modules/3.17.4-302.fc21.x86_64/extra/<em class="replaceable"><code>my_module</code></em>.ko
+~]# <code class="command">lsmod | grep <em class="replaceable"><code>my_module</code></em></code>
+<em class="replaceable"><code>my_module</code></em> 12425 0</pre></li></ol></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-signing-kernel-module-with-the-private-key.html"><strong>Prev</strong>22.7.5. Signing Kernel Module with the Private Key</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>22.8. Additional Resources</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-signing-kernel-module-with-the-private-key.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-signing-kernel-module-with-the-private-key.html
new file mode 100644
index 0000000..a796278
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-signing-kernel-module-with-the-private-key.html
@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.7.5. Signing Kernel Module with the Private Key</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="sect-signing-kernel-modules-for-secure-boot.html" title="22.7. Signing Kernel Modules for Secure Boot" /><link rel="prev" href="sect-enrolling-public-key-on-target-system.html" title="22.7.4. Enrolling Public Key on Target System" /><link rel="next" href="sect-loading-signed-kernel-module.html" title="22.7.6. Loading Signed Kernel Module" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="pre
vious"><a accesskey="p" href="sect-enrolling-public-key-on-target-system.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-loading-signed-kernel-module.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-signing-kernel-module-with-the-private-key"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.5. Signing Kernel Module with the Private Key</h3></div></div></div><div class="para">
+ There are no extra steps required to prepare your kernel module for signing. You build your kernel module normally. Assuming an appropriate Makefile and corresponding sources, follow these steps to build your module and sign it:
+ </div><div class="procedure"><ol class="1"><li class="step"><div class="para">
+ Build your <code class="filename">my_module.ko</code> module the standard way:
+ </div><pre class="screen">~]# <code class="command">make -C /usr/src/kernels/$(uname -r) M=$PWD modules</code></pre></li><li class="step"><div class="para">
+ Sign your kernel module with your private key. This is done with a Perl script. Note that the script requires that you provide both the files that contain your private and the public key as well as the kernel module file that you want to sign.
+ </div><pre class="screen">~]# <code class="command">perl /usr/src/kernels/$(uname -r)/scripts/sign-file \ > sha256 \ > my_signing_key.priv \ > my_signing_key_pub.der \ > my_module.ko</code></pre></li></ol></div><div class="para">
+ Your kernel module is in ELF image format and this script computes and appends the signature directly to the ELF image in your <code class="filename">my_module.ko</code> file. The <code class="command">modinfo</code> utility can be used to display information about the kernel module's signature, if it is present. For information on using the utility, see <a class="xref" href="sec-Displaying_Information_About_a_Module.html">Section 22.2, “Displaying Information About a Module”</a>.
+ </div><div class="para">
+ Note that this appended signature is not contained in an ELF image section and is not a formal part of the ELF image. Therefore, tools such as <code class="command">readelf</code> will not be able to display the signature on your kernel module.
+ </div><div class="para">
+ Your kernel module is now ready for loading. Note that your signed kernel module is also loadable on systems where UEFI Secure Boot is disabled or on a non-UEFI system. That means you do not need to provide both a signed and unsigned version of your kernel module.
+ </div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sect-enrolling-public-key-on-target-system.html"><strong>Prev</strong>22.7.4. Enrolling Public Key on Target 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="sect-loading-signed-kernel-module.html"><strong>Next</strong>22.7.6. Loading Signed Kernel Module</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-signing-kernel-modules-for-secure-boot.html b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-signing-kernel-modules-for-secure-boot.html
new file mode 100644
index 0000000..a78bdd0
--- /dev/null
+++ b/public_html/en-US/Fedora/21/html/System_Administrators_Guide/sect-signing-kernel-modules-for-secure-boot.html
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>22.7. Signing Kernel Modules for Secure Boot</title><link rel="stylesheet" type="text/css" href="Common_Content/css/default.css" /><link rel="stylesheet" media="print" href="Common_Content/css/print.css" type="text/css" /><meta name="generator" content="publican 2.8" /><meta name="package" content="Fedora-System_Administrators_Guide-21-en-US-1.0-0" /><script type="text/javascript" src="../../../../../toc.js"></script><script type="text/javascript">
+ addID('Fedora');
+
+ addID('Fedora.21');
+
+ addID('Fedora.21.books');
+ addID('Fedora.21.System_Administrators_Guide');
+ </script><link rel="home" href="index.html" title="System Administrator's Guide" /><link rel="up" href="ch-Working_with_Kernel_Modules.html" title="Chapter 22. Working with Kernel Modules" /><link rel="prev" href="sec-Persistent_Module_Loading.html" title="22.6. Persistent Module Loading" /><link rel="next" href="sect-kernel-module-authentication.html" title="22.7.2. Kernel Module Authentication" /></head><body class="toc_embeded "><div id="tocdiv" class="toc"><iframe id="tocframe" class="toc" src="../../../../toc.html">This is an iframe, to view it upgrade your browser or enable iframe display.</iframe></div><p id="title"><a class="left" href="http://www.fedoraproject.org"><img src="Common_Content/images/image_left.png" alt="Product Site" /></a><a class="right" href="http://docs.fedoraproject.org"><img src="Common_Content/images/image_right.png" alt="Documentation Site" /></a></p><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Persistent
_Module_Loading.html"><strong>Prev</strong></a></li><li class="next"><a accesskey="n" href="sect-kernel-module-authentication.html"><strong>Next</strong></a></li></ul><div class="section" id="sect-signing-kernel-modules-for-secure-boot"><div class="titlepage"><div><div keep-together.within-column="always"><h2 class="title">22.7. Signing Kernel Modules for Secure Boot</h2></div></div></div><div class="para">
+ Fedora includes support for the UEFI Secure Boot feature, which means that Fedora can be installed and run on systems where UEFI Secure Boot is enabled. <a href="#ftn.idm261758594672" class="footnote"><sup class="footnote" id="idm261758594672">[2]</sup></a> When Secure Boot is enabled, the EFI operating system boot loaders, the Fedora kernel, and all kernel modules must be signed with a private key and authenticated with the corresponding public key. The Fedora distribution includes signed boot loaders, signed kernels, and signed kernel modules. In addition, the signed first-stage boot loader and the signed kernel include embedded Fedora public keys. These signed executable binaries and embedded keys enable Fedora to install, boot, and run with the Microsoft UEFI Secure Boot CA keys that are provided by the UEFI firmware on systems that support UEFI Secure Boot.<a href="#ftn.idm261758593136" class="footnote"><sup class="footnote" id="idm261758593136">[3]</sup></a>
+ </div><div class="para">
+ The information provided in the following sections describes steps necessary to enable you to self-sign privately built kernel modules for use with Fedora on UEFI-based systems where Secure Boot is enabled. These sections also provide an overview of available options for getting your public key onto the target system where you want to deploy your kernel module.
+ </div><div class="section" id="sect-prerequisites"><div class="titlepage"><div><div keep-together.within-column="always"><h3 class="title">22.7.1. Prerequisites</h3></div></div></div><div class="para">
+ In order to enable signing of externally built modules, the tools listed in the following table are required to be installed on the system.
+ </div><div class="table" id="table-required-tools"><h6>Table 22.1. Required Tools</h6><div class="table-contents"><table summary="Required Tools" border="1"><colgroup><col width="25%" /><col width="25%" /><col width="25%" /><col width="25%" /></colgroup><thead><tr><th class="" align="left">
+ Tool
+ </th><th class="" align="left">
+ Provided by Package
+ </th><th class="" align="left">
+ Used on
+ </th><th class="" align="left">
+ Purpose
+ </th></tr></thead><tbody><tr><td class="" align="left">
+ <code class="command">openssl</code>
+ </td><td class="" align="left">
+ <span class="package">openssl</span>
+ </td><td class="" align="left">
+ Build system
+ </td><td class="" align="left">
+ Generates public and private X.509 key pair
+ </td></tr><tr><td class="" align="left">
+ <code class="command">sign-file</code>
+ </td><td class="" align="left">
+ <span class="package">kernel-devel</span>
+ </td><td class="" align="left">
+ Build system
+ </td><td class="" align="left">
+ Perl script used to sign kernel modules
+ </td></tr><tr><td class="" align="left">
+ <code class="command">perl</code>
+ </td><td class="" align="left">
+ <span class="package">perl</span>
+ </td><td class="" align="left">
+ Build system
+ </td><td class="" align="left">
+ Perl interpreter used to run the signing script
+ </td></tr><tr><td class="" align="left">
+ <code class="command">mokutil</code>
+ </td><td class="" align="left">
+ <span class="package">mokutil</span>
+ </td><td class="" align="left">
+ Target system
+ </td><td class="" align="left">
+ Optional tool used to manually enroll the public key
+ </td></tr><tr><td class="" align="left">
+ <code class="command">keyctl</code>
+ </td><td class="" align="left">
+ <span class="package">keyutils</span>
+ </td><td class="" align="left">
+ Target system
+ </td><td class="" align="left">
+ Optional tool used to display public keys in the system key ring
+ </td></tr></tbody></table></div></div><br class="table-break" /><div class="note"><div class="admonition_header"><h2>Note</h2></div><div class="admonition"><div class="para">
+ Note that the build system, where you build and sign your kernel module, does not need to have UEFI Secure Boot enabled and does not even need to be a UEFI-based system.
+ </div></div></div></div><div class="footnotes"><br /><hr /><div id="ftn.idm261758594672" class="footnote"><div class="para"><a href="#idm261758594672" class="para"><sup class="para">[2] </sup></a>
+ Fedora does not require the use of Secure Boot on UEFI systems.
+ </div></div><div id="ftn.idm261758593136" class="footnote"><div class="para"><a href="#idm261758593136" class="para"><sup class="para">[3] </sup></a>
+ Not all UEFI-based systems include support for Secure Boot.
+ </div></div></div></div><ul class="docnav"><li class="previous"><a accesskey="p" href="sec-Persistent_Module_Loading.html"><strong>Prev</strong>22.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="sect-kernel-module-authentication.html"><strong>Next</strong>22.7.2. Kernel Module Authentication</a></li></ul></body></html>
\ No newline at end of file
diff --git a/public_html/en-US/Fedora/21/pdf/System_Administrators_Guide/Fedora-21-System_Administrators_Guide-en-US.pdf b/public_html/en-US/Fedora/21/pdf/System_Administrators_Guide/Fedora-21-System_Administrators_Guide-en-US.pdf
index 127d68a..e532a3d 100644
Binary files a/public_html/en-US/Fedora/21/pdf/System_Administrators_Guide/Fedora-21-System_Administrators_Guide-en-US.pdf and b/public_html/en-US/Fedora/21/pdf/System_Administrators_Guide/Fedora-21-System_Administrators_Guide-en-US.pdf differ
diff --git a/public_html/en-US/opds-Community_Services_Infrastructure.xml b/public_html/en-US/opds-Community_Services_Infrastructure.xml
index ea8d3c4..391c6dd 100644
--- a/public_html/en-US/opds-Community_Services_Infrastructure.xml
+++ b/public_html/en-US/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora.xml b/public_html/en-US/opds-Fedora.xml
index 471a0e4..91291cd 100644
--- a/public_html/en-US/opds-Fedora.xml
+++ b/public_html/en-US/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:24</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>en-US</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/en-US/opds-Fedora_Contributor_Documentation.xml b/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
index 2ca3c0f..87cab14 100644
--- a/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:24</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 821a8ac..3fc30f7 100644
--- a/public_html/en-US/opds-Fedora_Core.xml
+++ b/public_html/en-US/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:24</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Documentation.xml b/public_html/en-US/opds-Fedora_Documentation.xml
index 87e5ad1..f76fcba 100644
--- a/public_html/en-US/opds-Fedora_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:25</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 4d7e11a..17d0ab2 100644
--- a/public_html/en-US/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/en-US/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds-Fedora_Security_Team.xml b/public_html/en-US/opds-Fedora_Security_Team.xml
index efbcecf..6c9edff 100644
--- a/public_html/en-US/opds-Fedora_Security_Team.xml
+++ b/public_html/en-US/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/en-US/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/en-US/opds.xml b/public_html/en-US/opds.xml
index 4a1f77d..b9d71a5 100644
--- a/public_html/en-US/opds.xml
+++ b/public_html/en-US/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/en-US/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:25</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/en-US/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/en-US/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:24</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:24</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:24</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:25</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:25</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/en-US/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:25</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/en-US/toc.html b/public_html/en-US/toc.html
index 22c8d32..57acf7b 100644
--- a/public_html/en-US/toc.html
+++ b/public_html/en-US/toc.html
@@ -370,7 +370,7 @@
<a class="type" href="./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed">
@@ -447,7 +447,7 @@
<a class="type" href="./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed">
@@ -491,7 +491,7 @@
<a class="type" href="./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed">
@@ -662,7 +662,7 @@
<a class="type" href="./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed">
@@ -1363,7 +1363,7 @@
<a class="type" href="./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed">
@@ -1390,7 +1390,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>
@@ -1710,7 +1710,7 @@
<a class="type" href="./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/es-ES/opds-Community_Services_Infrastructure.xml b/public_html/es-ES/opds-Community_Services_Infrastructure.xml
index c5aacc4..6a4fc6f 100644
--- a/public_html/es-ES/opds-Community_Services_Infrastructure.xml
+++ b/public_html/es-ES/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:25</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora.xml b/public_html/es-ES/opds-Fedora.xml
index 4c16e22..af122f6 100644
--- a/public_html/es-ES/opds-Fedora.xml
+++ b/public_html/es-ES/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:02</updated>
+ <updated>2015-03-06T05:43:27</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>es-ES</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml b/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
index 3cfc27b..f507aa6 100644
--- a/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Documentación de Contribuyente</title>
<subtitle>Fedora Documentación de Contribuyente</subtitle>
- <updated>2015-03-03T16:19:02</updated>
+ <updated>2015-03-06T05:43:27</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 8e2a27a..afee455 100644
--- a/public_html/es-ES/opds-Fedora_Core.xml
+++ b/public_html/es-ES/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:02</updated>
+ <updated>2015-03-06T05:43:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Documentation.xml b/public_html/es-ES/opds-Fedora_Documentation.xml
index 519ad7f..62542f2 100644
--- a/public_html/es-ES/opds-Fedora_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:02</updated>
+ <updated>2015-03-06T05:43:28</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 a59297e..991ca08 100644
--- a/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/es-ES/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:02</updated>
+ <updated>2015-03-06T05:43:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds-Fedora_Security_Team.xml b/public_html/es-ES/opds-Fedora_Security_Team.xml
index 0680a5d..f3b76b6 100644
--- a/public_html/es-ES/opds-Fedora_Security_Team.xml
+++ b/public_html/es-ES/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/es-ES/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:02</updated>
+ <updated>2015-03-06T05:43:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/es-ES/opds.xml b/public_html/es-ES/opds.xml
index a683a43..582b681 100644
--- a/public_html/es-ES/opds.xml
+++ b/public_html/es-ES/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/es-ES/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:28</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/es-ES/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:25</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:02</updated>
+ <updated>2015-03-06T05:43:27</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Documentación de Contribuyente</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:02</updated>
+ <updated>2015-03-06T05:43:27</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:02</updated>
+ <updated>2015-03-06T05:43:28</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:02</updated>
+ <updated>2015-03-06T05:43:28</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:02</updated>
+ <updated>2015-03-06T05:43:28</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/es-ES/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:02</updated>
+ <updated>2015-03-06T05:43:28</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/es-ES/toc.html b/public_html/es-ES/toc.html
index bbe658f..0daf9ab 100644
--- a/public_html/es-ES/toc.html
+++ b/public_html/es-ES/toc.html
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -909,7 +909,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">
@@ -1642,7 +1642,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>
@@ -1997,7 +1997,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/fa-IR/opds-Community_Services_Infrastructure.xml b/public_html/fa-IR/opds-Community_Services_Infrastructure.xml
index 049f863..cb0578b 100644
--- a/public_html/fa-IR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/fa-IR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:28</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora.xml b/public_html/fa-IR/opds-Fedora.xml
index 8c5c924..99b0e50 100644
--- a/public_html/fa-IR/opds-Fedora.xml
+++ b/public_html/fa-IR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:28</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>fa-IR</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml b/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
index 2998b8e..406f8d9 100644
--- a/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Contributor_Documentation.xml</id>
<title>مستندات مشارکت کننده فدورا</title>
<subtitle>مستندات مشارکت کننده فدورا</subtitle>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:29</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 4801136..d0d088e 100644
--- a/public_html/fa-IR/opds-Fedora_Core.xml
+++ b/public_html/fa-IR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:29</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Documentation.xml b/public_html/fa-IR/opds-Fedora_Documentation.xml
index 21fa760..aa9ebfc 100644
--- a/public_html/fa-IR/opds-Fedora_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:29</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 4883f90..6277d31 100644
--- a/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fa-IR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:29</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds-Fedora_Security_Team.xml b/public_html/fa-IR/opds-Fedora_Security_Team.xml
index ad1fd30..fd766bd 100644
--- a/public_html/fa-IR/opds-Fedora_Security_Team.xml
+++ b/public_html/fa-IR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fa-IR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:29</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fa-IR/opds.xml b/public_html/fa-IR/opds.xml
index 6cbf51d..768a34b 100644
--- a/public_html/fa-IR/opds.xml
+++ b/public_html/fa-IR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/fa-IR/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:29</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/fa-IR/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:28</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:28</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>مستندات مشارکت کننده فدورا</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:29</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:29</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:29</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:29</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/fa-IR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:29</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/fa-IR/toc.html b/public_html/fa-IR/toc.html
index b28ac63..212cb29 100644
--- a/public_html/fa-IR/toc.html
+++ b/public_html/fa-IR/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1453,7 +1453,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1471,7 +1471,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>
@@ -1831,7 +1831,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/fi-FI/opds-Community_Services_Infrastructure.xml b/public_html/fi-FI/opds-Community_Services_Infrastructure.xml
index dc202b2..8bb76b3 100644
--- a/public_html/fi-FI/opds-Community_Services_Infrastructure.xml
+++ b/public_html/fi-FI/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:29</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora.xml b/public_html/fi-FI/opds-Fedora.xml
index 4a6dbf3..72ee9af 100644
--- a/public_html/fi-FI/opds-Fedora.xml
+++ b/public_html/fi-FI/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:04</updated>
+ <updated>2015-03-06T05:43:29</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>fi-FI</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml b/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
index 27ab3c6..4958b7e 100644
--- a/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:04</updated>
+ <updated>2015-03-06T05:43:29</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 50c8359..90f61ec 100644
--- a/public_html/fi-FI/opds-Fedora_Core.xml
+++ b/public_html/fi-FI/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:04</updated>
+ <updated>2015-03-06T05:43:29</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Documentation.xml b/public_html/fi-FI/opds-Fedora_Documentation.xml
index 058fd7c..ffc387d 100644
--- a/public_html/fi-FI/opds-Fedora_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:04</updated>
+ <updated>2015-03-06T05:43:29</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 7887afa..638b1ce 100644
--- a/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fi-FI/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:04</updated>
+ <updated>2015-03-06T05:43:29</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds-Fedora_Security_Team.xml b/public_html/fi-FI/opds-Fedora_Security_Team.xml
index ae454c3..29f6ee7 100644
--- a/public_html/fi-FI/opds-Fedora_Security_Team.xml
+++ b/public_html/fi-FI/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fi-FI/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:04</updated>
+ <updated>2015-03-06T05:43:29</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fi-FI/opds.xml b/public_html/fi-FI/opds.xml
index 29480b8..8e9f639 100644
--- a/public_html/fi-FI/opds.xml
+++ b/public_html/fi-FI/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/fi-FI/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:05</updated>
+ <updated>2015-03-06T05:43:30</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/fi-FI/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:29</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:04</updated>
+ <updated>2015-03-06T05:43:29</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:04</updated>
+ <updated>2015-03-06T05:43:29</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:04</updated>
+ <updated>2015-03-06T05:43:29</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:04</updated>
+ <updated>2015-03-06T05:43:29</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:04</updated>
+ <updated>2015-03-06T05:43:29</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/fi-FI/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:04</updated>
+ <updated>2015-03-06T05:43:29</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/fi-FI/toc.html b/public_html/fi-FI/toc.html
index a97e39b..e95b6a1 100644
--- a/public_html/fi-FI/toc.html
+++ b/public_html/fi-FI/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/fr-FR/opds-Community_Services_Infrastructure.xml b/public_html/fr-FR/opds-Community_Services_Infrastructure.xml
index 5652154..0fe715d 100644
--- a/public_html/fr-FR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/fr-FR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:05</updated>
+ <updated>2015-03-06T05:43:30</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora.xml b/public_html/fr-FR/opds-Fedora.xml
index 9a6f43e..0fb1a30 100644
--- a/public_html/fr-FR/opds-Fedora.xml
+++ b/public_html/fr-FR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:05</updated>
+ <updated>2015-03-06T05:43:31</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>fr-FR</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml b/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
index 6f8c5a9..27bcae3 100644
--- a/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:05</updated>
+ <updated>2015-03-06T05:43:31</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 38e6f45..35231d7 100644
--- a/public_html/fr-FR/opds-Fedora_Core.xml
+++ b/public_html/fr-FR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:05</updated>
+ <updated>2015-03-06T05:43:31</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Documentation.xml b/public_html/fr-FR/opds-Fedora_Documentation.xml
index 4d4002e..7fd1844 100644
--- a/public_html/fr-FR/opds-Fedora_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:05</updated>
+ <updated>2015-03-06T05:43:31</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 0b900c0..4b6220f 100644
--- a/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/fr-FR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds-Fedora_Security_Team.xml b/public_html/fr-FR/opds-Fedora_Security_Team.xml
index 89690c1..47e8fe1 100644
--- a/public_html/fr-FR/opds-Fedora_Security_Team.xml
+++ b/public_html/fr-FR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/fr-FR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/fr-FR/opds.xml b/public_html/fr-FR/opds.xml
index 172d227..df0ff11 100644
--- a/public_html/fr-FR/opds.xml
+++ b/public_html/fr-FR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/fr-FR/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/fr-FR/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:05</updated>
+ <updated>2015-03-06T05:43:30</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:05</updated>
+ <updated>2015-03-06T05:43:31</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:05</updated>
+ <updated>2015-03-06T05:43:31</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:05</updated>
+ <updated>2015-03-06T05:43:31</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:05</updated>
+ <updated>2015-03-06T05:43:31</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/fr-FR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/fr-FR/toc.html b/public_html/fr-FR/toc.html
index 8c3bbf7..0699e86 100644
--- a/public_html/fr-FR/toc.html
+++ b/public_html/fr-FR/toc.html
@@ -402,7 +402,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -484,7 +484,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -528,7 +528,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Resource_Management_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.Resource_Management_Guide.types');">
@@ -1442,7 +1442,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1469,7 +1469,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>
@@ -1824,7 +1824,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/gu-IN/opds-Community_Services_Infrastructure.xml b/public_html/gu-IN/opds-Community_Services_Infrastructure.xml
index c21459e..5c2ae5a 100644
--- a/public_html/gu-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/gu-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora.xml b/public_html/gu-IN/opds-Fedora.xml
index 6b40b3f..29d61b3 100644
--- a/public_html/gu-IN/opds-Fedora.xml
+++ b/public_html/gu-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>gu-IN</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
index 3e936da..ee7dddf 100644
--- a/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</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 9ccc9b9..6fa3029 100644
--- a/public_html/gu-IN/opds-Fedora_Core.xml
+++ b/public_html/gu-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Documentation.xml b/public_html/gu-IN/opds-Fedora_Documentation.xml
index da037d3..ebeeafc 100644
--- a/public_html/gu-IN/opds-Fedora_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</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 31ae127..a6586fd 100644
--- a/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/gu-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:31</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds-Fedora_Security_Team.xml b/public_html/gu-IN/opds-Fedora_Security_Team.xml
index 833afaa..7498655 100644
--- a/public_html/gu-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/gu-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/gu-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:31</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/gu-IN/opds.xml b/public_html/gu-IN/opds.xml
index bb7fd3b..e0a6bf9 100644
--- a/public_html/gu-IN/opds.xml
+++ b/public_html/gu-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/gu-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/gu-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:31</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/gu-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:31</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/gu-IN/toc.html b/public_html/gu-IN/toc.html
index ffbac2d..3e51d88 100644
--- a/public_html/gu-IN/toc.html
+++ b/public_html/gu-IN/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/he-IL/opds-Community_Services_Infrastructure.xml b/public_html/he-IL/opds-Community_Services_Infrastructure.xml
index 62c09ad..80ac7a4 100644
--- a/public_html/he-IL/opds-Community_Services_Infrastructure.xml
+++ b/public_html/he-IL/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora.xml b/public_html/he-IL/opds-Fedora.xml
index 09bc915..fcaeba3 100644
--- a/public_html/he-IL/opds-Fedora.xml
+++ b/public_html/he-IL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>he-IL</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml b/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
index 983f1d9..8a13aa8 100644
--- a/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</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 f950593..88d2986 100644
--- a/public_html/he-IL/opds-Fedora_Core.xml
+++ b/public_html/he-IL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Documentation.xml b/public_html/he-IL/opds-Fedora_Documentation.xml
index d481f25..5c2facf 100644
--- a/public_html/he-IL/opds-Fedora_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</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 5781a00..be2730f 100644
--- a/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/he-IL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds-Fedora_Security_Team.xml b/public_html/he-IL/opds-Fedora_Security_Team.xml
index bf24445..3805941 100644
--- a/public_html/he-IL/opds-Fedora_Security_Team.xml
+++ b/public_html/he-IL/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/he-IL/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/he-IL/opds.xml b/public_html/he-IL/opds.xml
index 83e0060..84653d5 100644
--- a/public_html/he-IL/opds.xml
+++ b/public_html/he-IL/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/he-IL/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:32</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/he-IL/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/he-IL/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/he-IL/toc.html b/public_html/he-IL/toc.html
index 60d4add..df620b0 100644
--- a/public_html/he-IL/toc.html
+++ b/public_html/he-IL/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -697,7 +697,7 @@
<a class="type" href="./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-he-IL.epub" >epub</a>
<a class="type" href="./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-he-IL.pdf" onclick="window.top.location='./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-he-IL.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-he-IL.pdf" onclick="window.top.location='./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-he-IL.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15' class="version collapsed untranslated" onclick="toggle(event, 'Fedora.15.untrans_books');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/hi-IN/opds-Community_Services_Infrastructure.xml b/public_html/hi-IN/opds-Community_Services_Infrastructure.xml
index 60e64b3..1c74a23 100644
--- a/public_html/hi-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/hi-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:32</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora.xml b/public_html/hi-IN/opds-Fedora.xml
index d2ef0ae..990b243 100644
--- a/public_html/hi-IN/opds-Fedora.xml
+++ b/public_html/hi-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:33</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>hi-IN</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
index b6ba6b0..c88382a 100644
--- a/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:33</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 45aaac6..8359618 100644
--- a/public_html/hi-IN/opds-Fedora_Core.xml
+++ b/public_html/hi-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:33</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Documentation.xml b/public_html/hi-IN/opds-Fedora_Documentation.xml
index 68e90a3..3b04475 100644
--- a/public_html/hi-IN/opds-Fedora_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:33</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 92f005e..373f320 100644
--- a/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/hi-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:33</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds-Fedora_Security_Team.xml b/public_html/hi-IN/opds-Fedora_Security_Team.xml
index e20327a..0810bbc 100644
--- a/public_html/hi-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/hi-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hi-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:33</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hi-IN/opds.xml b/public_html/hi-IN/opds.xml
index ecf4c75..dc1cdfe 100644
--- a/public_html/hi-IN/opds.xml
+++ b/public_html/hi-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/hi-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:09</updated>
+ <updated>2015-03-06T05:43:33</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/hi-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:32</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:33</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:33</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:33</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:33</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:33</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/hi-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:33</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/hi-IN/toc.html b/public_html/hi-IN/toc.html
index 08e0994..c187232 100644
--- a/public_html/hi-IN/toc.html
+++ b/public_html/hi-IN/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/hu-HU/opds-Community_Services_Infrastructure.xml b/public_html/hu-HU/opds-Community_Services_Infrastructure.xml
index b7d3f88..8c8f921 100644
--- a/public_html/hu-HU/opds-Community_Services_Infrastructure.xml
+++ b/public_html/hu-HU/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:09</updated>
+ <updated>2015-03-06T05:43:33</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora.xml b/public_html/hu-HU/opds-Fedora.xml
index 59419bd..ccf414a 100644
--- a/public_html/hu-HU/opds-Fedora.xml
+++ b/public_html/hu-HU/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:09</updated>
+ <updated>2015-03-06T05:43:33</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>hu-HU</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml b/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
index da13983..237dea5 100644
--- a/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:09</updated>
+ <updated>2015-03-06T05:43:33</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 46412ab..16dcef1 100644
--- a/public_html/hu-HU/opds-Fedora_Core.xml
+++ b/public_html/hu-HU/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:10</updated>
+ <updated>2015-03-06T05:43:33</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Documentation.xml b/public_html/hu-HU/opds-Fedora_Documentation.xml
index a1afa9b..2d3d577 100644
--- a/public_html/hu-HU/opds-Fedora_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:10</updated>
+ <updated>2015-03-06T05:43:33</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 091911d..afb7ac3 100644
--- a/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/hu-HU/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:10</updated>
+ <updated>2015-03-06T05:43:33</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds-Fedora_Security_Team.xml b/public_html/hu-HU/opds-Fedora_Security_Team.xml
index 6b20cad..856db40 100644
--- a/public_html/hu-HU/opds-Fedora_Security_Team.xml
+++ b/public_html/hu-HU/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/hu-HU/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:10</updated>
+ <updated>2015-03-06T05:43:34</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/hu-HU/opds.xml b/public_html/hu-HU/opds.xml
index 3a59e96..7b00e64 100644
--- a/public_html/hu-HU/opds.xml
+++ b/public_html/hu-HU/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/hu-HU/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:10</updated>
+ <updated>2015-03-06T05:43:34</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/hu-HU/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:09</updated>
+ <updated>2015-03-06T05:43:33</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:09</updated>
+ <updated>2015-03-06T05:43:33</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:09</updated>
+ <updated>2015-03-06T05:43:33</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:10</updated>
+ <updated>2015-03-06T05:43:33</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:10</updated>
+ <updated>2015-03-06T05:43:33</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:10</updated>
+ <updated>2015-03-06T05:43:34</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/hu-HU/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:10</updated>
+ <updated>2015-03-06T05:43:34</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/hu-HU/toc.html b/public_html/hu-HU/toc.html
index 5a83da7..4fc943e 100644
--- a/public_html/hu-HU/toc.html
+++ b/public_html/hu-HU/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ia/opds-Community_Services_Infrastructure.xml b/public_html/ia/opds-Community_Services_Infrastructure.xml
index c2cb0ec..43154ca 100644
--- a/public_html/ia/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ia/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:10</updated>
+ <updated>2015-03-06T05:43:34</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora.xml b/public_html/ia/opds-Fedora.xml
index 811f518..daf2c4b 100644
--- a/public_html/ia/opds-Fedora.xml
+++ b/public_html/ia/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>ia</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/ia/opds-Fedora_Contributor_Documentation.xml b/public_html/ia/opds-Fedora_Contributor_Documentation.xml
index a35baa2..f8b708e 100644
--- a/public_html/ia/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ia/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora_Core.xml b/public_html/ia/opds-Fedora_Core.xml
index 9313f70..5458c92 100644
--- a/public_html/ia/opds-Fedora_Core.xml
+++ b/public_html/ia/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora_Documentation.xml b/public_html/ia/opds-Fedora_Documentation.xml
index cc87781..15ad239 100644
--- a/public_html/ia/opds-Fedora_Documentation.xml
+++ b/public_html/ia/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora_Draft_Documentation.xml b/public_html/ia/opds-Fedora_Draft_Documentation.xml
index 51c34f1..d9422d9 100644
--- a/public_html/ia/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ia/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds-Fedora_Security_Team.xml b/public_html/ia/opds-Fedora_Security_Team.xml
index c226964..1a2ecfd 100644
--- a/public_html/ia/opds-Fedora_Security_Team.xml
+++ b/public_html/ia/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ia/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ia/opds.xml b/public_html/ia/opds.xml
index 9172be4..c5368d8 100644
--- a/public_html/ia/opds.xml
+++ b/public_html/ia/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ia/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ia/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:10</updated>
+ <updated>2015-03-06T05:43:34</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ia/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ia/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ia/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ia/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ia/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ia/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ia/toc.html b/public_html/ia/toc.html
index f2c97f3..31c38f7 100644
--- a/public_html/ia/toc.html
+++ b/public_html/ia/toc.html
@@ -402,7 +402,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/id-ID/opds-Community_Services_Infrastructure.xml b/public_html/id-ID/opds-Community_Services_Infrastructure.xml
index 6d8fe8b..22753ec 100644
--- a/public_html/id-ID/opds-Community_Services_Infrastructure.xml
+++ b/public_html/id-ID/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora.xml b/public_html/id-ID/opds-Fedora.xml
index c22ba09..a5a80ce 100644
--- a/public_html/id-ID/opds-Fedora.xml
+++ b/public_html/id-ID/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:34</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>id-ID</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml b/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
index 8bf4d4c..5f38698 100644
--- a/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:34</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 8dba506..93d3d6d 100644
--- a/public_html/id-ID/opds-Fedora_Core.xml
+++ b/public_html/id-ID/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:35</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Documentation.xml b/public_html/id-ID/opds-Fedora_Documentation.xml
index 61fbb40..1a0ea39 100644
--- a/public_html/id-ID/opds-Fedora_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:35</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 6af38fc..b221704 100644
--- a/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/id-ID/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:35</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds-Fedora_Security_Team.xml b/public_html/id-ID/opds-Fedora_Security_Team.xml
index 54cb678..7754f9d 100644
--- a/public_html/id-ID/opds-Fedora_Security_Team.xml
+++ b/public_html/id-ID/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/id-ID/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:35</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/id-ID/opds.xml b/public_html/id-ID/opds.xml
index 2c3f218..e649308 100644
--- a/public_html/id-ID/opds.xml
+++ b/public_html/id-ID/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/id-ID/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:35</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/id-ID/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:34</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:35</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:35</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:35</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:35</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/id-ID/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:35</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/id-ID/toc.html b/public_html/id-ID/toc.html
index 2cd151f..902823f 100644
--- a/public_html/id-ID/toc.html
+++ b/public_html/id-ID/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/it-IT/opds-Community_Services_Infrastructure.xml b/public_html/it-IT/opds-Community_Services_Infrastructure.xml
index 18db1da..9b825bf 100644
--- a/public_html/it-IT/opds-Community_Services_Infrastructure.xml
+++ b/public_html/it-IT/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:35</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora.xml b/public_html/it-IT/opds-Fedora.xml
index 562067c..ad017ea 100644
--- a/public_html/it-IT/opds-Fedora.xml
+++ b/public_html/it-IT/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:37</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>it-IT</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml b/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
index 5b62c14..6370db3 100644
--- a/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Contributor_Documentation.xml</id>
<title>Documentazione Collaboratori Fedora</title>
<subtitle>Documentazione Collaboratori Fedora</subtitle>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:37</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 cb4383f..5c3269b 100644
--- a/public_html/it-IT/opds-Fedora_Core.xml
+++ b/public_html/it-IT/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:37</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Documentation.xml b/public_html/it-IT/opds-Fedora_Documentation.xml
index 40373d8..c4341ac 100644
--- a/public_html/it-IT/opds-Fedora_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:37</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 006d7c7..cbcc80e 100644
--- a/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/it-IT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:37</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds-Fedora_Security_Team.xml b/public_html/it-IT/opds-Fedora_Security_Team.xml
index 6a0f3e5..2e6e490 100644
--- a/public_html/it-IT/opds-Fedora_Security_Team.xml
+++ b/public_html/it-IT/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/it-IT/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:37</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/it-IT/opds.xml b/public_html/it-IT/opds.xml
index 05c26f5..8e7c814 100644
--- a/public_html/it-IT/opds.xml
+++ b/public_html/it-IT/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/it-IT/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:38</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/it-IT/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:36</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:37</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Documentazione Collaboratori Fedora</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:37</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:37</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:37</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:37</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/it-IT/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:37</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/it-IT/toc.html b/public_html/it-IT/toc.html
index 0eca6b0..dbfe7d3 100644
--- a/public_html/it-IT/toc.html
+++ b/public_html/it-IT/toc.html
@@ -484,7 +484,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -528,7 +528,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Resource_Management_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.Resource_Management_Guide.types');">
@@ -1643,7 +1643,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1661,7 +1661,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>
@@ -2021,7 +2021,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ja-JP/opds-Community_Services_Infrastructure.xml b/public_html/ja-JP/opds-Community_Services_Infrastructure.xml
index c3cdc01..179514f 100644
--- a/public_html/ja-JP/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ja-JP/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:38</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora.xml b/public_html/ja-JP/opds-Fedora.xml
index 6b86064..496b445 100644
--- a/public_html/ja-JP/opds-Fedora.xml
+++ b/public_html/ja-JP/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</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 644805c..e614822 100644
--- a/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora コントリビュータ用ドキュメント</title>
<subtitle>Fedora コントリビュータ用ドキュメント</subtitle>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</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 d6175d2..9205814 100644
--- a/public_html/ja-JP/opds-Fedora_Core.xml
+++ b/public_html/ja-JP/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Documentation.xml b/public_html/ja-JP/opds-Fedora_Documentation.xml
index d9e5f7f..d090709 100644
--- a/public_html/ja-JP/opds-Fedora_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</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 e9ce22a..3abab89 100644
--- a/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ja-JP/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds-Fedora_Security_Team.xml b/public_html/ja-JP/opds-Fedora_Security_Team.xml
index 913bf01..3d52383 100644
--- a/public_html/ja-JP/opds-Fedora_Security_Team.xml
+++ b/public_html/ja-JP/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ja-JP/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ja-JP/opds.xml b/public_html/ja-JP/opds.xml
index d30d1ad..818e93c 100644
--- a/public_html/ja-JP/opds.xml
+++ b/public_html/ja-JP/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ja-JP/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ja-JP/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:38</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora コントリビュータ用ドキュメント</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ja-JP/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ja-JP/toc.html b/public_html/ja-JP/toc.html
index a39a035..0f086e2 100644
--- a/public_html/ja-JP/toc.html
+++ b/public_html/ja-JP/toc.html
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -537,7 +537,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Resource_Management_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.Resource_Management_Guide.types');">
@@ -695,7 +695,7 @@
<a class="type" href="./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-ja-JP.epub" >epub</a>
<a class="type" href="./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-ja-JP.pdf" onclick="window.top.location='./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-ja-JP.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-ja-JP.pdf" onclick="window.top.location='./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-ja-JP.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed">
@@ -1490,7 +1490,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1508,7 +1508,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>
@@ -1863,7 +1863,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/kn-IN/opds-Community_Services_Infrastructure.xml b/public_html/kn-IN/opds-Community_Services_Infrastructure.xml
index 261331e..dd9688c 100644
--- a/public_html/kn-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/kn-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora.xml b/public_html/kn-IN/opds-Fedora.xml
index 8a99735..b117151 100644
--- a/public_html/kn-IN/opds-Fedora.xml
+++ b/public_html/kn-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:40</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>kn-IN</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
index 2bccb5f..f186488 100644
--- a/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:40</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 0ddb9c5..092bdbf 100644
--- a/public_html/kn-IN/opds-Fedora_Core.xml
+++ b/public_html/kn-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Documentation.xml b/public_html/kn-IN/opds-Fedora_Documentation.xml
index 7dbc337..8a67a8a 100644
--- a/public_html/kn-IN/opds-Fedora_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:40</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 0af1666..8d37083 100644
--- a/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/kn-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds-Fedora_Security_Team.xml b/public_html/kn-IN/opds-Fedora_Security_Team.xml
index c9573ee..937ed1f 100644
--- a/public_html/kn-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/kn-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/kn-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/kn-IN/opds.xml b/public_html/kn-IN/opds.xml
index 31f8502..a84547e 100644
--- a/public_html/kn-IN/opds.xml
+++ b/public_html/kn-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/kn-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:40</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/kn-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:40</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:40</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:40</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:40</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:40</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/kn-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:40</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/kn-IN/toc.html b/public_html/kn-IN/toc.html
index 6c3b3ea..3e24587 100644
--- a/public_html/kn-IN/toc.html
+++ b/public_html/kn-IN/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ko-KR/opds-Community_Services_Infrastructure.xml b/public_html/ko-KR/opds-Community_Services_Infrastructure.xml
index d258aaa..44ccb63 100644
--- a/public_html/ko-KR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ko-KR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:40</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora.xml b/public_html/ko-KR/opds-Fedora.xml
index ecbe908..94cd9cb 100644
--- a/public_html/ko-KR/opds-Fedora.xml
+++ b/public_html/ko-KR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:17</updated>
+ <updated>2015-03-06T05:43:41</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>ko-KR</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml b/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
index 7fc6986..9ea7bb3 100644
--- a/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:17</updated>
+ <updated>2015-03-06T05:43:41</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 d51393c..eebbdb9 100644
--- a/public_html/ko-KR/opds-Fedora_Core.xml
+++ b/public_html/ko-KR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:17</updated>
+ <updated>2015-03-06T05:43:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Documentation.xml b/public_html/ko-KR/opds-Fedora_Documentation.xml
index 77d0fe2..0aefee3 100644
--- a/public_html/ko-KR/opds-Fedora_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:17</updated>
+ <updated>2015-03-06T05:43:41</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 ba73e91..a71fd6b 100644
--- a/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ko-KR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:17</updated>
+ <updated>2015-03-06T05:43:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds-Fedora_Security_Team.xml b/public_html/ko-KR/opds-Fedora_Security_Team.xml
index 9fc4c5f..ccf54a3 100644
--- a/public_html/ko-KR/opds-Fedora_Security_Team.xml
+++ b/public_html/ko-KR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ko-KR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:17</updated>
+ <updated>2015-03-06T05:43:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ko-KR/opds.xml b/public_html/ko-KR/opds.xml
index 09adcec..5bfa6f6 100644
--- a/public_html/ko-KR/opds.xml
+++ b/public_html/ko-KR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ko-KR/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:17</updated>
+ <updated>2015-03-06T05:43:41</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ko-KR/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:41</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:17</updated>
+ <updated>2015-03-06T05:43:41</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:17</updated>
+ <updated>2015-03-06T05:43:41</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:17</updated>
+ <updated>2015-03-06T05:43:41</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:17</updated>
+ <updated>2015-03-06T05:43:41</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:17</updated>
+ <updated>2015-03-06T05:43:41</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ko-KR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:17</updated>
+ <updated>2015-03-06T05:43:41</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ko-KR/toc.html b/public_html/ko-KR/toc.html
index f165200..de59b81 100644
--- a/public_html/ko-KR/toc.html
+++ b/public_html/ko-KR/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/lt-LT/opds-Community_Services_Infrastructure.xml b/public_html/lt-LT/opds-Community_Services_Infrastructure.xml
index 131bdbc..415a19d 100644
--- a/public_html/lt-LT/opds-Community_Services_Infrastructure.xml
+++ b/public_html/lt-LT/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/lt-LT/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:18</updated>
+ <updated>2015-03-06T05:43:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds-Fedora.xml b/public_html/lt-LT/opds-Fedora.xml
index 28d3455..00a098b 100644
--- a/public_html/lt-LT/opds-Fedora.xml
+++ b/public_html/lt-LT/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/lt-LT/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:18</updated>
+ <updated>2015-03-06T05:43:41</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>lt-LT</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml b/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml
index ddccac0..3dc56f5 100644
--- a/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/lt-LT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/lt-LT/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:18</updated>
+ <updated>2015-03-06T05:43:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds-Fedora_Core.xml b/public_html/lt-LT/opds-Fedora_Core.xml
index fcc7cbc..d76b70a 100644
--- a/public_html/lt-LT/opds-Fedora_Core.xml
+++ b/public_html/lt-LT/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/lt-LT/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:18</updated>
+ <updated>2015-03-06T05:43:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds-Fedora_Documentation.xml b/public_html/lt-LT/opds-Fedora_Documentation.xml
index a880403..8b7e42f 100644
--- a/public_html/lt-LT/opds-Fedora_Documentation.xml
+++ b/public_html/lt-LT/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/lt-LT/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:18</updated>
+ <updated>2015-03-06T05:43:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds-Fedora_Draft_Documentation.xml b/public_html/lt-LT/opds-Fedora_Draft_Documentation.xml
index 4270f53..ce5051a 100644
--- a/public_html/lt-LT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/lt-LT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/lt-LT/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:19</updated>
+ <updated>2015-03-06T05:43:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds-Fedora_Security_Team.xml b/public_html/lt-LT/opds-Fedora_Security_Team.xml
index a2d0ca0..58ec161 100644
--- a/public_html/lt-LT/opds-Fedora_Security_Team.xml
+++ b/public_html/lt-LT/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/lt-LT/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:19</updated>
+ <updated>2015-03-06T05:43:41</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/lt-LT/opds.xml b/public_html/lt-LT/opds.xml
index 723388c..98520e4 100644
--- a/public_html/lt-LT/opds.xml
+++ b/public_html/lt-LT/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/lt-LT/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:19</updated>
+ <updated>2015-03-06T05:43:42</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/lt-LT/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:18</updated>
+ <updated>2015-03-06T05:43:41</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/lt-LT/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:18</updated>
+ <updated>2015-03-06T05:43:41</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/lt-LT/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:18</updated>
+ <updated>2015-03-06T05:43:41</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/lt-LT/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:18</updated>
+ <updated>2015-03-06T05:43:41</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/lt-LT/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:18</updated>
+ <updated>2015-03-06T05:43:41</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/lt-LT/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:19</updated>
+ <updated>2015-03-06T05:43:41</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/lt-LT/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:19</updated>
+ <updated>2015-03-06T05:43:41</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/lt-LT/toc.html b/public_html/lt-LT/toc.html
index 20e4093..6595657 100644
--- a/public_html/lt-LT/toc.html
+++ b/public_html/lt-LT/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ml-IN/opds-Community_Services_Infrastructure.xml b/public_html/ml-IN/opds-Community_Services_Infrastructure.xml
index 23838fc..04e42dd 100644
--- a/public_html/ml-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ml-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:19</updated>
+ <updated>2015-03-06T05:43:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora.xml b/public_html/ml-IN/opds-Fedora.xml
index 14e8dd4..50c042e 100644
--- a/public_html/ml-IN/opds-Fedora.xml
+++ b/public_html/ml-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:19</updated>
+ <updated>2015-03-06T05:43:42</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>ml-IN</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
index de19bf3..c581c1c 100644
--- a/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:19</updated>
+ <updated>2015-03-06T05:43:42</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 5a8d4f5..1032c3c 100644
--- a/public_html/ml-IN/opds-Fedora_Core.xml
+++ b/public_html/ml-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Documentation.xml b/public_html/ml-IN/opds-Fedora_Documentation.xml
index 3bd32af..4640afc 100644
--- a/public_html/ml-IN/opds-Fedora_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:42</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 d60a0b6..c807f16 100644
--- a/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ml-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds-Fedora_Security_Team.xml b/public_html/ml-IN/opds-Fedora_Security_Team.xml
index 7ec9f31..0e18788 100644
--- a/public_html/ml-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/ml-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ml-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ml-IN/opds.xml b/public_html/ml-IN/opds.xml
index c318257..3abb7d5 100644
--- a/public_html/ml-IN/opds.xml
+++ b/public_html/ml-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ml-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:42</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ml-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:19</updated>
+ <updated>2015-03-06T05:43:42</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:19</updated>
+ <updated>2015-03-06T05:43:42</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:19</updated>
+ <updated>2015-03-06T05:43:42</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:42</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:42</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:42</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ml-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:42</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ml-IN/toc.html b/public_html/ml-IN/toc.html
index 1f13d3f..4f95ef6 100644
--- a/public_html/ml-IN/toc.html
+++ b/public_html/ml-IN/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/mr-IN/opds-Community_Services_Infrastructure.xml b/public_html/mr-IN/opds-Community_Services_Infrastructure.xml
index f9a5b59..85a5303 100644
--- a/public_html/mr-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/mr-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:42</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora.xml b/public_html/mr-IN/opds-Fedora.xml
index b576bb3..35e25fb 100644
--- a/public_html/mr-IN/opds-Fedora.xml
+++ b/public_html/mr-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:43</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>mr-IN</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
index f6ed09a..9e5dc2a 100644
--- a/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43: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 974de79..d7ce495 100644
--- a/public_html/mr-IN/opds-Fedora_Core.xml
+++ b/public_html/mr-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Documentation.xml b/public_html/mr-IN/opds-Fedora_Documentation.xml
index 5181695..cc4fb6e 100644
--- a/public_html/mr-IN/opds-Fedora_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43: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 90e26a6..d270721 100644
--- a/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/mr-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:21</updated>
+ <updated>2015-03-06T05:43:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds-Fedora_Security_Team.xml b/public_html/mr-IN/opds-Fedora_Security_Team.xml
index 9c1ff99..ab21bd8 100644
--- a/public_html/mr-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/mr-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/mr-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:21</updated>
+ <updated>2015-03-06T05:43:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/mr-IN/opds.xml b/public_html/mr-IN/opds.xml
index a09a314..d373f6b 100644
--- a/public_html/mr-IN/opds.xml
+++ b/public_html/mr-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/mr-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:21</updated>
+ <updated>2015-03-06T05:43:43</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/mr-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:42</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:43</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:43</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:43</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:43</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:21</updated>
+ <updated>2015-03-06T05:43:43</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/mr-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:21</updated>
+ <updated>2015-03-06T05:43:43</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/mr-IN/toc.html b/public_html/mr-IN/toc.html
index 0b3f17d..cdb4855 100644
--- a/public_html/mr-IN/toc.html
+++ b/public_html/mr-IN/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/nb-NO/opds-Community_Services_Infrastructure.xml b/public_html/nb-NO/opds-Community_Services_Infrastructure.xml
index bb910ce..53ad719 100644
--- a/public_html/nb-NO/opds-Community_Services_Infrastructure.xml
+++ b/public_html/nb-NO/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:21</updated>
+ <updated>2015-03-06T05:43:43</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora.xml b/public_html/nb-NO/opds-Fedora.xml
index d544bd6..3876f43 100644
--- a/public_html/nb-NO/opds-Fedora.xml
+++ b/public_html/nb-NO/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:21</updated>
+ <updated>2015-03-06T05:43:43</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>nb-NO</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml b/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
index e40d967..2cc9b01 100644
--- a/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:21</updated>
+ <updated>2015-03-06T05:43:44</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 cae1dce..d6353a0 100644
--- a/public_html/nb-NO/opds-Fedora_Core.xml
+++ b/public_html/nb-NO/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:21</updated>
+ <updated>2015-03-06T05:43:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Documentation.xml b/public_html/nb-NO/opds-Fedora_Documentation.xml
index a1c70c6..f4eeba4 100644
--- a/public_html/nb-NO/opds-Fedora_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:22</updated>
+ <updated>2015-03-06T05:43:44</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 224bc08..7d29128 100644
--- a/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/nb-NO/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:22</updated>
+ <updated>2015-03-06T05:43:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds-Fedora_Security_Team.xml b/public_html/nb-NO/opds-Fedora_Security_Team.xml
index 1db464d..4785d6e 100644
--- a/public_html/nb-NO/opds-Fedora_Security_Team.xml
+++ b/public_html/nb-NO/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nb-NO/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:22</updated>
+ <updated>2015-03-06T05:43:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nb-NO/opds.xml b/public_html/nb-NO/opds.xml
index beaecd7..7e26b55 100644
--- a/public_html/nb-NO/opds.xml
+++ b/public_html/nb-NO/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/nb-NO/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:22</updated>
+ <updated>2015-03-06T05:43:44</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/nb-NO/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:21</updated>
+ <updated>2015-03-06T05:43:43</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:21</updated>
+ <updated>2015-03-06T05:43:44</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:21</updated>
+ <updated>2015-03-06T05:43:44</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:22</updated>
+ <updated>2015-03-06T05:43:44</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:22</updated>
+ <updated>2015-03-06T05:43:44</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:22</updated>
+ <updated>2015-03-06T05:43:44</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/nb-NO/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:22</updated>
+ <updated>2015-03-06T05:43:44</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/nb-NO/toc.html b/public_html/nb-NO/toc.html
index 7db6b3a..94fbed2 100644
--- a/public_html/nb-NO/toc.html
+++ b/public_html/nb-NO/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/nl-NL/opds-Community_Services_Infrastructure.xml b/public_html/nl-NL/opds-Community_Services_Infrastructure.xml
index 217e9d3..b236dd1 100644
--- a/public_html/nl-NL/opds-Community_Services_Infrastructure.xml
+++ b/public_html/nl-NL/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:22</updated>
+ <updated>2015-03-06T05:43:44</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora.xml b/public_html/nl-NL/opds-Fedora.xml
index 5774577..c4ab1c9 100644
--- a/public_html/nl-NL/opds-Fedora.xml
+++ b/public_html/nl-NL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:23</updated>
+ <updated>2015-03-06T05:43:45</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>nl-NL</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml b/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
index 780850c..1f572c5 100644
--- a/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:23</updated>
+ <updated>2015-03-06T05:43:45</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 8fd815d..bb36d18 100644
--- a/public_html/nl-NL/opds-Fedora_Core.xml
+++ b/public_html/nl-NL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:23</updated>
+ <updated>2015-03-06T05:43:45</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Documentation.xml b/public_html/nl-NL/opds-Fedora_Documentation.xml
index fc9312b..0ff2a90 100644
--- a/public_html/nl-NL/opds-Fedora_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:23</updated>
+ <updated>2015-03-06T05:43:45</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 c44985a..840f121 100644
--- a/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/nl-NL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:23</updated>
+ <updated>2015-03-06T05:43:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds-Fedora_Security_Team.xml b/public_html/nl-NL/opds-Fedora_Security_Team.xml
index 51dead1..bfc10df 100644
--- a/public_html/nl-NL/opds-Fedora_Security_Team.xml
+++ b/public_html/nl-NL/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/nl-NL/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:23</updated>
+ <updated>2015-03-06T05:43:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/nl-NL/opds.xml b/public_html/nl-NL/opds.xml
index 50cca01..c5399cd 100644
--- a/public_html/nl-NL/opds.xml
+++ b/public_html/nl-NL/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/nl-NL/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/nl-NL/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:22</updated>
+ <updated>2015-03-06T05:43:44</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:23</updated>
+ <updated>2015-03-06T05:43:45</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:23</updated>
+ <updated>2015-03-06T05:43:45</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:23</updated>
+ <updated>2015-03-06T05:43:45</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:23</updated>
+ <updated>2015-03-06T05:43:46</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:23</updated>
+ <updated>2015-03-06T05:43:46</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/nl-NL/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:23</updated>
+ <updated>2015-03-06T05:43:46</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/nl-NL/toc.html b/public_html/nl-NL/toc.html
index a4eab10..28b2010 100644
--- a/public_html/nl-NL/toc.html
+++ b/public_html/nl-NL/toc.html
@@ -355,7 +355,7 @@
<a class="type" href="./Fedora/18/epub/Virtualization_Getting_Started_Guide/Fedora-18-Virtualization_Getting_Started_Guide-nl-NL.epub" >epub</a>
<a class="type" href="./Fedora/18/html/Virtualization_Getting_Started_Guide/index.html" onclick="window.top.location='./Fedora/18/html/Virtualization_Getting_Started_Guide/index.html';return false;">html</a>
<a class="type" href="./Fedora/18/html-single/Virtualization_Getting_Started_Guide/index.html" onclick="window.top.location='./Fedora/18/html-single/Virtualization_Getting_Started_Guide/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/18/pdf/Virtualization_Getting_Started_Guide/Fedora-18-Virtualization_Getting_Started_Guide-nl-NL.pdf" onclick="window.top.location='./Fedora/18/pdf/Virtualization_Getting_Started_Guide/Fedora-18-Virtualization_Getting_Started_Guide-nl-NL.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/18/pdf/Virtualization_Getting_Started_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Getting_Started_Guide-nl-NL.pdf" onclick="window.top.location='./Fedora/18/pdf/Virtualization_Getting_Started_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Getting_Started_Guide-nl-NL.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18' class="version collapsed untranslated" onclick="toggle(event, 'Fedora.18.untrans_books');">
@@ -411,7 +411,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -484,7 +484,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -528,7 +528,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Resource_Management_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.Resource_Management_Guide.types');">
@@ -697,7 +697,7 @@
<a class="type" href="./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-nl-NL.epub" >epub</a>
<a class="type" href="./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-nl-NL.pdf" onclick="window.top.location='./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-nl-NL.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-nl-NL.pdf" onclick="window.top.location='./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-nl-NL.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Fedora_Live_Images' class="book collapsed">
@@ -909,7 +909,7 @@
<a class="type" href="./Fedora/13/epub/Accessibility_Guide/Fedora-13-Accessibility_Guide-nl-NL.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-nl-NL.pdf" onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-nl-NL.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-nl-NL.pdf" onclick="window.top.location='./Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-nl-NL.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.13.Burning_ISO_images_to_disc' class="book collapsed">
@@ -1261,7 +1261,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">
@@ -1660,7 +1660,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1687,7 +1687,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>
@@ -2042,7 +2042,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/opds.xml b/public_html/opds.xml
index 8534b1d..514677b 100644
--- a/public_html/opds.xml
+++ b/public_html/opds.xml
@@ -7,7 +7,7 @@
<link rel="start" href="http://docs.fedoraproject.org/opds.xml" type="application/atom+xml;type=feed;profile=opds-catalog"/>
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<title>Fedora Documentation</title>
- <updated>2015-03-03T16:19:45</updated>
+ <updated>2015-03-06T05:44:02</updated>
<!--author>
<name></name>
<uri></uri>
@@ -16,7 +16,7 @@
<entry>
<title>অসমীয়া</title>
<id>as-IN/opds.xml</id>
- <updated>2015-03-03T16:18:52</updated>
+ <updated>2015-03-06T05:43:18</updated>
<dc:language>as-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="as-IN/opds.xml"/>
@@ -24,7 +24,7 @@
<entry>
<title>български</title>
<id>bg-BG/opds.xml</id>
- <updated>2015-03-03T16:18:53</updated>
+ <updated>2015-03-06T05:43:19</updated>
<dc:language>bg-BG</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bg-BG/opds.xml"/>
@@ -32,7 +32,7 @@
<entry>
<title>বাংলা</title>
<id>bn-IN/opds.xml</id>
- <updated>2015-03-03T16:18:54</updated>
+ <updated>2015-03-06T05:43:19</updated>
<dc:language>bn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bn-IN/opds.xml"/>
@@ -40,7 +40,7 @@
<entry>
<title>Bosanski</title>
<id>bs-BA/opds.xml</id>
- <updated>2015-03-03T16:18:55</updated>
+ <updated>2015-03-06T05:43:20</updated>
<dc:language>bs-BA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="bs-BA/opds.xml"/>
@@ -48,7 +48,7 @@
<entry>
<title>Català</title>
<id>ca-ES/opds.xml</id>
- <updated>2015-03-03T16:18:56</updated>
+ <updated>2015-03-06T05:43:21</updated>
<dc:language>ca-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ca-ES/opds.xml"/>
@@ -56,7 +56,7 @@
<entry>
<title>Čeština</title>
<id>cs-CZ/opds.xml</id>
- <updated>2015-03-03T16:18:57</updated>
+ <updated>2015-03-06T05:43:22</updated>
<dc:language>cs-CZ</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="cs-CZ/opds.xml"/>
@@ -64,7 +64,7 @@
<entry>
<title>Dansk</title>
<id>da-DK/opds.xml</id>
- <updated>2015-03-03T16:18:58</updated>
+ <updated>2015-03-06T05:43:23</updated>
<dc:language>da-DK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="da-DK/opds.xml"/>
@@ -72,7 +72,7 @@
<entry>
<title>Deutsch</title>
<id>de-DE/opds.xml</id>
- <updated>2015-03-03T16:18:59</updated>
+ <updated>2015-03-06T05:43:23</updated>
<dc:language>de-DE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="de-DE/opds.xml"/>
@@ -80,7 +80,7 @@
<entry>
<title>Ελληνικά</title>
<id>el-GR/opds.xml</id>
- <updated>2015-03-03T16:19:00</updated>
+ <updated>2015-03-06T05:43:24</updated>
<dc:language>el-GR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="el-GR/opds.xml"/>
@@ -88,7 +88,7 @@
<entry>
<title>English</title>
<id>en-US/opds.xml</id>
- <updated>2015-03-03T16:19:01</updated>
+ <updated>2015-03-06T05:43:25</updated>
<dc:language>en-US</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="en-US/opds.xml"/>
@@ -96,7 +96,7 @@
<entry>
<title>Español</title>
<id>es-ES/opds.xml</id>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:28</updated>
<dc:language>es-ES</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="es-ES/opds.xml"/>
@@ -104,7 +104,7 @@
<entry>
<title>فارسی</title>
<id>fa-IR/opds.xml</id>
- <updated>2015-03-03T16:19:03</updated>
+ <updated>2015-03-06T05:43:29</updated>
<dc:language>fa-IR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fa-IR/opds.xml"/>
@@ -112,7 +112,7 @@
<entry>
<title>Suomi</title>
<id>fi-FI/opds.xml</id>
- <updated>2015-03-03T16:19:05</updated>
+ <updated>2015-03-06T05:43:30</updated>
<dc:language>fi-FI</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fi-FI/opds.xml"/>
@@ -120,7 +120,7 @@
<entry>
<title>Français</title>
<id>fr-FR/opds.xml</id>
- <updated>2015-03-03T16:19:06</updated>
+ <updated>2015-03-06T05:43:31</updated>
<dc:language>fr-FR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="fr-FR/opds.xml"/>
@@ -128,7 +128,7 @@
<entry>
<title>ગુજરાતી</title>
<id>gu-IN/opds.xml</id>
- <updated>2015-03-03T16:19:07</updated>
+ <updated>2015-03-06T05:43:32</updated>
<dc:language>gu-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="gu-IN/opds.xml"/>
@@ -136,7 +136,7 @@
<entry>
<title>עברית</title>
<id>he-IL/opds.xml</id>
- <updated>2015-03-03T16:19:08</updated>
+ <updated>2015-03-06T05:43:32</updated>
<dc:language>he-IL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="he-IL/opds.xml"/>
@@ -144,7 +144,7 @@
<entry>
<title>हिन्दी</title>
<id>hi-IN/opds.xml</id>
- <updated>2015-03-03T16:19:09</updated>
+ <updated>2015-03-06T05:43:33</updated>
<dc:language>hi-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="hi-IN/opds.xml"/>
@@ -152,7 +152,7 @@
<entry>
<title>Magyar</title>
<id>hu-HU/opds.xml</id>
- <updated>2015-03-03T16:19:10</updated>
+ <updated>2015-03-06T05:43:34</updated>
<dc:language>hu-HU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="hu-HU/opds.xml"/>
@@ -160,7 +160,7 @@
<entry>
<title>Interlingua (International Auxiliary Language Association)</title>
<id>ia/opds.xml</id>
- <updated>2015-03-03T16:19:11</updated>
+ <updated>2015-03-06T05:43:34</updated>
<dc:language>ia</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ia/opds.xml"/>
@@ -168,7 +168,7 @@
<entry>
<title>Indonesia</title>
<id>id-ID/opds.xml</id>
- <updated>2015-03-03T16:19:12</updated>
+ <updated>2015-03-06T05:43:35</updated>
<dc:language>id-ID</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="id-ID/opds.xml"/>
@@ -176,7 +176,7 @@
<entry>
<title>Italiano</title>
<id>it-IT/opds.xml</id>
- <updated>2015-03-03T16:19:13</updated>
+ <updated>2015-03-06T05:43:38</updated>
<dc:language>it-IT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="it-IT/opds.xml"/>
@@ -184,7 +184,7 @@
<entry>
<title>日本語</title>
<id>ja-JP/opds.xml</id>
- <updated>2015-03-03T16:19:15</updated>
+ <updated>2015-03-06T05:43:40</updated>
<dc:language>ja-JP</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ja-JP/opds.xml"/>
@@ -192,7 +192,7 @@
<entry>
<title>ಕನ್ನಡ</title>
<id>kn-IN/opds.xml</id>
- <updated>2015-03-03T16:19:16</updated>
+ <updated>2015-03-06T05:43:40</updated>
<dc:language>kn-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="kn-IN/opds.xml"/>
@@ -200,7 +200,7 @@
<entry>
<title>한국어</title>
<id>ko-KR/opds.xml</id>
- <updated>2015-03-03T16:19:17</updated>
+ <updated>2015-03-06T05:43:41</updated>
<dc:language>ko-KR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ko-KR/opds.xml"/>
@@ -208,7 +208,7 @@
<entry>
<title>Lithuanian</title>
<id>lt-LT/opds.xml</id>
- <updated>2015-03-03T16:19:19</updated>
+ <updated>2015-03-06T05:43:42</updated>
<dc:language>lt-LT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="lt-LT/opds.xml"/>
@@ -216,7 +216,7 @@
<entry>
<title>മലയാളം</title>
<id>ml-IN/opds.xml</id>
- <updated>2015-03-03T16:19:20</updated>
+ <updated>2015-03-06T05:43:42</updated>
<dc:language>ml-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ml-IN/opds.xml"/>
@@ -224,7 +224,7 @@
<entry>
<title>मराठी</title>
<id>mr-IN/opds.xml</id>
- <updated>2015-03-03T16:19:21</updated>
+ <updated>2015-03-06T05:43:43</updated>
<dc:language>mr-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="mr-IN/opds.xml"/>
@@ -232,7 +232,7 @@
<entry>
<title>Norsk (bokmål)</title>
<id>nb-NO/opds.xml</id>
- <updated>2015-03-03T16:19:22</updated>
+ <updated>2015-03-06T05:43:44</updated>
<dc:language>nb-NO</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nb-NO/opds.xml"/>
@@ -240,7 +240,7 @@
<entry>
<title>Nederlands</title>
<id>nl-NL/opds.xml</id>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</updated>
<dc:language>nl-NL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="nl-NL/opds.xml"/>
@@ -248,7 +248,7 @@
<entry>
<title>ଓଡ଼ିଆ</title>
<id>or-IN/opds.xml</id>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:47</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="or-IN/opds.xml"/>
@@ -256,7 +256,7 @@
<entry>
<title>ਪੰਜਾਬੀ</title>
<id>pa-IN/opds.xml</id>
- <updated>2015-03-03T16:19:26</updated>
+ <updated>2015-03-06T05:43:47</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pa-IN/opds.xml"/>
@@ -264,7 +264,7 @@
<entry>
<title>Polski</title>
<id>pl-PL/opds.xml</id>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:49</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pl-PL/opds.xml"/>
@@ -272,7 +272,7 @@
<entry>
<title>Português Brasileiro</title>
<id>pt-BR/opds.xml</id>
- <updated>2015-03-03T16:19:29</updated>
+ <updated>2015-03-06T05:43:50</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-BR/opds.xml"/>
@@ -280,7 +280,7 @@
<entry>
<title>Português</title>
<id>pt-PT/opds.xml</id>
- <updated>2015-03-03T16:19:30</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="pt-PT/opds.xml"/>
@@ -288,7 +288,7 @@
<entry>
<title>Romanian</title>
<id>ro/opds.xml</id>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ro/opds.xml"/>
@@ -296,7 +296,7 @@
<entry>
<title>Русский</title>
<id>ru-RU/opds.xml</id>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ru-RU/opds.xml"/>
@@ -304,7 +304,7 @@
<entry>
<title>Slovenščina</title>
<id>sk-SK/opds.xml</id>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sk-SK/opds.xml"/>
@@ -312,7 +312,7 @@
<entry>
<title>Srpski (latinica)</title>
<id>sr-Latn-RS/opds.xml</id>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sr-Latn-RS/opds.xml"/>
@@ -320,7 +320,7 @@
<entry>
<title>Српски</title>
<id>sr-RS/opds.xml</id>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sr-RS/opds.xml"/>
@@ -328,7 +328,7 @@
<entry>
<title>Svenska</title>
<id>sv-SE/opds.xml</id>
- <updated>2015-03-03T16:19:37</updated>
+ <updated>2015-03-06T05:43:56</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="sv-SE/opds.xml"/>
@@ -336,7 +336,7 @@
<entry>
<title>தமிழ்</title>
<id>ta-IN/opds.xml</id>
- <updated>2015-03-03T16:19:38</updated>
+ <updated>2015-03-06T05:43:57</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="ta-IN/opds.xml"/>
@@ -344,7 +344,7 @@
<entry>
<title>తెలుగు</title>
<id>te-IN/opds.xml</id>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="te-IN/opds.xml"/>
@@ -352,7 +352,7 @@
<entry>
<title>Українська</title>
<id>uk-UA/opds.xml</id>
- <updated>2015-03-03T16:19:41</updated>
+ <updated>2015-03-06T05:43:59</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="uk-UA/opds.xml"/>
@@ -360,7 +360,7 @@
<entry>
<title>简体中文</title>
<id>zh-CN/opds.xml</id>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="zh-CN/opds.xml"/>
@@ -368,7 +368,7 @@
<entry>
<title>繁體中文</title>
<id>zh-TW/opds.xml</id>
- <updated>2015-03-03T16:19:43</updated>
+ <updated>2015-03-06T05:44:01</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-Community_Services_Infrastructure.xml b/public_html/or-IN/opds-Community_Services_Infrastructure.xml
index 2dd3776..50b7d32 100644
--- a/public_html/or-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/or-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora.xml b/public_html/or-IN/opds-Fedora.xml
index 86d6baf..bca242a 100644
--- a/public_html/or-IN/opds-Fedora.xml
+++ b/public_html/or-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>or-IN</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
index f7e407a..8af1ca6 100644
--- a/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</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 437249f..0020a79 100644
--- a/public_html/or-IN/opds-Fedora_Core.xml
+++ b/public_html/or-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Documentation.xml b/public_html/or-IN/opds-Fedora_Documentation.xml
index 963fb93..8b966fd 100644
--- a/public_html/or-IN/opds-Fedora_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</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 1cc9af3..b0d4951 100644
--- a/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/or-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds-Fedora_Security_Team.xml b/public_html/or-IN/opds-Fedora_Security_Team.xml
index 9e86e4d..e5b4807 100644
--- a/public_html/or-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/or-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/or-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/or-IN/opds.xml b/public_html/or-IN/opds.xml
index b92d680..4556af1 100644
--- a/public_html/or-IN/opds.xml
+++ b/public_html/or-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/or-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:46</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/or-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/or-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:24</updated>
+ <updated>2015-03-06T05:43:46</updated>
<dc:language>or-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/or-IN/toc.html b/public_html/or-IN/toc.html
index 5f87d39..9b854cc 100644
--- a/public_html/or-IN/toc.html
+++ b/public_html/or-IN/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/pa-IN/opds-Community_Services_Infrastructure.xml b/public_html/pa-IN/opds-Community_Services_Infrastructure.xml
index 0c2ddff..1a82a87 100644
--- a/public_html/pa-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pa-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora.xml b/public_html/pa-IN/opds-Fedora.xml
index c1ffa77..757b3e0 100644
--- a/public_html/pa-IN/opds-Fedora.xml
+++ b/public_html/pa-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:47</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>pa-IN</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
index b7f950a..742197b 100644
--- a/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:47</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 9382b0a..d4dd21b 100644
--- a/public_html/pa-IN/opds-Fedora_Core.xml
+++ b/public_html/pa-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Documentation.xml b/public_html/pa-IN/opds-Fedora_Documentation.xml
index da41d00..f874cf4 100644
--- a/public_html/pa-IN/opds-Fedora_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:47</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 ead157a..c41216c 100644
--- a/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pa-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds-Fedora_Security_Team.xml b/public_html/pa-IN/opds-Fedora_Security_Team.xml
index 7b41c88..0205b07 100644
--- a/public_html/pa-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/pa-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pa-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:47</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pa-IN/opds.xml b/public_html/pa-IN/opds.xml
index c7ed319..2e246dc 100644
--- a/public_html/pa-IN/opds.xml
+++ b/public_html/pa-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pa-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:26</updated>
+ <updated>2015-03-06T05:43:47</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/pa-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:47</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:47</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:47</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:47</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:47</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:47</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/pa-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:25</updated>
+ <updated>2015-03-06T05:43:47</updated>
<dc:language>pa-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pa-IN/toc.html b/public_html/pa-IN/toc.html
index 8c06002..aa80ac2 100644
--- a/public_html/pa-IN/toc.html
+++ b/public_html/pa-IN/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/pl-PL/opds-Community_Services_Infrastructure.xml b/public_html/pl-PL/opds-Community_Services_Infrastructure.xml
index 23d44c6..c9fd689 100644
--- a/public_html/pl-PL/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pl-PL/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:26</updated>
+ <updated>2015-03-06T05:43:48</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora.xml b/public_html/pl-PL/opds-Fedora.xml
index f1be49b..2f129e2 100644
--- a/public_html/pl-PL/opds-Fedora.xml
+++ b/public_html/pl-PL/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:48</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>pl-PL</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml b/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
index 6493b46..8ab1857 100644
--- a/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Contributor_Documentation.xml</id>
<title>Dokumentacja dla współtwórców Fedory</title>
<subtitle>Dokumentacja dla współtwórców Fedory</subtitle>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:49</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 6e4505e..4a134cb 100644
--- a/public_html/pl-PL/opds-Fedora_Core.xml
+++ b/public_html/pl-PL/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Documentation.xml b/public_html/pl-PL/opds-Fedora_Documentation.xml
index e0a835d..aa0ec1d 100644
--- a/public_html/pl-PL/opds-Fedora_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:49</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 b1cad9c..d83ec69 100644
--- a/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pl-PL/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds-Fedora_Security_Team.xml b/public_html/pl-PL/opds-Fedora_Security_Team.xml
index e3284f0..71733ef 100644
--- a/public_html/pl-PL/opds-Fedora_Security_Team.xml
+++ b/public_html/pl-PL/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pl-PL/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pl-PL/opds.xml b/public_html/pl-PL/opds.xml
index 6c2f577..f67c597 100644
--- a/public_html/pl-PL/opds.xml
+++ b/public_html/pl-PL/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pl-PL/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:49</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/pl-PL/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:26</updated>
+ <updated>2015-03-06T05:43:48</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:48</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Dokumentacja dla współtwórców Fedory</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:49</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:49</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:49</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:49</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/pl-PL/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:49</updated>
<dc:language>pl-PL</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pl-PL/toc.html b/public_html/pl-PL/toc.html
index 76390a7..f40433b 100644
--- a/public_html/pl-PL/toc.html
+++ b/public_html/pl-PL/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -1527,7 +1527,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1545,7 +1545,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>
@@ -1905,7 +1905,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/pt-BR/opds-Community_Services_Infrastructure.xml b/public_html/pt-BR/opds-Community_Services_Infrastructure.xml
index 8afb068..d9e5e77 100644
--- a/public_html/pt-BR/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pt-BR/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:49</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora.xml b/public_html/pt-BR/opds-Fedora.xml
index f4c4eee..47b7a3c 100644
--- a/public_html/pt-BR/opds-Fedora.xml
+++ b/public_html/pt-BR/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:28</updated>
+ <updated>2015-03-06T05:43:50</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>pt-BR</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml b/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
index e8d6b9a..4e70d79 100644
--- a/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:28</updated>
+ <updated>2015-03-06T05:43:50</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 3767f1c..ada48d7 100644
--- a/public_html/pt-BR/opds-Fedora_Core.xml
+++ b/public_html/pt-BR/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:28</updated>
+ <updated>2015-03-06T05:43:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Documentation.xml b/public_html/pt-BR/opds-Fedora_Documentation.xml
index bfd4415..539c56f 100644
--- a/public_html/pt-BR/opds-Fedora_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:28</updated>
+ <updated>2015-03-06T05:43:50</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 deedf51..77c367b 100644
--- a/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pt-BR/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:28</updated>
+ <updated>2015-03-06T05:43:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds-Fedora_Security_Team.xml b/public_html/pt-BR/opds-Fedora_Security_Team.xml
index 7329402..1179b60 100644
--- a/public_html/pt-BR/opds-Fedora_Security_Team.xml
+++ b/public_html/pt-BR/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-BR/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:28</updated>
+ <updated>2015-03-06T05:43:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-BR/opds.xml b/public_html/pt-BR/opds.xml
index 7e3ecaa..59849b7 100644
--- a/public_html/pt-BR/opds.xml
+++ b/public_html/pt-BR/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pt-BR/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:29</updated>
+ <updated>2015-03-06T05:43:50</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/pt-BR/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:27</updated>
+ <updated>2015-03-06T05:43:49</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:28</updated>
+ <updated>2015-03-06T05:43:50</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:28</updated>
+ <updated>2015-03-06T05:43:50</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:28</updated>
+ <updated>2015-03-06T05:43:50</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:28</updated>
+ <updated>2015-03-06T05:43:50</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:28</updated>
+ <updated>2015-03-06T05:43:50</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/pt-BR/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:28</updated>
+ <updated>2015-03-06T05:43:50</updated>
<dc:language>pt-BR</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pt-BR/toc.html b/public_html/pt-BR/toc.html
index 2b23327..49be98a 100644
--- a/public_html/pt-BR/toc.html
+++ b/public_html/pt-BR/toc.html
@@ -402,7 +402,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1455,7 +1455,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1482,7 +1482,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>
@@ -1842,7 +1842,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/pt-PT/opds-Community_Services_Infrastructure.xml b/public_html/pt-PT/opds-Community_Services_Infrastructure.xml
index a7e639e..43343ab 100644
--- a/public_html/pt-PT/opds-Community_Services_Infrastructure.xml
+++ b/public_html/pt-PT/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:29</updated>
+ <updated>2015-03-06T05:43:50</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora.xml b/public_html/pt-PT/opds-Fedora.xml
index 99c10da..006e38d 100644
--- a/public_html/pt-PT/opds-Fedora.xml
+++ b/public_html/pt-PT/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:29</updated>
+ <updated>2015-03-06T05:43:50</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>pt-PT</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml b/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
index 46d20e6..2753d0e 100644
--- a/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:30</updated>
+ <updated>2015-03-06T05:43:51</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 a389734..64ef3dc 100644
--- a/public_html/pt-PT/opds-Fedora_Core.xml
+++ b/public_html/pt-PT/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:30</updated>
+ <updated>2015-03-06T05:43:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Documentation.xml b/public_html/pt-PT/opds-Fedora_Documentation.xml
index 78e5c80..3aa8abd 100644
--- a/public_html/pt-PT/opds-Fedora_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:30</updated>
+ <updated>2015-03-06T05:43:51</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 1dca503..452e64a 100644
--- a/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/pt-PT/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:30</updated>
+ <updated>2015-03-06T05:43:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds-Fedora_Security_Team.xml b/public_html/pt-PT/opds-Fedora_Security_Team.xml
index f5f4cc3..cd19d4c 100644
--- a/public_html/pt-PT/opds-Fedora_Security_Team.xml
+++ b/public_html/pt-PT/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/pt-PT/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:30</updated>
+ <updated>2015-03-06T05:43:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/pt-PT/opds.xml b/public_html/pt-PT/opds.xml
index 39e1ad9..80f395e 100644
--- a/public_html/pt-PT/opds.xml
+++ b/public_html/pt-PT/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/pt-PT/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:30</updated>
+ <updated>2015-03-06T05:43:51</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/pt-PT/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:29</updated>
+ <updated>2015-03-06T05:43:50</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:29</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:30</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:30</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:30</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:30</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/pt-PT/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:30</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>pt-PT</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/pt-PT/toc.html b/public_html/pt-PT/toc.html
index fbc0f68..7f47877 100644
--- a/public_html/pt-PT/toc.html
+++ b/public_html/pt-PT/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -708,7 +708,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -911,7 +911,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">
@@ -1455,7 +1455,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1482,7 +1482,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>
@@ -1832,7 +1832,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ro/opds-Community_Services_Infrastructure.xml b/public_html/ro/opds-Community_Services_Infrastructure.xml
index 4f4d536..aa9a221 100644
--- a/public_html/ro/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ro/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:30</updated>
+ <updated>2015-03-06T05:43:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora.xml b/public_html/ro/opds-Fedora.xml
index 7d8b30a..fdc6923 100644
--- a/public_html/ro/opds-Fedora.xml
+++ b/public_html/ro/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>ro</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/ro/opds-Fedora_Contributor_Documentation.xml b/public_html/ro/opds-Fedora_Contributor_Documentation.xml
index 6183c6d..d0da5aa 100644
--- a/public_html/ro/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ro/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora_Core.xml b/public_html/ro/opds-Fedora_Core.xml
index 8e389ed..260fa29 100644
--- a/public_html/ro/opds-Fedora_Core.xml
+++ b/public_html/ro/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora_Documentation.xml b/public_html/ro/opds-Fedora_Documentation.xml
index 9f81781..afd19dd 100644
--- a/public_html/ro/opds-Fedora_Documentation.xml
+++ b/public_html/ro/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora_Draft_Documentation.xml b/public_html/ro/opds-Fedora_Draft_Documentation.xml
index c5afaa5..5fac106 100644
--- a/public_html/ro/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ro/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora_Draft_Documentation.xml</id>
<title>Schiță Documentație Fedora</title>
<subtitle>Schiță Documentație Fedora</subtitle>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds-Fedora_Security_Team.xml b/public_html/ro/opds-Fedora_Security_Team.xml
index 12240d4..e6994a0 100644
--- a/public_html/ro/opds-Fedora_Security_Team.xml
+++ b/public_html/ro/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ro/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ro/opds.xml b/public_html/ro/opds.xml
index 14bfa23..3bbfcd8 100644
--- a/public_html/ro/opds.xml
+++ b/public_html/ro/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ro/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ro/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:30</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ro/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ro/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ro/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ro/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Schiță Documentație Fedora</title>
<id>http://docs.fedoraproject.org/ro/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ro/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>ro</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ro/toc.html b/public_html/ro/toc.html
index af0827a..5782a75 100644
--- a/public_html/ro/toc.html
+++ b/public_html/ro/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ru-RU/opds-Community_Services_Infrastructure.xml b/public_html/ru-RU/opds-Community_Services_Infrastructure.xml
index 613b6c1..f85d68a 100644
--- a/public_html/ru-RU/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ru-RU/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora.xml b/public_html/ru-RU/opds-Fedora.xml
index 3680e6c..007fa01 100644
--- a/public_html/ru-RU/opds-Fedora.xml
+++ b/public_html/ru-RU/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:32</updated>
+ <updated>2015-03-06T05:43:52</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>ru-RU</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml b/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
index a0758e0..5278fc0 100644
--- a/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Contributor_Documentation.xml</id>
<title>Документация участника Fedora</title>
<subtitle>Документация участника Fedora</subtitle>
- <updated>2015-03-03T16:19:32</updated>
+ <updated>2015-03-06T05:43:52</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 4fdf9ca..766fdd2 100644
--- a/public_html/ru-RU/opds-Fedora_Core.xml
+++ b/public_html/ru-RU/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:32</updated>
+ <updated>2015-03-06T05:43:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Documentation.xml b/public_html/ru-RU/opds-Fedora_Documentation.xml
index 9545151..e66a43c 100644
--- a/public_html/ru-RU/opds-Fedora_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:32</updated>
+ <updated>2015-03-06T05:43:52</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 6908d20..cc069a0 100644
--- a/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ru-RU/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:32</updated>
+ <updated>2015-03-06T05:43:52</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds-Fedora_Security_Team.xml b/public_html/ru-RU/opds-Fedora_Security_Team.xml
index 3e94c06..76eaf84 100644
--- a/public_html/ru-RU/opds-Fedora_Security_Team.xml
+++ b/public_html/ru-RU/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ru-RU/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:32</updated>
+ <updated>2015-03-06T05:43:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ru-RU/opds.xml b/public_html/ru-RU/opds.xml
index 99220ad..f89c29f 100644
--- a/public_html/ru-RU/opds.xml
+++ b/public_html/ru-RU/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ru-RU/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ru-RU/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:31</updated>
+ <updated>2015-03-06T05:43:51</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:32</updated>
+ <updated>2015-03-06T05:43:52</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Документация участника Fedora</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:32</updated>
+ <updated>2015-03-06T05:43:52</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:32</updated>
+ <updated>2015-03-06T05:43:52</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:32</updated>
+ <updated>2015-03-06T05:43:52</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:32</updated>
+ <updated>2015-03-06T05:43:53</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ru-RU/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:32</updated>
+ <updated>2015-03-06T05:43:53</updated>
<dc:language>ru-RU</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ru-RU/toc.html b/public_html/ru-RU/toc.html
index 00d56c2..6b6ceca 100644
--- a/public_html/ru-RU/toc.html
+++ b/public_html/ru-RU/toc.html
@@ -328,7 +328,7 @@
<a class="type" href="./Fedora/18/epub/Fedora_Live_Images/Fedora-18-Fedora_Live_Images-ru-RU.epub" >epub</a>
<a class="type" href="./Fedora/18/html/Fedora_Live_Images/index.html" onclick="window.top.location='./Fedora/18/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="./Fedora/18/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='./Fedora/18/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/18/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-ru-RU.pdf" onclick="window.top.location='./Fedora/18/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-ru-RU.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/18/pdf/Fedora_Live_Images/Fedora-18-Fedora_Live_Images-ru-RU.pdf" onclick="window.top.location='./Fedora/18/pdf/Fedora_Live_Images/Fedora-18-Fedora_Live_Images-ru-RU.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.Release_Notes' class="book collapsed">
@@ -402,7 +402,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -472,7 +472,7 @@
<a class="type" href="./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-ru-RU.epub" >epub</a>
<a class="type" href="./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-ru-RU.pdf" onclick="window.top.location='./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-ru-RU.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/17/pdf/Fedora_Live_Images/Fedora-18-Fedora_Live_Images-ru-RU.pdf" onclick="window.top.location='./Fedora/17/pdf/Fedora_Live_Images/Fedora-18-Fedora_Live_Images-ru-RU.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Resource_Management_Guide' class="book collapsed">
@@ -528,7 +528,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/sk-SK/opds-Community_Services_Infrastructure.xml b/public_html/sk-SK/opds-Community_Services_Infrastructure.xml
index bd7fed7..c408a10 100644
--- a/public_html/sk-SK/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sk-SK/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora.xml b/public_html/sk-SK/opds-Fedora.xml
index 4ff4b14..6ed6004 100644
--- a/public_html/sk-SK/opds-Fedora.xml
+++ b/public_html/sk-SK/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>sk-SK</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml b/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
index f8c512f..1a55b3c 100644
--- a/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</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 427bcad..723b250 100644
--- a/public_html/sk-SK/opds-Fedora_Core.xml
+++ b/public_html/sk-SK/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Documentation.xml b/public_html/sk-SK/opds-Fedora_Documentation.xml
index 035c7dc..619c4f5 100644
--- a/public_html/sk-SK/opds-Fedora_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</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 38e68c9..54e6645 100644
--- a/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sk-SK/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds-Fedora_Security_Team.xml b/public_html/sk-SK/opds-Fedora_Security_Team.xml
index d41486b..a0670b1 100644
--- a/public_html/sk-SK/opds-Fedora_Security_Team.xml
+++ b/public_html/sk-SK/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sk-SK/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sk-SK/opds.xml b/public_html/sk-SK/opds.xml
index bc3a22f..5f100d7 100644
--- a/public_html/sk-SK/opds.xml
+++ b/public_html/sk-SK/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sk-SK/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/sk-SK/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/sk-SK/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:33</updated>
+ <updated>2015-03-06T05:43:53</updated>
<dc:language>sk-SK</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sk-SK/toc.html b/public_html/sk-SK/toc.html
index 020b5f4..b5a7cb4 100644
--- a/public_html/sk-SK/toc.html
+++ b/public_html/sk-SK/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml b/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml
index db65ab5..7c6c206 100644
--- a/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sr-Latn-RS/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:53</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora.xml b/public_html/sr-Latn-RS/opds-Fedora.xml
index 9bb3a7e..4349f15 100644
--- a/public_html/sr-Latn-RS/opds-Fedora.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>sr-Latn-RS</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
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 c856714..863383b 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</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 3c128cb..9add364 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Core.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Documentation.xml b/public_html/sr-Latn-RS/opds-Fedora_Documentation.xml
index 9131f8a..0d1d327 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</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 008d0b5..6a427d0 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml b/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml
index 8c46e8c..5732b01 100644
--- a/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml
+++ b/public_html/sr-Latn-RS/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</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 b82ca74..2c87c54 100644
--- a/public_html/sr-Latn-RS/opds.xml
+++ b/public_html/sr-Latn-RS/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sr-Latn-RS/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:53</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/sr-Latn-RS/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</updated>
<dc:language>sr-Latn-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sr-Latn-RS/toc.html b/public_html/sr-Latn-RS/toc.html
index 58eaeb8..b9780f5 100644
--- a/public_html/sr-Latn-RS/toc.html
+++ b/public_html/sr-Latn-RS/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/sr-RS/opds-Community_Services_Infrastructure.xml b/public_html/sr-RS/opds-Community_Services_Infrastructure.xml
index 6a4582b..afe17f6 100644
--- a/public_html/sr-RS/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sr-RS/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora.xml b/public_html/sr-RS/opds-Fedora.xml
index 67c64ee..6e92895 100644
--- a/public_html/sr-RS/opds-Fedora.xml
+++ b/public_html/sr-RS/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>sr-RS</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml b/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
index fae9a6a..c3048f9 100644
--- a/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</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 df98942..5ec7686 100644
--- a/public_html/sr-RS/opds-Fedora_Core.xml
+++ b/public_html/sr-RS/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Documentation.xml b/public_html/sr-RS/opds-Fedora_Documentation.xml
index e336b66..e54618a 100644
--- a/public_html/sr-RS/opds-Fedora_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</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 2575268..0bec882 100644
--- a/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sr-RS/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds-Fedora_Security_Team.xml b/public_html/sr-RS/opds-Fedora_Security_Team.xml
index ec9ba05..f216cbe 100644
--- a/public_html/sr-RS/opds-Fedora_Security_Team.xml
+++ b/public_html/sr-RS/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sr-RS/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sr-RS/opds.xml b/public_html/sr-RS/opds.xml
index 9b3e13b..76a31aa 100644
--- a/public_html/sr-RS/opds.xml
+++ b/public_html/sr-RS/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sr-RS/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/sr-RS/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:34</updated>
+ <updated>2015-03-06T05:43:54</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/sr-RS/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</updated>
<dc:language>sr-RS</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sr-RS/toc.html b/public_html/sr-RS/toc.html
index 330f133..cfe2d1a 100644
--- a/public_html/sr-RS/toc.html
+++ b/public_html/sr-RS/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1455,7 +1455,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1482,7 +1482,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>
@@ -1842,7 +1842,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/sv-SE/opds-Community_Services_Infrastructure.xml b/public_html/sv-SE/opds-Community_Services_Infrastructure.xml
index 04f6f62..c71da35 100644
--- a/public_html/sv-SE/opds-Community_Services_Infrastructure.xml
+++ b/public_html/sv-SE/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora.xml b/public_html/sv-SE/opds-Fedora.xml
index a8fc29e..14ca06c 100644
--- a/public_html/sv-SE/opds-Fedora.xml
+++ b/public_html/sv-SE/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:36</updated>
+ <updated>2015-03-06T05:43:56</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>sv-SE</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml b/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
index 17d8e39..8ee5e0b 100644
--- a/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:36</updated>
+ <updated>2015-03-06T05:43:56</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 060684b..c2ebab5 100644
--- a/public_html/sv-SE/opds-Fedora_Core.xml
+++ b/public_html/sv-SE/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:36</updated>
+ <updated>2015-03-06T05:43:56</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Documentation.xml b/public_html/sv-SE/opds-Fedora_Documentation.xml
index bb9a5f3..54217d2 100644
--- a/public_html/sv-SE/opds-Fedora_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:36</updated>
+ <updated>2015-03-06T05:43:56</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 9c6f376..1e605c3 100644
--- a/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/sv-SE/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:36</updated>
+ <updated>2015-03-06T05:43:56</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds-Fedora_Security_Team.xml b/public_html/sv-SE/opds-Fedora_Security_Team.xml
index 5275742..8c19e9a 100644
--- a/public_html/sv-SE/opds-Fedora_Security_Team.xml
+++ b/public_html/sv-SE/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/sv-SE/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:36</updated>
+ <updated>2015-03-06T05:43:56</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/sv-SE/opds.xml b/public_html/sv-SE/opds.xml
index 785962a..00ab5e8 100644
--- a/public_html/sv-SE/opds.xml
+++ b/public_html/sv-SE/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/sv-SE/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:37</updated>
+ <updated>2015-03-06T05:43:56</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/sv-SE/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:35</updated>
+ <updated>2015-03-06T05:43:55</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:36</updated>
+ <updated>2015-03-06T05:43:56</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:36</updated>
+ <updated>2015-03-06T05:43:56</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:36</updated>
+ <updated>2015-03-06T05:43:56</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:36</updated>
+ <updated>2015-03-06T05:43:56</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:36</updated>
+ <updated>2015-03-06T05:43:56</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/sv-SE/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:37</updated>
+ <updated>2015-03-06T05:43:56</updated>
<dc:language>sv-SE</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/sv-SE/toc.html b/public_html/sv-SE/toc.html
index 8e2dc05..b2133ad 100644
--- a/public_html/sv-SE/toc.html
+++ b/public_html/sv-SE/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -1491,7 +1491,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1518,7 +1518,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>
@@ -1878,7 +1878,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/ta-IN/opds-Community_Services_Infrastructure.xml b/public_html/ta-IN/opds-Community_Services_Infrastructure.xml
index 0f7d6c1..239133c 100644
--- a/public_html/ta-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/ta-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:37</updated>
+ <updated>2015-03-06T05:43:56</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora.xml b/public_html/ta-IN/opds-Fedora.xml
index 136e992..32d91f4 100644
--- a/public_html/ta-IN/opds-Fedora.xml
+++ b/public_html/ta-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:37</updated>
+ <updated>2015-03-06T05:43:56</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>ta-IN</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
index f6a0bb5..601f882 100644
--- a/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:38</updated>
+ <updated>2015-03-06T05:43:56</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 8cf1ce8..325e7a0 100644
--- a/public_html/ta-IN/opds-Fedora_Core.xml
+++ b/public_html/ta-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:38</updated>
+ <updated>2015-03-06T05:43:56</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Documentation.xml b/public_html/ta-IN/opds-Fedora_Documentation.xml
index 328c615..8d2a80c 100644
--- a/public_html/ta-IN/opds-Fedora_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:38</updated>
+ <updated>2015-03-06T05:43:56</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 1ecf62d..5ce77be 100644
--- a/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/ta-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:38</updated>
+ <updated>2015-03-06T05:43:57</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds-Fedora_Security_Team.xml b/public_html/ta-IN/opds-Fedora_Security_Team.xml
index 11c779e..5065c84 100644
--- a/public_html/ta-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/ta-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/ta-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:38</updated>
+ <updated>2015-03-06T05:43:57</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/ta-IN/opds.xml b/public_html/ta-IN/opds.xml
index 0bacf21..d8853bf 100644
--- a/public_html/ta-IN/opds.xml
+++ b/public_html/ta-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/ta-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:38</updated>
+ <updated>2015-03-06T05:43:57</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/ta-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:37</updated>
+ <updated>2015-03-06T05:43:56</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:38</updated>
+ <updated>2015-03-06T05:43:56</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:38</updated>
+ <updated>2015-03-06T05:43:56</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:38</updated>
+ <updated>2015-03-06T05:43:56</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:38</updated>
+ <updated>2015-03-06T05:43:57</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:38</updated>
+ <updated>2015-03-06T05:43:57</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/ta-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:38</updated>
+ <updated>2015-03-06T05:43:57</updated>
<dc:language>ta-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/ta-IN/toc.html b/public_html/ta-IN/toc.html
index f2d54e5..cb11114 100644
--- a/public_html/ta-IN/toc.html
+++ b/public_html/ta-IN/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/te-IN/opds-Community_Services_Infrastructure.xml b/public_html/te-IN/opds-Community_Services_Infrastructure.xml
index 44ee2b5..45db69a 100644
--- a/public_html/te-IN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/te-IN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:38</updated>
+ <updated>2015-03-06T05:43:57</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora.xml b/public_html/te-IN/opds-Fedora.xml
index 5d8bbc4..9af1186 100644
--- a/public_html/te-IN/opds-Fedora.xml
+++ b/public_html/te-IN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>te-IN</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml b/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
index cce17a2..302d2c3 100644
--- a/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</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 2dbd073..6bb3502 100644
--- a/public_html/te-IN/opds-Fedora_Core.xml
+++ b/public_html/te-IN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Documentation.xml b/public_html/te-IN/opds-Fedora_Documentation.xml
index 5b4ca46..151180b 100644
--- a/public_html/te-IN/opds-Fedora_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</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 c6c3277..8e9dbf3 100644
--- a/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/te-IN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds-Fedora_Security_Team.xml b/public_html/te-IN/opds-Fedora_Security_Team.xml
index 0ba872b..9719b22 100644
--- a/public_html/te-IN/opds-Fedora_Security_Team.xml
+++ b/public_html/te-IN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/te-IN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/te-IN/opds.xml b/public_html/te-IN/opds.xml
index 83fefaa..c296921 100644
--- a/public_html/te-IN/opds.xml
+++ b/public_html/te-IN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/te-IN/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/te-IN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:38</updated>
+ <updated>2015-03-06T05:43:57</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/te-IN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</updated>
<dc:language>te-IN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/te-IN/toc.html b/public_html/te-IN/toc.html
index 1f8a1cc..8088f27 100644
--- a/public_html/te-IN/toc.html
+++ b/public_html/te-IN/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -475,7 +475,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -519,7 +519,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Release_Notes' class="book collapsed" onclick="toggle(event, 'Fedora.17.Release_Notes.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/toc.html b/public_html/toc.html
index 8030482..30bcab8 100644
--- a/public_html/toc.html
+++ b/public_html/toc.html
@@ -452,7 +452,7 @@
<a class="type" href="./ca-ES/Fedora/15/html-single/Burning_ISO_images_to_disc/index.html">html-single</a>
- <a class="type" href="./ca-ES/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-ca-ES.pdf">pdf</a>
+ <a class="type" href="./ca-ES/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-ca-ES.pdf">pdf</a>
</div>
</div>
@@ -660,7 +660,7 @@
<a class="type" href="./cs-CZ/Fedora/15/html-single/Burning_ISO_images_to_disc/index.html">html-single</a>
- <a class="type" href="./cs-CZ/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-cs-CZ.pdf">pdf</a>
+ <a class="type" href="./cs-CZ/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-cs-CZ.pdf">pdf</a>
</div>
</div>
@@ -902,7 +902,7 @@
<a class="type" href="./de-DE/Fedora/18/html-single/Burning_ISO_images_to_disc/index.html">html-single</a>
- <a class="type" href="./de-DE/Fedora/18/pdf/Burning_ISO_images_to_disc/Fedora-17-Burning_ISO_images_to_disc-de-DE.pdf">pdf</a>
+ <a class="type" href="./de-DE/Fedora/18/pdf/Burning_ISO_images_to_disc/Fedora-18-Burning_ISO_images_to_disc-de-DE.pdf">pdf</a>
</div>
</div>
@@ -2041,7 +2041,7 @@
<a class="type" href="./en-US/Fedora/18/html-single/Security_Guide/index.html">html-single</a>
- <a class="type" href="./en-US/Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf">pdf</a>
+ <a class="type" href="./en-US/Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf">pdf</a>
</div>
</div>
@@ -2164,7 +2164,7 @@
<a class="type" href="./en-US/Fedora/17/html-single/Fedora_Live_Images/index.html">html-single</a>
- <a class="type" href="./en-US/Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf">pdf</a>
+ <a class="type" href="./en-US/Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf">pdf</a>
</div>
</div>
@@ -2237,7 +2237,7 @@
<a class="type" href="./en-US/Fedora/17/html-single/Power_Management_Guide/index.html">html-single</a>
- <a class="type" href="./en-US/Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf">pdf</a>
+ <a class="type" href="./en-US/Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf">pdf</a>
</div>
</div>
@@ -2511,7 +2511,7 @@
<a class="type" href="./en-US/Fedora/15/html-single/Burning_ISO_images_to_disc/index.html">html-single</a>
- <a class="type" href="./en-US/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf">pdf</a>
+ <a class="type" href="./en-US/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf">pdf</a>
</div>
</div>
@@ -3631,7 +3631,7 @@
<a class="type" href="./en-US/Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html">html-single</a>
- <a class="type" href="./en-US/Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf">pdf</a>
+ <a class="type" href="./en-US/Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf">pdf</a>
</div>
</div>
@@ -3676,7 +3676,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>
@@ -4158,7 +4158,7 @@
<a class="type" href="./en-US/Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html">html-single</a>
- <a class="type" href="./en-US/Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf">pdf</a>
+ <a class="type" href="./en-US/Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf">pdf</a>
</div>
</div>
@@ -4638,7 +4638,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>
@@ -6548,7 +6548,7 @@
<a class="type" href="./he-IL/Fedora/15/html-single/Burning_ISO_images_to_disc/index.html">html-single</a>
- <a class="type" href="./he-IL/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-he-IL.pdf">pdf</a>
+ <a class="type" href="./he-IL/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-he-IL.pdf">pdf</a>
</div>
</div>
@@ -8285,7 +8285,7 @@
<a class="type" href="./ja-JP/Fedora/15/html-single/Burning_ISO_images_to_disc/index.html">html-single</a>
- <a class="type" href="./ja-JP/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-ja-JP.pdf">pdf</a>
+ <a class="type" href="./ja-JP/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-ja-JP.pdf">pdf</a>
</div>
</div>
@@ -9432,7 +9432,7 @@
<a class="type" href="./nl-NL/Fedora/18/html-single/Virtualization_Getting_Started_Guide/index.html">html-single</a>
- <a class="type" href="./nl-NL/Fedora/18/pdf/Virtualization_Getting_Started_Guide/Fedora-18-Virtualization_Getting_Started_Guide-nl-NL.pdf">pdf</a>
+ <a class="type" href="./nl-NL/Fedora/18/pdf/Virtualization_Getting_Started_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Getting_Started_Guide-nl-NL.pdf">pdf</a>
</div>
</div>
@@ -9546,7 +9546,7 @@
<a class="type" href="./nl-NL/Fedora/15/html-single/Burning_ISO_images_to_disc/index.html">html-single</a>
- <a class="type" href="./nl-NL/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-nl-NL.pdf">pdf</a>
+ <a class="type" href="./nl-NL/Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-nl-NL.pdf">pdf</a>
</div>
</div>
@@ -9711,7 +9711,7 @@
<a class="type" href="./nl-NL/Fedora/13/html-single/Accessibility_Guide/index.html">html-single</a>
- <a class="type" href="./nl-NL/Fedora/13/pdf/Accessibility_Guide/fedora-13-Accessibility_Guide-nl-NL.pdf">pdf</a>
+ <a class="type" href="./nl-NL/Fedora/13/pdf/Accessibility_Guide/Fedora-13-Accessibility_Guide-nl-NL.pdf">pdf</a>
</div>
</div>
@@ -10137,7 +10137,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>
@@ -11629,7 +11629,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>
@@ -12188,7 +12188,7 @@
<a class="type" href="./ru-RU/Fedora/18/html-single/Fedora_Live_Images/index.html">html-single</a>
- <a class="type" href="./ru-RU/Fedora/18/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-ru-RU.pdf">pdf</a>
+ <a class="type" href="./ru-RU/Fedora/18/pdf/Fedora_Live_Images/Fedora-18-Fedora_Live_Images-ru-RU.pdf">pdf</a>
</div>
</div>
@@ -12251,7 +12251,7 @@
<a class="type" href="./ru-RU/Fedora/17/html-single/Fedora_Live_Images/index.html">html-single</a>
- <a class="type" href="./ru-RU/Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-ru-RU.pdf">pdf</a>
+ <a class="type" href="./ru-RU/Fedora/17/pdf/Fedora_Live_Images/Fedora-18-Fedora_Live_Images-ru-RU.pdf">pdf</a>
</div>
</div>
@@ -14877,7 +14877,7 @@
<a class="type" href="./zh-CN/Fedora/18/html-single/Release_Notes/index.html">html-single</a>
- <a class="type" href="./zh-CN/Fedora/18/pdf/Release_Notes/Fedora-17-Release_Notes-zh-CN.pdf">pdf</a>
+ <a class="type" href="./zh-CN/Fedora/18/pdf/Release_Notes/Fedora-18-Release_Notes-zh-CN.pdf">pdf</a>
</div>
</div>
@@ -15051,7 +15051,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-Community_Services_Infrastructure.xml b/public_html/uk-UA/opds-Community_Services_Infrastructure.xml
index a88062d..129d135 100644
--- a/public_html/uk-UA/opds-Community_Services_Infrastructure.xml
+++ b/public_html/uk-UA/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora.xml b/public_html/uk-UA/opds-Fedora.xml
index 7cd9749..01c27cf 100644
--- a/public_html/uk-UA/opds-Fedora.xml
+++ b/public_html/uk-UA/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:40</updated>
+ <updated>2015-03-06T05:43:58</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>uk-UA</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml b/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
index 9f13181..ea10a8e 100644
--- a/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Contributor_Documentation.xml</id>
<title>Документація для учасника розробки Fedora</title>
<subtitle>Документація для учасника розробки Fedora</subtitle>
- <updated>2015-03-03T16:19:40</updated>
+ <updated>2015-03-06T05:43:59</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 e9898f1..5df8f16 100644
--- a/public_html/uk-UA/opds-Fedora_Core.xml
+++ b/public_html/uk-UA/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:40</updated>
+ <updated>2015-03-06T05:43:59</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Documentation.xml b/public_html/uk-UA/opds-Fedora_Documentation.xml
index c10df45..5bf83a5 100644
--- a/public_html/uk-UA/opds-Fedora_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:40</updated>
+ <updated>2015-03-06T05:43:59</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 3827646..43d0879 100644
--- a/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/uk-UA/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Draft_Documentation.xml</id>
<title>Чернетки документації з Fedora</title>
<subtitle>Чернетки документації з Fedora</subtitle>
- <updated>2015-03-03T16:19:40</updated>
+ <updated>2015-03-06T05:43:59</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds-Fedora_Security_Team.xml b/public_html/uk-UA/opds-Fedora_Security_Team.xml
index 972c742..6213973 100644
--- a/public_html/uk-UA/opds-Fedora_Security_Team.xml
+++ b/public_html/uk-UA/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/uk-UA/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:41</updated>
+ <updated>2015-03-06T05:43:59</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/uk-UA/opds.xml b/public_html/uk-UA/opds.xml
index 83a156f..bd0c6fa 100644
--- a/public_html/uk-UA/opds.xml
+++ b/public_html/uk-UA/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/uk-UA/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:41</updated>
+ <updated>2015-03-06T05:43:59</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/uk-UA/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:39</updated>
+ <updated>2015-03-06T05:43:57</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:40</updated>
+ <updated>2015-03-06T05:43:58</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Документація для учасника розробки Fedora</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:40</updated>
+ <updated>2015-03-06T05:43:59</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:40</updated>
+ <updated>2015-03-06T05:43:59</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:40</updated>
+ <updated>2015-03-06T05:43:59</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Чернетки документації з Fedora</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:41</updated>
+ <updated>2015-03-06T05:43:59</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/uk-UA/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:41</updated>
+ <updated>2015-03-06T05:43:59</updated>
<dc:language>uk-UA</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/uk-UA/toc.html b/public_html/uk-UA/toc.html
index 7ccecd6..f2a2381 100644
--- a/public_html/uk-UA/toc.html
+++ b/public_html/uk-UA/toc.html
@@ -402,7 +402,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -528,7 +528,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Resource_Management_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.Resource_Management_Guide.types');">
@@ -1455,7 +1455,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1845,7 +1845,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/zh-CN/opds-Community_Services_Infrastructure.xml b/public_html/zh-CN/opds-Community_Services_Infrastructure.xml
index 6b098e0..6e8c113 100644
--- a/public_html/zh-CN/opds-Community_Services_Infrastructure.xml
+++ b/public_html/zh-CN/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:41</updated>
+ <updated>2015-03-06T05:43:59</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora.xml b/public_html/zh-CN/opds-Fedora.xml
index f9f2b80..1ebac6d 100644
--- a/public_html/zh-CN/opds-Fedora.xml
+++ b/public_html/zh-CN/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>zh-CN</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml b/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
index c311a63..9ab6fdc 100644
--- a/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</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 894c2ae..6cc27f9 100644
--- a/public_html/zh-CN/opds-Fedora_Core.xml
+++ b/public_html/zh-CN/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Documentation.xml b/public_html/zh-CN/opds-Fedora_Documentation.xml
index 2136bb6..92b017c 100644
--- a/public_html/zh-CN/opds-Fedora_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</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 ca157df..a95737f 100644
--- a/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/zh-CN/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds-Fedora_Security_Team.xml b/public_html/zh-CN/opds-Fedora_Security_Team.xml
index 7522317..dba3467 100644
--- a/public_html/zh-CN/opds-Fedora_Security_Team.xml
+++ b/public_html/zh-CN/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-CN/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-CN/opds.xml b/public_html/zh-CN/opds.xml
index afc56ce..94aae5c 100644
--- a/public_html/zh-CN/opds.xml
+++ b/public_html/zh-CN/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/zh-CN/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/zh-CN/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:41</updated>
+ <updated>2015-03-06T05:43:59</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/zh-CN/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</updated>
<dc:language>zh-CN</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/zh-CN/toc.html b/public_html/zh-CN/toc.html
index 4d6269b..b1740dc 100644
--- a/public_html/zh-CN/toc.html
+++ b/public_html/zh-CN/toc.html
@@ -319,7 +319,7 @@
<a class="type" href="./Fedora/18/epub/Release_Notes/Fedora-18-Release_Notes-zh-CN.epub" >epub</a>
<a class="type" href="./Fedora/18/html/Release_Notes/index.html" onclick="window.top.location='./Fedora/18/html/Release_Notes/index.html';return false;">html</a>
<a class="type" href="./Fedora/18/html-single/Release_Notes/index.html" onclick="window.top.location='./Fedora/18/html-single/Release_Notes/index.html';return false;">html-single</a>
- <a class="type" href="./Fedora/18/pdf/Release_Notes/Fedora-17-Release_Notes-zh-CN.pdf" onclick="window.top.location='./Fedora/18/pdf/Release_Notes/Fedora-17-Release_Notes-zh-CN.pdf';return false;">pdf</a>
+ <a class="type" href="./Fedora/18/pdf/Release_Notes/Fedora-18-Release_Notes-zh-CN.pdf" onclick="window.top.location='./Fedora/18/pdf/Release_Notes/Fedora-18-Release_Notes-zh-CN.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18' class="version collapsed untranslated" onclick="toggle(event, 'Fedora.18.untrans_books');">
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -528,7 +528,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Resource_Management_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.Resource_Management_Guide.types');">
@@ -909,7 +909,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">
@@ -1525,7 +1525,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1543,7 +1543,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>
@@ -1903,7 +1903,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
diff --git a/public_html/zh-TW/opds-Community_Services_Infrastructure.xml b/public_html/zh-TW/opds-Community_Services_Infrastructure.xml
index 8d26311..285f3ed 100644
--- a/public_html/zh-TW/opds-Community_Services_Infrastructure.xml
+++ b/public_html/zh-TW/opds-Community_Services_Infrastructure.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Community_Services_Infrastructure.xml</id>
<title>Community Services Infrastructure</title>
<subtitle>Community Services Infrastructure</subtitle>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora.xml b/public_html/zh-TW/opds-Fedora.xml
index 328a384..4875dd6 100644
--- a/public_html/zh-TW/opds-Fedora.xml
+++ b/public_html/zh-TW/opds-Fedora.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora.xml</id>
<title>Fedora</title>
<subtitle>Fedora</subtitle>
- <updated>2015-03-03T16:19:43</updated>
+ <updated>2015-03-06T05:44:00</updated>
<!--author>
<name></name>
<uri></uri>
@@ -91,7 +91,7 @@
<name></name>
<uri></uri>
</author-->
- <updated>2014-12-10</updated>
+ <updated>2015-03-06</updated>
<dc:language>zh-TW</dc:language>
<category label="" scheme="http://lexcycle.com/stanza/header" term="free"/>
<!--dc:issued></dc:issued-->
diff --git a/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml b/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
index 783e886..e4aba2f 100644
--- a/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Contributor_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Contributor_Documentation.xml</id>
<title>Fedora Contributor Documentation</title>
<subtitle>Fedora Contributor Documentation</subtitle>
- <updated>2015-03-03T16:19:43</updated>
+ <updated>2015-03-06T05:44:00</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 4e24d75..9b9d0cd 100644
--- a/public_html/zh-TW/opds-Fedora_Core.xml
+++ b/public_html/zh-TW/opds-Fedora_Core.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Core.xml</id>
<title>Fedora Core</title>
<subtitle>Fedora Core</subtitle>
- <updated>2015-03-03T16:19:43</updated>
+ <updated>2015-03-06T05:44:00</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Documentation.xml b/public_html/zh-TW/opds-Fedora_Documentation.xml
index 5a53f79..8ba8230 100644
--- a/public_html/zh-TW/opds-Fedora_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Documentation.xml</id>
<title>Fedora Documentation</title>
<subtitle>Fedora Documentation</subtitle>
- <updated>2015-03-03T16:19:43</updated>
+ <updated>2015-03-06T05:44:00</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 e500a6e..14e84ee 100644
--- a/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
+++ b/public_html/zh-TW/opds-Fedora_Draft_Documentation.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Draft_Documentation.xml</id>
<title>Fedora Draft Documentation</title>
<subtitle>Fedora Draft Documentation</subtitle>
- <updated>2015-03-03T16:19:43</updated>
+ <updated>2015-03-06T05:44:00</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds-Fedora_Security_Team.xml b/public_html/zh-TW/opds-Fedora_Security_Team.xml
index be34f91..d267ca3 100644
--- a/public_html/zh-TW/opds-Fedora_Security_Team.xml
+++ b/public_html/zh-TW/opds-Fedora_Security_Team.xml
@@ -6,7 +6,7 @@
<id>http://docs.fedoraproject.org/zh-TW/opds-Fedora_Security_Team.xml</id>
<title>Fedora Security Team</title>
<subtitle>Fedora Security Team</subtitle>
- <updated>2015-03-03T16:19:43</updated>
+ <updated>2015-03-06T05:44:00</updated>
<!--author>
<name></name>
<uri></uri>
diff --git a/public_html/zh-TW/opds.xml b/public_html/zh-TW/opds.xml
index 892c21a..1442b03 100644
--- a/public_html/zh-TW/opds.xml
+++ b/public_html/zh-TW/opds.xml
@@ -6,7 +6,7 @@
<link rel="http://opds-spec.org/crawlable" type="application/atom+xml" href="http://bookserver.archive.org/catalog/crawlable" title="Crawlable feed"/>
<id>http://docs.fedoraproject.org/zh-TW/opds.xml</id>
<title>Product List</title>
- <updated>2015-03-03T16:19:43</updated>
+ <updated>2015-03-06T05:44:01</updated>
<!--author>
<name></name>
<uri></uri>
@@ -15,7 +15,7 @@
<entry>
<title>Community Services Infrastructure</title>
<id>http://docs.fedoraproject.org/zh-TW/Community_Services_Infrastructure/opds-Community_Services_Infrastructure.xml</id>
- <updated>2015-03-03T16:19:42</updated>
+ <updated>2015-03-06T05:44:00</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Community_Services_Infrastructure.xml"/>
@@ -23,7 +23,7 @@
<entry>
<title>Fedora</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora/opds-Fedora.xml</id>
- <updated>2015-03-03T16:19:43</updated>
+ <updated>2015-03-06T05:44:00</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora.xml"/>
@@ -31,7 +31,7 @@
<entry>
<title>Fedora Contributor Documentation</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Contributor_Documentation/opds-Fedora_Contributor_Documentation.xml</id>
- <updated>2015-03-03T16:19:43</updated>
+ <updated>2015-03-06T05:44:00</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Contributor_Documentation.xml"/>
@@ -39,7 +39,7 @@
<entry>
<title>Fedora Core</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Core/opds-Fedora_Core.xml</id>
- <updated>2015-03-03T16:19:43</updated>
+ <updated>2015-03-06T05:44:00</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Core.xml"/>
@@ -47,7 +47,7 @@
<entry>
<title>Fedora Documentation</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Documentation/opds-Fedora_Documentation.xml</id>
- <updated>2015-03-03T16:19:43</updated>
+ <updated>2015-03-06T05:44:00</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Documentation.xml"/>
@@ -55,7 +55,7 @@
<entry>
<title>Fedora Draft Documentation</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Draft_Documentation/opds-Fedora_Draft_Documentation.xml</id>
- <updated>2015-03-03T16:19:43</updated>
+ <updated>2015-03-06T05:44:00</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Draft_Documentation.xml"/>
@@ -63,7 +63,7 @@
<entry>
<title>Fedora Security Team</title>
<id>http://docs.fedoraproject.org/zh-TW/Fedora_Security_Team/opds-Fedora_Security_Team.xml</id>
- <updated>2015-03-03T16:19:43</updated>
+ <updated>2015-03-06T05:44:01</updated>
<dc:language>zh-TW</dc:language>
<content type="text"></content>
<link type="application/atom+xml" href="opds-Fedora_Security_Team.xml"/>
diff --git a/public_html/zh-TW/toc.html b/public_html/zh-TW/toc.html
index 3946885..81cf561 100644
--- a/public_html/zh-TW/toc.html
+++ b/public_html/zh-TW/toc.html
@@ -393,7 +393,7 @@
<a class="type" href="../en-US/./Fedora/18/epub/Security_Guide/Fedora-18-Security_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/18/html/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html/Security_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/18/html-single/Security_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/18/html-single/Security_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora-18-Security_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/18/pdf/Security_Guide/Fedora_Documentation-18-Security_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.18.System_Administrators_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.18.System_Administrators_Guide.types');">
@@ -484,7 +484,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Fedora_Live_Images/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Fedora_Live_Images/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-16-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Fedora_Live_Images/Fedora-17-Fedora_Live_Images-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.FreeIPA_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.FreeIPA_Guide.types');">
@@ -528,7 +528,7 @@
<a class="type" href="../en-US/./Fedora/17/epub/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/17/html/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html/Power_Management_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html" onclick="window.top.location='../en-US/./Fedora/17/html-single/Power_Management_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora--Power_Management_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/17/pdf/Power_Management_Guide/Fedora-17-Power_Management_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.17.Resource_Management_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.17.Resource_Management_Guide.types');">
@@ -700,7 +700,7 @@
<a class="type" href="../en-US/./Fedora/15/epub/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html/Burning_ISO_images_to_disc/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html" onclick="window.top.location='../en-US/./Fedora/15/html-single/Burning_ISO_images_to_disc/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15.0-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf" onclick="window.top.location='../en-US/./Fedora/15/pdf/Burning_ISO_images_to_disc/Fedora-15-Burning_ISO_images_to_disc-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora.15.Deployment_Guide' class="book collapsed" onclick="toggle(event, 'Fedora.15.Deployment_Guide.types');">
@@ -1446,7 +1446,7 @@
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/epub/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html/Fedora_Elections_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/html-single/Fedora_Elections_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation--Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Contributor_Documentation/1/pdf/Fedora_Elections_Guide/Fedora_Contributor_Documentation-1-Fedora_Elections_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
<div id='Fedora_Contributor_Documentation.1.Software_Collections_Guide' class="book collapsed" onclick="toggle(event, 'Fedora_Contributor_Documentation.1.Software_Collections_Guide.types');">
@@ -1473,7 +1473,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>
@@ -1833,7 +1833,7 @@
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/epub/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.epub" >epub</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html</a>
<a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/html-single/Virtualization_Deployment_and_Administration_Guide/index.html';return false;">html-single</a>
- <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora-19-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
+ <a class="type" href="../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf" onclick="window.top.location='../en-US/./Fedora_Draft_Documentation/0.1/pdf/Virtualization_Deployment_and_Administration_Guide/Fedora_Draft_Documentation-0.1-Virtualization_Deployment_and_Administration_Guide-en-US.pdf';return false;">pdf</a>
</div>
</div>
</div>
More information about the docs-commits
mailing list