Changeset 96733af


Ignore:
Timestamp:
07/20/2014 01:15:37 PM (10 years ago)
Author:
Krejzi <krejzi@…>
Branches:
7.6-blfs, 7.6-systemd, kde5-14269, kde5-14686, systemd-13485
Children:
932240d
Parents:
c32ea611
Message:

Cosmetic changes to last night's updates.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/branches/systemd@13501 af4574ff-66df-0310-9fd7-8a98e5e911e0

Files:
10 edited

Legend:

Unmodified
Added
Removed

  • general/sysutils/acpid-systemd.xml

    rc32ea611 r96733af  
    142142
    143143    <sect3  id="acpid-init">
    144       <title>Systemd Unit</title>
     144      <title>Systemd Units</title>
    145145
    146146      <para>
    147         To automatically start <command>acpid</command> when the system is
    148         rebooted, install the systemd unit
    149         from the <xref linkend="bootscripts"/> package.
     147        To automatically start <command>acpid</command> daemon at boot,
     148        install the systemd unit from the <xref linkend="bootscripts"/>
     149        package by running the following command as the
     150        <systemitem class="username">root</systemitem> user:
    150151      </para>
    151152

  • general/sysutils/at-systemd.xml

    rc32ea611 r96733af  
    140140
    141141    <sect3  id="at-init">
    142       <title>Systemd Unit</title>
    143 
    144       <para>To start the <command>atd</command> daemon at boot,
    145       enable the previously installed systemd unit by running
    146       the following command as the
    147       <systemitem class="username">root</systemitem> user:</para>
     142      <title>Systemd Units</title>
     143
     144      <para>
     145        To start the <command>atd</command> daemon at boot,
     146        enable the previously installed systemd unit by
     147        running the following command as the
     148        <systemitem class="username">root</systemitem> user:
     149      </para>
    148150
    149151      <indexterm zone="at at-init">

  • general/sysutils/autofs-systemd.xml

    rc32ea611 r96733af  
    252252
    253253    <sect3  id="autofs-init">
    254       <title>Systemd Unit</title>
    255 
    256       <para>To start the <application>Autofs</application> at boot,
    257       enable the previously installed systemd unit by running
    258       the following command as the
    259       <systemitem class="username">root</systemitem> user:</para>
    260 
     254      <title>Systemd Units</title>
     255
     256      <para>
     257        To start the <application>Autofs</application> at boot,
     258        enable the previously installed systemd unit by
     259        running the following command as the
     260        <systemitem class="username">root</systemitem> user:
     261      </para>
    261262
    262263      <indexterm zone="autofs autofs-init">
    … …  
    268269      <note>
    269270        <para>
    270           You can also specify <envar>OPTIONS</envar> variable in
    271           <filename>/etc/sysconfig/autofs</filename> with any additional
     271          You can also specify <envar>OPTIONS</envar> variable in the
     272          <filename>/etc/sysconfig/autofs</filename> file with any additional
    272273          parameters that you might want to pass to the automount daemon.
    273274        </para>

  • general/sysutils/bluez-systemd.xml

    rc32ea611 r96733af  
    174174
    175175  </sect2>
    176 
    177176
    178177  <sect2 role="commands">
    … …  
    207206# See the rfcomm man page for options
    208207
    209 
    210208# End of rfcomm.conf</literal></screen>
    211209
    … …  
    226224
    227225    <sect3  id="bluez-init">
    228       <title>Boot Script</title>
     226      <title>Systemd Units</title>
    229227
    230228      <para>
    231         To automatically start the <command>bluetoothd</command> daemon when the
    232         system is rebooted, enable the previously installed systemd unit by
     229        To start the <command>bluetoothd</command> daemon at boot,
     230        enable the previously installed systemd unit by
    233231        running the following command as the
    234232        <systemitem class="username">root</systemitem> user:
    … …  
    243241      <note>
    244242        <para>
    245           The bluetooth daemon will only start when a bluetooth device has been detected
    246           on the system.
     243          <application>Systemd</application> will start the Bluetooth daemon
     244          only when a bluetooth device is detected on the system.
    247245        </para>
    248246      </note>

  • general/sysutils/fcron-systemd.xml

    rc32ea611 r96733af  
    222222
    223223    <sect3  id="fcron-init">
    224       <title>Systemd Unit</title>
    225 
    226       <para>To start the <command>fcron</command> daemon at boot,
    227       enable the previously installed systemd unit by running
    228       the following command as the
    229       <systemitem class="username">root</systemitem> user:</para>
     224      <title>Systemd Units</title>
     225
     226      <para>
     227        To start the <command>fcron</command> daemon at boot,
     228        enable the previously installed systemd unit by
     229        running the following command as the
     230        <systemitem class="username">root</systemitem> user:
     231      </para>
    230232
    231233      <indexterm zone="fcron fcron-init">

  • general/sysutils/upower-systemd.xml

    rc32ea611 r96733af  
    157157
    158158    <sect3  id="upower-init">
    159       <title>Systemd Unit</title>
    160 
    161       <para>To start the <command>upowerd</command> daemon at boot,
    162       enable the previously installed systemd unit by running
    163       the following command as the
    164       <systemitem class="username">root</systemitem> user:</para>
     159      <title>Systemd Units</title>
     160
     161      <para>
     162        To start the <command>upowerd</command> daemon at boot,
     163        enable the previously installed systemd unit by
     164        running the following command as the
     165        <systemitem class="username">root</systemitem> user:
     166      </para>
    165167
    166168      <indexterm zone="upower upower-init">

  • postlfs/security/cyrus-sasl-systemd.xml

    rc32ea611 r96733af  
    283283
    284284    <sect3 id="cyrus-sasl-init">
    285       <title>Systemd Unit</title>
    286 
    287       <para>
    288         If you need to run the <command>saslauthd</command> daemon at system
    289         startup, install the systemd unit included in the
    290         <xref linkend="bootscripts"/> package using the following command:
     285      <title>Systemd Units</title>
     286
     287      <para>
     288        To automatically start <command>saslauthd</command> daemon at boot,
     289        install the systemd unit from the <xref linkend="bootscripts"/>
     290        package by running the following command as the
     291        <systemitem class="username">root</systemitem> user:
    291292      </para>
    292293

  • postlfs/security/mitkrb-systemd.xml

    rc32ea611 r96733af  
    467467
    468468      <para>
    469         If you want to start <application>Kerberos</application> services
    470         at boot, install the systemd units included in the
    471         <xref linkend="bootscripts"/> package using the following command:
     469        To automatically start Kerberos services at boot,
     470        install the systemd unit from the <xref linkend="bootscripts"/>
     471        package by running the following command as the
     472        <systemitem class="username">root</systemitem> user:
    472473      </para>
    473474

  • postlfs/security/openssh-systemd.xml

    rc32ea611 r96733af  
    305305
    306306      <para>
    307         To start the SSH server at system boot, install the systemd
    308         units included in the <xref linkend="bootscripts"/> package.
     307        To automatically start <command>sshd</command> daemon at boot,
     308        install the systemd unit from the <xref linkend="bootscripts"/>
     309        package by running the following command as the
     310        <systemitem class="username">root</systemitem> user:
    309311      </para>
    310312

  • postlfs/security/stunnel-systemd.xml

    rc32ea611 r96733af  
    242242
    243243    <sect3  id="stunnel-init">
    244       <title>Systemd Unit</title>
    245 
    246       <para>To automatically start the <command>stunnel</command> daemon
    247       when the system is rebooted, enable the previously installed
    248       systemd unit by running the following command as the
    249       <systemitem class="username">root</systemitem> user:</para>
     244      <title>Systemd Units</title>
     245
     246      <para>
     247        To start the <command>stunnel</command> daemon at boot,
     248        enable the previously installed systemd unit by
     249        running the following command as the
     250        <systemitem class="username">root</systemitem> user:
     251      </para>
    250252
    251253      <indexterm zone="stunnel stunnel-init">
Note: See TracChangeset for help on using the changeset viewer.