Changeset b1532549 for general/sysutils/logrotate.xml

Timestamp:

03/19/2020 10:00:16 AM (4 years ago)

Author:

Pierre Labastie <pieere@…>

Branches:

10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal

Children:

e68b588

Parents:

09f0998

Message:

Format sysutils

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@22859 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:

• general/sysutils/logrotate.xml (modified) (5 diffs)

general/sysutils/logrotate.xml

@@ -31 +31 @@
 
     <para>
-      The <application>logrotate</application> package allows automatic rotation,
-      compression, removal, and mailing of log files.
+      The <application>logrotate</application> package allows automatic
+      rotation, compression, removal, and mailing of log files.
     </para>
 
@@ -119 +119 @@
 
   <sect2 role="configuration">
-     <title>Configuring Logrotate</title>
-
-     <para><application>Logrotate</application> needs a configuration file,
-     which must be passed as an argument to the command when executed.  Create
-     the file as the <systemitem class="username">root</systemitem> user:</para>
+    <title>Configuring Logrotate</title>
+
+    <para>
+      <application>Logrotate</application> needs a configuration file,
+      which must be passed as an argument to the command when executed.  Create
+      the file as the <systemitem class="username">root</systemitem> user:
+    </para>
 
 <screen role="root"><userinput>cat &gt; /etc/logrotate.conf &lt;&lt; EOF
@@ -170 +172 @@
 chmod -v 0644 /etc/logrotate.conf</userinput></screen>
 
-    <para>Now create the <filename class='directory'>/etc/logrotate.d</filename>
-    directory as the  <systemitem class="username">root</systemitem> user:</para>
+    <para>
+      Now create the <filename class='directory'>/etc/logrotate.d</filename>
+      directory as the  <systemitem class="username">root</systemitem> user:
+    </para>
 
 <screen role="root"><userinput>mkdir -p /etc/logrotate.d</userinput></screen>
 
-  <para>At this point additional log rotation commands can be entered, typically
-  in the <filename class='directory'>/etc/logrotate.d</filename> directory.
-  For example:</para>
+    <para>
+      At this point additional log rotation commands can be entered, typically
+      in the <filename class='directory'>/etc/logrotate.d</filename> directory.
+      For example:
+    </para>
 
 <screen role="nodump"><userinput>cat &gt; /etc/logrotate.d/sys.log &lt;&lt; EOF
@@ -193 +199 @@
 chmod -v 0644 /etc/logrotate.d/sys.log</userinput></screen>
 
-  <para>You can designate multiple files in one entry:</para>
+    <para>
+      You can designate multiple files in one entry:
+    </para>
 
 <screen role="nodump"><userinput>cat &gt; /etc/logrotate.d/example.log &lt;&lt; EOF
@@ -208 +216 @@
 chmod -v 0644 /etc/logrotate.d/example.log</userinput></screen>
 
-  <para>You can use in the same line the list of files: file1 file2 file3.
-  See the logrotate man page or
-  <ulink url='http://www.techrepublic.com/article/manage-linux-log-files-with-logrotate/'/>
-  for more examples.</para>
-
-  <para>The command <command>logrotate /etc/logrotate.conf</command> can be
-  run manually, however, the command should be run daily.
-  Other useful commands are <command>logrotate -d /etc/logrotate.conf</command>
-  for debugging purposes and <command>logrotate -f /etc/logrotate.conf</command>
-  forcing the logrotate commands to be run immediately. Combining the previous
-  options <option>-df</option>, you can debug the effect of the force command.
-  When debugging, the command is only simulated, not really run, thus, eventual
-  non-existing errors appear, when some intermediate files are expected,
-  because they are not actually created.</para>
+    <para>
+      You can use in the same line the list of files: file1 file2 file3.
+      See the logrotate man page or <ulink
+      url='http://www.techrepublic.com/article/manage-linux-log-files-with-logrotate/'/>
+      for more examples.
+    </para>
+
+    <para>
+      The command <command>logrotate /etc/logrotate.conf</command> can be
+      run manually, however, the command should be run daily.
+      Other useful commands are <command>logrotate -d
+      /etc/logrotate.conf</command> for debugging purposes and
+      <command>logrotate -f /etc/logrotate.conf</command> forcing the
+      logrotate commands to be run immediately. Combining the previous options
+      <option>-df</option>, you can debug the effect of the force command.
+      When debugging, the command is only simulated, not really run, thus,
+      eventual non-existing errors appear, when some intermediate files are
+      expected, because they are not actually created.
+    </para>
 
     <para>