Managing and Analyzing System Log Files
System log files record almost everything that happens on your
system, from kernel events to service failures and application
errors. Knowing where these logs are located, how to query them with
journalctl and standard tools and how to read
their priority levels lets you diagnose problems quickly instead of
guessing. This article also covers logrotate,
which automates log rotation and compression to keep logs from
filling up your disk.
Prerequisites:
Access to a terminal with
sudoprivileges
1 Where to find system log files? #
SLES logs several types of messages, for example, from the kernel, SELinux or other services.
Kernel messages and messages of system services registered with systemd
are logged in the systemd journal (see
Section 4, “The systemd journal”). The journal also forwards
messages to rsyslog, which writes
most of them to plain-text files under the /var/log
directory. SELinux messages are logged
separately, in /var/log/audit/audit.log.
The following list provides an overview of all system log files found in
SLES after a default installation. Depending on your installation
scope, /var/log also contains log files from other
services and applications not listed here. Some files and directories
described below are “placeholders” and are only used when the
corresponding application is installed. Most log files are only visible for
the user with sudo access. Usually, you can view these files using an editor as
they are in plain text.
utmp, wtmp and
lastlog have been removed from SLES and
are no longer supported. If there are any applications that write into
these log files, remember that the log files are incomplete then.
wtmp has been replaced with wtmpdb,
lastlog with lastlog2.
audit/audit.logLogs from the audit framework, including SELinux access control decisions.
boot.logMessages logged during the current boot, mirroring what is also shown on the console while the system starts up.
boot.msgandboot.omsgcontain raw kernel ring buffer dumps from the current and previous boot. They show the same content asdmesg. Use them to find the exact kernel command line of a boot.chrony/Logs from the Network Time Protocol daemon (
chrony). This directory is empty by default. Files only appear here once you enable specific logging directives (for example,log measurements) in/etc/chrony.conf.cups/Access and error logs of the Common Unix Printing System (
cups).firewall,firewalldfirewallcatches kernel-level packet-filter messages.firewalldholds errors and warnings from thefirewallddaemon itself. Neither is the place to look for logged network traffic unless you have explicitly enabled that in your firewall rules.journal/The
systemdjournal's own storage location. See Section 4, “Thesystemdjournal”.krb5/Log files from the Kerberos network authentication system. Empty unless you have installed and configured Kerberos client or server tools.
localmessagesMessages logged to the
local0throughlocal7facilities, commonly used by third-party applications that do not have a dedicated log file of their own. This file only appears once something logs to one of these facilities.mail,mail.info,mail.warn,mail.errMail server logs, split by severity. Empty unless a mail transfer agent such as
postfixis installed.messagesThe default destination for kernel and system log messages, forwarded from the journal by
rsyslog. Together with/var/log/warn, this is the first place to look in case of problems.NetworkManagerNetworkManagerlog files.pbl.logLog of the
update-bootloadertool (also known aspbl), which configures the boot loader on SLES. Check this file after a kernel update or a manual boot loader change if the system does not boot as expected.pcp/Logs from Performance Co-Pilot, installed and enabled by default for system performance monitoring.
snapper.logLog of
snapper, the tool that manages Btrfs snapshots. Check this file if a scheduled snapshot did not run or a snapshot could not be deleted.warnAll system warnings and errors, filtered from
/var/log/messages.zypp/libzypplog files. Refer to these files for the package installation history.zypper.logLogs from the command-line installer
zypper.
2 Viewing and parsing /var/log files #
Plain-text logs in /var/log can be viewed,
searched and parsed with standard command-line tools.
For viewing log files, use the commands less or
more. Use head and
tail to view the beginning or end of a log file. To view
entries appended to a log file in real time, use tail
-f. For information about how to use these tools, see
their man pages.
>sudotail -f /var/log/messages
To search for strings or regular expressions in log files, use
grep. awk is useful for parsing and
rewriting log files. For example, to show only lines logged by the
sshd-session process:
>sudogrep sshd-session /var/log/messages
Rotated log files are compressed (see
Section 5.1, “Configuring logrotate”). SLES
compresses them with xz by default, so use
xzless, xzcat or
xzgrep instead of the less,
cat or grep commands above:
>sudoxzgrep sshd-session /var/log/messages-20260828.xz
3 Interpreting log entries #
Whether a message comes from a plain-text file or from the journal, it follows a predictable structure and carries a priority level. Knowing both helps you find what matters quickly.
3.1 Structure of a plain-text log line #
A line in a plain-text log file such as
/var/log/messages consists of a time stamp, the
host name, the name of the program that generated the message (usually
followed by its process ID in brackets) and the message text itself:
/var/log/messages #2026-09-07T09:21:30.439903+02:00 sles16 sshd-session[4731]: pam_unix(sshd:session): session opened for user tux(uid=1000) by tux(uid=0)
In this example, 2026-09-07T09:21:30.439903+02:00 is
the time stamp (in ISO 8601 format, including the time zone
offset), sles16 is the host name,
sshd-session is the program that logged the message,
4731 is its process ID and everything after the
colon is the message itself. Not every program includes a process ID.
Certain programs log under just their name.
3.2 Priority levels #
Every log message carries a priority level indicating its severity. The
same eight levels apply both to journal entries (visible in the
PRIORITY field and filterable with
journalctl -p) and to the selector lines in
rsyslog configuration files
(for example, *.err or
mail.warning), which decide into which file a message
is written. Raw kernel messages, such as those in
boot.msg or the output of dmesg,
show the same level as a bracketed number prefix, for example,
<6> for info.
| Level | Name | Meaning |
|---|---|---|
| 0 | emerg | The system is unusable. |
| 1 | alert | Action must be taken immediately. |
| 2 | crit | A critical condition. |
| 3 | err | A service or application failed to complete a requested operation. |
| 4 | warning | Something undesirable happened, but it is not a failure. |
| 5 | notice | A normal but significant condition. |
| 6 | info | Normal operational information. |
| 7 | debug | Information useful for developers only. |
When troubleshooting, start by looking for the lowest-numbered (most
severe) entries around the time the problem occurred. For example,
journalctl -p err -b shows the messages of the
current boot with the priority err or more severe
(crit, alert and
emerg).
4 The systemd journal #
systemd features its own logging system called
journal. The journal itself is a system service
managed by systemd—systemd-journald.service.
The systemd-journald service is enabled and started by
default. On SLES, it stores log data persistently in
/var/log/journal/, so entries survive a reboot, and
forwards a copy of every message to
rsyslog (see
Section 1, “Where to find system log files?”). To query the journal, use the
journalctl command (see
Section 4.1, “Using journalctl”).
4.1 Using journalctl #
Because the journal stores data in a binary format, you cannot
open it directly with tools such as cat or
less. Use the journalctl
command to query and display its content instead.
Running journalctl without any options displays all logged messages, usually starting from the oldest, and pipes the output through a pager (like less) for easy navigation.
The general syntax of the journalctl command is as follows:
>sudojournalctl [OPTIONS...] [MATCHES...]
To show all journal messages related to a specific executable, specify the full path to the executable:
>sudojournalctl /usr/lib/systemd/systemd
Listed below are the common useful options to enhance the default journalctl behavior:
- -f
Shows only the most recent journal messages, and prints new log entries as they are added to the journal.
- -e
Prints the messages and jumps to the end of the journal, so that the latest entries are visible within the pager.
- -r
Prints the messages of the journal in reverse order, so that the latest entries are listed first.
- -k
Shows only kernel messages from the current boot. This is equivalent to
-bwith the field match_TRANSPORT=kernel.- -u
Shows only messages for the specified
systemdunit. Besides messages with_SYSTEMD_UNIT=UNIT, the output includes whatsystemdlogs about the unit, such as start and stop messages and core dump reports.>sudojournalctl -u apache2
For a complete list of options refer to man page, man 1 journalctl.
5 Controlling log file growth with logrotate #
Log files under /var/log grow daily and can
quickly become large. logrotate is a tool that
helps you manage log files and their growth. It allows automatic
rotation, removal, compression and mailing of log files. Log files
can be handled periodically (daily, weekly or monthly) or when
exceeding a particular size.
logrotate is usually run daily by systemd, and thus
usually modifies log files only once a day. However, exceptions occur when
a log file is modified because of its size, if logrotate
is run multiple times a day or if --force is enabled.
View the /var/lib/misc/logrotate.status file to find
out when a particular file was last rotated.
logrotate can be configured to suit your needs. For
details, see Section 5.1, “Configuring logrotate”.
To test your configuration without rotating anything, run
logrotate in debug mode, pointing it at whichever
configuration file is in effect
(/etc/logrotate.conf if you have created it, or the
shipped default otherwise, see
Section 5.1, “Configuring logrotate”):
>sudologrotate -d /usr/etc/logrotate.conf
To rotate logs immediately, for example, right after changing a
configuration file, use --force with the same path:
>sudologrotate --force /usr/etc/logrotate.conf
logrotate only rotates the plain-text files under
/var/log. The journal binary storage in
/var/log/journal/ is unaffected by it and, unless
you have set a limit in a journald.conf.d
drop-in, is only capped by the built-in systemd default (a percentage
of the file system it resides on).
Check the current journal disk usage and trim it manually if needed with:
>sudojournalctl --disk-usage>sudojournalctl --vacuum-size=500M
--vacuum-time=TIME (for
example, --vacuum-time=2weeks) and
--vacuum-files=COUNT work
the same way, removing the oldest archived journal files until the given
age or file count is reached.
5.1 Configuring logrotate #
The main configuration file logrotate.conf
defines, for example, how often to rotate logs or which tool is used
for data compression. Each service can have its own logrotate
configuration in /etc/logrotate.d/.
SLES ships with weekly rotation, four kept backlogs and
compression enabled by default.
5.1.1 Adjusting logrotate.conf #
The default version of logrotate.conf resides in the
/usr/etc/ directory. If the default does not suit
your needs, copy the file to /etc/logrotate.conf and
change the configuration values there. Do not modify the
/usr/etc/ version as it may be overwritten with a
system update. You can replace the following values:
/usr/etc/logrotate.conf ## see "man logrotate" for details # rotate log files weekly weekly # keep 4 weeks worth of backlogs rotate 4 # create new (empty) log files after rotating old ones create # use date as a suffix of the rotated file dateext # uncomment this if you want your log files compressed compress # comment these to switch compression to use gzip or another # compression scheme compresscmd /usr/bin/xz uncompresscmd /usr/bin/xzdec # Additional location (directory or file) for rotation information # include <file_or_directory>
weeklyThe frequency of log rotation. You can use any of the values:
hourly,daily,weekly,monthlyoryearly.maxageYou can specify a number of days that logs are kept.
rotate 4The number determines the amount of log rotations to retain the rotated logs. When set to
rotate 0, the logs are deleted immediately. When set torotate -1, the logs are not removed until they reach the value ofmaxage.dateextIf the option is present in the configuration file, rotated log file names receive a suffix with a date in the format
logname-YYYYMMDD, for example,messages-20260828.xz. If not present, the default file name scheme islogname.1,logname.2. SLES enablesdateextby default.compressIf commented out, the logs are not compressed. Enabled by default on SLES.
compresscmdanduncompresscmdHere, you can change the default compression and decompression tools by setting corresponding absolute paths to the tools. SLES uses
/usr/bin/xzand/usr/bin/xzdecby default.include PATHYou can change the default location of the file with log rotation information. The default is
/var/lib/misc/logrotate.status.
5.1.2 Service-specific logrotate configuration #
Services and applications can have a specific logrotate configuration in
/etc/logrotate.d. Besides the options mentioned in
Section 5.1.1, “Adjusting logrotate.conf”, you
can also use the following configurations:
missingokThe log rotation does not report errors if any of the specified log files are missing.
notifemptyAn empty log file is not rotated.
delaycompressThe compression of rotated logs is postponed until the next log rotation.
sharedscriptsDenotes a section with scripts that should be executed only once regardless of the numbers of logs being rotated. If omitted, the scripts are executed for each log file being rotated.
sizeDefines the size a log file can reach before the log rotation is initiated. This option may ignore the time scheduling. The value can be in megabytes (M), kilobytes (K) or bytes (B).
minsizeLogs are rotated according to the specified time schedule if their size exceeds this value. The value can be in megabytes (M), kilobytes (K) or bytes (B).
maxsizeSpecifies the maximum log file size. Reaching this limit triggers rotation even when the time interval has not been reached. The value can be in megabytes (M), kilobytes (K) or bytes (B).
6 For more information #
For more information about configuring
systemd-journaldand filtering the journal by boot, time or field, see Mastering System Logs: From systemd-journald to journalctl.For more information about the SELinux messages in
/var/log/audit/audit.log, see Understanding SELinux logs.
7 Legal Notice #
Copyright© 2006– 2026 SUSE LLC and contributors. All rights reserved.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”.
For SUSE trademarks, see https://www.suse.com/company/legal/. All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its affiliates. Asterisks (*) denote third-party trademarks.
All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors, nor the translators shall be held liable for possible errors or the consequences thereof.
GNU Free Documentation License
Copyright (C) 2000, 2001, 2002 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
0. PREAMBLE #
The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or non-commercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.
This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.
We have designed this License to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.
1. APPLICABILITY AND DEFINITIONS #
This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.
The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.
A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.
2. VERBATIM COPYING #
You may copy and distribute the Document in any medium, either commercially or non-commercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display copies.
3. COPYING IN QUANTITY #
If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.
4. MODIFICATIONS #
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:
Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.
List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.
State on the Title page the name of the publisher of the Modified Version, as the publisher.
Preserve all the copyright notices of the Document.
Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.
Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.
Include an unaltered copy of this License.
Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.
Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.
Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.
Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.
Preserve any Warranty Disclaimers.
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.
You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.
5. COMBINING DOCUMENTS #
You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".
6. COLLECTIONS OF DOCUMENTS #
You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.
7. AGGREGATION WITH INDEPENDENT WORKS #
A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.
8. TRANSLATION #
Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.
If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.
9. TERMINATION #
You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
10. FUTURE REVISIONS OF THIS LICENSE #
The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See https://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.
ADDENDUM: How to use this License for your documents #
Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the “with...Texts.” line with this:
with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.
If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.