/mandos/release

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

« back to all changes in this revision

Viewing changes to mandos-clients.conf.xml

Updated year in copyright notices.

Show diffs side-by-side

added added

removed removed

Lines of Context:
mandos-clients.conf.xml
3
3
        "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4
4
<!ENTITY CONFNAME "mandos-clients.conf">
5
5
<!ENTITY CONFPATH "<filename>/etc/mandos/clients.conf</filename>">
6
 
<!ENTITY TIMESTAMP "2012-05-27">
 
6
<!ENTITY TIMESTAMP "2012-01-01">
7
7
<!ENTITY % common SYSTEM "common.ent">
8
8
%common;
9
9
]>
66
66
      ><refentrytitle>mandos</refentrytitle>
67
67
      <manvolnum>8</manvolnum></citerefentry>, read by it at startup.
68
68
      The file needs to list all clients that should be able to use
69
 
      the service.  The settings in this file can be overridden by
70
 
      runtime changes to the server, which it saves across restarts.
71
 
      (See the section called <quote>PERSISTENT STATE</quote> in
72
 
      <citerefentry><refentrytitle>mandos</refentrytitle><manvolnum
73
 
      >8</manvolnum></citerefentry>.)  However, any <emphasis
74
 
      >changes</emphasis> to this file (including adding and removing
75
 
      clients) will, at startup, override changes done during runtime.
 
69
      the service.  All clients listed will be regarded as enabled,
 
70
      even if a client was disabled in a previous run of the server.
76
71
    </para>
77
72
    <para>
78
73
      The format starts with a <literal>[<replaceable>section
167
162
            This option is <emphasis>optional</emphasis>.
168
163
          </para>
169
164
          <para>
170
 
            This option overrides the default shell command that the
171
 
            server will use to check if the client is still up.  Any
172
 
            output of the command will be ignored, only the exit code
173
 
            is checked:  If the exit code of the command is zero, the
174
 
            client is considered up.  The command will be run using
175
 
            <quote><command><filename>/bin/sh</filename>
 
165
            This option allows you to override the default shell
 
166
            command that the server will use to check if the client is
 
167
            still up.  Any output of the command will be ignored, only
 
168
            the exit code is checked:  If the exit code of the command
 
169
            is zero, the client is considered up.  The command will be
 
170
            run using <quote><command><filename>/bin/sh</filename>
176
171
            <option>-c</option></command></quote>, so
177
172
            <varname>PATH</varname> will be searched.  The default
178
173
            value for the checker command is <quote><literal
409
404
        <quote><literal>approval_duration</literal></quote>,
410
405
        <quote><literal>created</literal></quote>,
411
406
        <quote><literal>enabled</literal></quote>,
412
 
        <quote><literal>expires</literal></quote>,
413
407
        <quote><literal>fingerprint</literal></quote>,
414
408
        <quote><literal>host</literal></quote>,
415
409
        <quote><literal>interval</literal></quote>,
512
506
      <citerefentry><refentrytitle>mandos.conf</refentrytitle>
513
507
      <manvolnum>5</manvolnum></citerefentry>,
514
508
      <citerefentry><refentrytitle>mandos</refentrytitle>
515
 
      <manvolnum>8</manvolnum></citerefentry>,
516
 
      <citerefentry><refentrytitle>fping</refentrytitle>
517
509
      <manvolnum>8</manvolnum></citerefentry>
518
510
    </para>
519
511
  </refsect1>