| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|
|
|
| |
Allows it to be used by S3Store, or in fact anything that uses Configuration.
|
|
|
|
| |
S3Stores don't have account numbers.
|
| |
|
|
|
|
|
|
| |
Make some keys not required in BackupDaemonConfigVerify, and verify them
afterwards instead, when the rest of the configuration file has been read
(and in future, the store type would be known.)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It has a sensible default, and backwards compatibility is broken by requiring it.
> Description of fields to fill in above: 76 columns --|
> PR: If a GNATS PR is affected by the change.
> Differential Revision: https://reviews.freebsd.org/D### (*full* phabric URL needed).
> Submitted by: If someone else sent in the change.
> Reviewed by: If someone else reviewed your modification.
> Approved by: If you needed approval for this commit.
> Obtained from: If the change is from a third party.
> MFC after: N [day[s]|week[s]|month[s]]. Request a reminder email.
> MFH: Ports tree branch name. Request approval for merge.
> Relnotes: Set to 'yes' for mention in release notes.
> Security: Vulnerability reference (one per line) or description.
> Sponsored by: If the change was sponsored by an organization.
> Empty fields above will be automatically removed.
M BackupDaemonConfigVerify.cpp
|
| |
|
| |
|
|
|
|
|
|
| |
Add a LogFileOverwrite option to allow configuring whether LogFile is
overwritten or appended to. Overwriting happens at startup, and the start
of each backup in bbackupd (via ResetLogFile()).
|
|
|
|
|
|
| |
Hopefully all of these changes are inconsequential.
Merged back changes from the test refactor branch to reduce diffs.
|
|
|
|
|
|
|
|
|
| |
Merged back changes from the test refactor branch to reduce diffs.
Fix wrong setting of log level in compare() function.
We want to only show errors if we expect mismatches, and show warnings if we
didn't expect mismatches. I had it the other way around before.
|
| |
|
|
|
|
|
|
|
| |
misinterpretation of char * arguments as bools. Use macros to
simplify test code. Test that locations not present when bbackupd
started will be detected and backed up if subsequently created.
|
| |
|
|
|
|
|
| |
Rename ProtocolObject to Message.
|
|
|
|
|
|
| |
dependencies to fail if anything else required by bbstored is still in
lib/backupclient instead of lib/backupstore.
|
|
|
|
|
|
|
| |
than the other way around. This is needed to allow clients to have all the
code that they'd need to implement local backups (using the Local protocol)
in subsequent commits.
|
| |
|
|
|
|
|
| |
multiply referenced object.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
users wanting more detailed restore output.
Disable printing dots when logging at TRACE level is enabled.
Warn rather than failing to restore when the file attributes could not
be restored. (merges [2745], [2827]).
|
| |
|
| |
|
|
|
|
|
| |
directory, old or deleted.
|
| |
|
|
|
|
|
| |
attributes if available in bbackupquery.
|
|
|
|
|
|
|
|
| |
BackupClientFileAttributes.
Add listing of attribute modification time to bbackupquery "list -t"
command.
|
|
|
|
|
|
| |
Add check for changing file creation times on Windows, to cause the
attributes to be uploaded again.
|
|
|
|
|
|
|
|
| |
format as well as the raw numbers.
Use existing helper functions to convert box_time_t to seconds, rather than
just arbitrarily dividing by 1000000.
|
|
|
|
|
|
|
| |
Convert timestamps to host byte order before dividing from usecs to secs,
store in uint64_t variables to avoid truncation, and display in host byte
order.
|
| |
|
|
|
|
|
|
| |
Enable -V option in bbackupquery, and document that -q, -v, -V and
-W<level> are allowed in the command-line help.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
project. See also:
http://patch-tracking.debian.net/package/boxbackup/0.11~rc2+r2072-1
http://lists.warhead.org.uk/pipermail/boxbackup/2009-April/005159.html
|
|
|
|
|
|
|
|
| |
it can't accidentally be used as one.
Fix use of encrypted filename in deleted file message, thanks to Kenny
Millington for reporting.
|
| |
|
|
|
|
|
| |
64 bits.
|
|
|
|
|
|
| |
well (e.g. wxWidgets) and it causes conflicts which are difficult to
resolve.
|
| |
|
|
|
|
|
|
|
| |
fail, for example setting, listing or reading extended attributes,
or creating or changing the owner of a symlink. Thanks to Torsten for
noticing that the filename was not reported in these cases.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ensure that backup-finish is always called, and add a new event,
backup-ok, which is called just before backup-finish when the backup
run was successful.
Keep track of the last backup status notification sent (excluding
backup-start and backup-finish) and send a notification whenever it
changes.
Add a new boolean option, NotifyAlways, to override that check and
always send notifications to the NotifyScript after every backup run,
for notify scripts which do their own state tracking or otherwise
require notification on every event.
|
| |
|
|
|
|
|
| |
Use SecureZeroMemory rather than memset() to wipe key material on Windows.
|
| |
|
|
|
|
|
| |
for C++ style.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BackupDaemon through BackupClientDirectoryRecord, BackupStoreFile and
BackupStoreFileEncodeStream to ReadLoggingStream, to allow progress
callbacks during file upload and cancelling upload part-way.
Implement ReadLoggingStream::Logger in
BackupClientDirectoryRecord::SyncParams, which thunks the notifications
back to the ProgressNotifier.
Add the SysadminNotifier interface from Boxi.
Add NotifyIDMapsSetup() to ProgressNotifier.
Change BackupClientDirectoryRecord::SyncParams to store references to
the individual callback interfaces rather than BackupDaemon.
Initialise all members in BackupDaemon.
Add ability for BackupDaemon user to override the ProgressNotifier,
LocationResolver, SysadminNotifier and RunStatusProvider that will be
used during the backup.
Make BackupDaemon::Location class public and provide access to the
configured locations for Boxi (dangerous, they could be modified without
BackupDaemon knowing it).
|
|
|
|
|
| |
potentially other frontends and allow stopping a backup in progress.
|
| |
|