runs on client computers in the background, finding new files to back up. When it is time for a backup,
will connect to the server (bbstored) to upload the files.
daemon can be controlled with the
command, to make it shut down, reload its configuration, or start an immediate backup.
needs to be configured to tell it which files to back up, how often, and to which server (running
bbstored). See the Client Configuration page for more information. For this, you must write a configuration file. You must either place it in the default location, or tell
where to find it.
You can check the default location with the
option. The default on Unix systems is usually
/etc/box/bbackupd.conf. On Windows systems, it is
in the same directory where
is located. If bbackupd cannot find or read the configuration file, it will log an error message and exit.
usually writes log messages to the system logs, using the facility
local5, which you can use to filter them to send them to a separate file. It can also write them to the console, see options below. If
is not doing what you expect, please check the logs first of all.
Use the specified configuration file. If
is omitted, the last argument is the configuration file. If none is specified, the default is used (see above).
Debugging mode. Do not fork into the background (do not run as a daemon). Not available on Windows.
No-fork mode. Same as
for bbackupd. Not available on Windows.
Keep console open after fork, keep writing log messages to it. Not available on Windows.
Run more quietly. Reduce verbosity level by one. Available levels are
EVERYTHING. Default level is
in non-debugging builds. Use once to drop to
level, twice for
level, four times for no logging at all.
Run more verbosely. Increase verbosity level by one. Use once to raise to
level, twice for
level, three times for
(currently the same as
Run at maximum verbosity (EVERYTHING
Tag each console message with specified marker. Mainly useful in testing when running multiple daemons on the same console.