Ignore:
Timestamp:
05/27/2016 07:55:47 PM (8 years ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
1aff37f
Parents:
cbd8bf0f
Message:

Update to dbus-1.10.8.
Update to e2fsprogs-1.43.
Update to gdbm-1.12.
Update to iproute2-4.6.0.
Update to make-4.2.
Update to systemd-230.

Add additional explanatory text for sytemctl and journalctl commands.
[chapter07/systemd-custom.xml]

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

File:
1 edited

Legend:

Unmodified
Added
Removed
  • chapter07/systemd-custom.xml

    rcbd8bf0f re787b1f  
    8787    <title>Overriding Default Services Behavior</title>
    8888
    89     <para>A systemd service contents can be overriden by creating a directory
     89    <para>The parameter of a unit can be overriden by creating a directory
    9090    and a configuration file in <filename
    9191    class="directory">/etc/systemd/system</filename>. For example:</para>
     
    110110
    111111    <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
     112    systems, systemd uses a unified format for different types of startup
    113113    files (or units). The command <command>systemctl</command> is used to
    114114    enable, disable, controll state, and obtain status of unit files. Here
     
    144144    <title>Working with the Systemd Journal</title>
    145145
    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>
     146    <para>Logging on a system booted with systemd is handled with
     147    systemd-journald (by default), rather than a typical unix syslog daemon.
     148    You can also add a normal syslog daemon and have both work side by
     149    side if desired. The systemd-journald program stores journal entries in a
     150    binary format rather than a plain text log file. To assist with
     151    parsing the file, the command <command>journalctl</command> is provided.
     152    Here are some examples of frequently used commands:</para>
    152153
    153154    <itemizedlist>
Note: See TracChangeset for help on using the changeset viewer.