Changeset 2112 for box/trunk/documentation/bbackupctl.xml
- Timestamp:
- 19/03/2008 07:06:40 (4 years ago)
- File:
-
- 1 edited
-
box/trunk/documentation/bbackupctl.xml (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
box/trunk/documentation/bbackupctl.xml
r2015 r2112 4 4 <refentrytitle>bbackupctl</refentrytitle> 5 5 6 <manvolnum> 1</manvolnum>6 <manvolnum>8</manvolnum> 7 7 </refmeta> 8 8 … … 24 24 <para><literal>bbackupctl</literal> lets the user control the bbackupd 25 25 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 do26 server. This is especially important if bbackupd(8) is configured to do 27 27 snapshot backups. In that case <literal>bbackupctl</literal> is the only 28 28 way to effect a backup.</para> … … 32 32 connecting on this socket has the correct credentials to execute the 33 33 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). 35 35 That disables the command socket, so bbackupd is secure. This does, 36 36 however, render bbackupctl unusable.</para> … … 94 94 <title>See Also</title> 95 95 96 <para><literal>bbackupd.conf( 8)</literal></para>96 <para><literal>bbackupd.conf(5)</literal></para> 97 97 98 <para> bbackupd(1)</para>98 <para><literal>bbackupd(8)</literal></para> 99 99 </refsection> 100 100
Note: See TracChangeset
for help on using the changeset viewer.
