Changeset 33d5aa3


Ignore:
Timestamp:
05/20/2016 12:26:32 AM (8 years ago)
Author:
DJ Lucas <dj@…>
Parents:
82d2dbe
Message:

Added additional explanatory text explaing use of systemctl and journalctl commands.

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/branches/systemd@11072 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:
4 edited

Legend:

Unmodified
Added
Removed

  • chapter01/changelog.xml

    r82d2dbe r33d5aa3  
    3737-->
    3838    <listitem>
     39      <para>2016-05-20</para>
     40      <itemizedlist>
     41        <listitem>
     42          <para>[dj] - Add additional explanatory text for sytemctl and
     43          journalctl commands.</para>
     44        </listitem>
     45     </itemizedlist>
     46    </listitem>
     47
     48    <listitem>
    3949      <para>2016-05-19</para>
    4050      <itemizedlist>

  • chapter07/network.xml

    r82d2dbe r33d5aa3  
    6464Address=192.168.0.2/24
    6565Gateway=192.168.0.1
    66 DNS=192.168.0.1</literal>
     66DNS=192.168.0.1
     67Domains=<replaceable>&lt;Your Domain Name&gt;</replaceable></literal>
    6768EOF</userinput></screen>
    6869
    6970      <para>Multiple DNS entries can be added if you have more than one DNS
    70       server.</para>
     71      server. Do not include DNS or Domains entries if you intend to use a
     72      static <filename>/etc/reslov.conf</filename> file.</para>
    7173
    7274    </sect3>
    … …  
    8385
    8486[Network]
    85 DHCP=ipv4</literal>
     87DHCP=ipv4
     88
     89[DHCP]
     90UseDomains=true</literal>
    8691EOF</userinput></screen>
    8792

  • chapter07/systemd-custom.xml

    r82d2dbe r33d5aa3  
    109109    <title>Debugging the Boot Sequence</title>
    110110
    111     <para>There are several commands that can be used to help debug the systemd
    112     boot process. Here are some examples:</para>
     111    <para>Rather than plain shell scripts used in SysVinit or BSD style init
     112    systems, systemd uses a unified format for different type of startup
     113    files (or units). The command <command>systemctl</command> is used to
     114    enable, disable, controll state, and obtain status of unit files. Here
     115    are some examples of frequently used commands:</para>
    113116
    114117    <itemizedlist>
    115        <listitem><para>systemctl list-units -t service [--all]</para></listitem>
    116        <listitem><para>systemctl list-units -t target  [--all]</para></listitem>
    117        <listitem><para>systemctl show -p Wants multi-user.target</para></listitem>
    118        <listitem><para>systemctl status sshd.service</para></listitem>
     118       <listitem>
     119         <para><command>systemctl list-units -t <replaceable>&lt;service&gt;</replaceable> [--all]</command>:
     120         lists loaded unit files of type service.</para>
     121       </listitem>
     122       <listitem>
     123         <para><command>systemctl list-units -t <replaceable>&lt;target&gt;</replaceable> [--all]</command>:
     124         lists loaded unit files of type target.</para>
     125       </listitem>
     126       <listitem>
     127         <para><command>systemctl show -p Wants <replaceable>&lt;multi-user.target&gt;</replaceable></command>:
     128         shows all units that depend on the multi-user target. Targets are
     129         special unit files that are anogalous to runlevels under
     130         SysVinit.</para>
     131       </listitem>
     132       <listitem>
     133         <para><command>systemctl status <replaceable>&lt;servicename.service&gt;</replaceable></command>:
     134         shows the status of the servicename service. The .service extension
     135         can be omitted if there are no other unit files with the same name,
     136         such as .socket files (which create a listening socket that provides
     137         similar functionality to inetd/xinetd).</para>
     138       </listitem>
    119139    </itemizedlist>
    120140
    121141  </sect2>
    122142
    123 <!--TBA
    124143  <sect2>
    125     <title>Working with journalctl</title>
     144    <title>Working with the Systemd Journal</title>
    126145
    127     <para>Logging on a system booted with systemd is handled by the systemd
    128     journal.</para>
     146    <para>Logging on a system booted with systemd is handled by
     147    systemd-journald (default), rather than a typical unix syslog daemon.
     148    systemd-journald write log entries to a binary file format, rather than
     149    a plain text log file. To assist with parsing the file, the command
     150    <command>journalctl</command> is provided. Here are some examples of
     151    frequently used commands:</para>
    129152
    130153    <itemizedlist>
    131        <listitem><para>journalctl -r </para></listitem>
    132        <listitem><para>journalctl -u <replaceable>UNIT</replaceable></para></listitem>
    133        <listitem><para>journalctl -b[=ID] -r</para></listitem>
    134        <listitem><para>journalctl -f</para></listitem>
     154       <listitem>
     155         <para><command>journalctl -r</command>: shows all contents of the
     156         journal in reverse chronological order.</para>
     157       </listitem>
     158       <listitem>
     159         <para><command>journalctl -u <replaceable>UNIT</replaceable></command>:
     160         shows the journal entries associated with the specified UNIT
     161         file.</para>
     162       </listitem>
     163       <listitem>
     164         <para><command>journalctl -b[=ID] -r</command>: shows the journal
     165         entries since last successfull boot (or for boot ID) in reverse
     166         chronological order.</para>
     167       </listitem>
     168       <listitem>
     169         <para><command>journalctl -f</command>: povides functionality similar
     170         to tail -f (follow).</para>
     171       </listitem>
    135172    </itemizedlist>
    136173
    137174  </sect2>
    138 -->
    139175</sect1>

  • general.ent

    r82d2dbe r33d5aa3  
    1 <!ENTITY version         "20160519-systemd">
     1<!ENTITY version         "20160520-systemd">
    22<!ENTITY short-version   "systemd">  <!-- Used in dbus chapter, change to x.y for release -->
    3 <!ENTITY releasedate     "May 19th, 2016">
     3<!ENTITY releasedate     "May 20th, 2016">
    44<!ENTITY copyrightdate   "1999-2016"><!-- jhalfs needs a literal dash, not &ndash; -->
    55<!ENTITY milestone       "7.10">
Note: See TracChangeset for help on using the changeset viewer.