/mandos/trunk

To get this branch, use:
bzr branch http://bzr.recompile.se/loggerhead/mandos/trunk

« back to all changes in this revision

Viewing changes to plugins.d/splashy.xml

  • Committer: Teddy Hogeborn
  • Date: 2018-02-18 01:14:23 UTC
  • Revision ID: teddy@recompile.se-20180218011423-twxv4clb7wvm9fof
Remove dead code.

* plugins.d/mandos-client.d (main/clean_dir_at): Remove dead code.

Show diffs side-by-side

added added

removed removed

Lines of Context:
plugins.d/splashy.xml
2
2
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3
3
        "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4
4
<!ENTITY COMMANDNAME "splashy">
5
 
<!ENTITY TIMESTAMP "2019-02-10">
 
5
<!ENTITY TIMESTAMP "2018-02-08">
6
6
<!ENTITY % common SYSTEM "../common.ent">
7
7
%common;
8
8
]>
42
42
      <year>2016</year>
43
43
      <year>2017</year>
44
44
      <year>2018</year>
45
 
      <year>2019</year>
46
45
      <holder>Teddy Hogeborn</holder>
47
46
      <holder>Björn Påhlsson</holder>
48
47
    </copyright>
135
134
        <para>
136
135
          These variables will normally be inherited from
137
136
          <citerefentry><refentrytitle>plugin-runner</refentrytitle>
138
 
          <manvolnum>8mandos</manvolnum></citerefentry>, which might
139
 
          have in turn inherited them from its calling process.
 
137
          <manvolnum>8mandos</manvolnum></citerefentry>, which will
 
138
          normally have inherited them from
 
139
          <filename>/scripts/local-top/cryptroot</filename> in the
 
140
          initial <acronym>RAM</acronym> disk environment, which will
 
141
          have set them from parsing kernel arguments and
 
142
          <filename>/conf/conf.d/cryptroot</filename> (also in the
 
143
          initial RAM disk environment), which in turn will have been
 
144
          created when the initial RAM disk image was created by
 
145
          <filename
 
146
          >/usr/share/initramfs-tools/hooks/cryptroot</filename>, by
 
147
          extracting the information of the root file system from
 
148
          <filename >/etc/crypttab</filename>.
140
149
        </para>
141
150
        <para>
142
151
          This behavior is meant to exactly mirror the behavior of
266
275
    <para>
267
276
      <citerefentry><refentrytitle>intro</refentrytitle>
268
277
      <manvolnum>8mandos</manvolnum></citerefentry>,
 
278
      <citerefentry><refentrytitle>crypttab</refentrytitle>
 
279
      <manvolnum>5</manvolnum></citerefentry>,
269
280
      <citerefentry><refentrytitle>plugin-runner</refentrytitle>
270
281
      <manvolnum>8mandos</manvolnum></citerefentry>,
271
282
      <citerefentry><refentrytitle>proc</refentrytitle>