Ignore:
Timestamp:
19/03/2008 07:06:40 (4 years ago)
Author:
jamesog
Message:
  • Update man sections
  • Correct typos
File:
1 edited

Legend:

Unmodified
Added
Removed
  • box/trunk/documentation/bbackupctl.xml

    r2015 r2112  
    44    <refentrytitle>bbackupctl</refentrytitle> 
    55 
    6     <manvolnum>1</manvolnum> 
     6    <manvolnum>8</manvolnum> 
    77  </refmeta> 
    88 
     
    2424    <para><literal>bbackupctl</literal> lets the user control the bbackupd 
    2525    daemon on a client machine. The main use is to force a sync with the store 
    26     server. This is especially important if bbackupd(1) is configured to do 
     26    server. This is especially important if bbackupd(8) is configured to do 
    2727    snapshot backups. In that case <literal>bbackupctl</literal> is the only 
    2828    way to effect a backup.</para> 
     
    3232    connecting on this socket has the correct credentials to execute the 
    3333    commands, leaving a rather sizeable security hole open. To avoid this, 
    34     unset the CommandSocket parameter in <literal>bbackupd.conf</literal>(8). 
     34    unset the CommandSocket parameter in <literal>bbackupd.conf</literal>(5). 
    3535    That disables the command socket, so bbackupd is secure. This does, 
    3636    however, render bbackupctl unusable.</para> 
     
    9494    <title>See Also</title> 
    9595 
    96     <para><literal>bbackupd.conf(8)</literal></para> 
     96    <para><literal>bbackupd.conf(5)</literal></para> 
    9797 
    98     <para>bbackupd(1)</para> 
     98    <para><literal>bbackupd(8)</literal></para> 
    9999  </refsection> 
    100100 
Note: See TracChangeset for help on using the changeset viewer.