https://bugzilla.samba.org/show_bug.cgi?id=8682
--- Comment #6 from Joachim Wagner ---
The "echo > sourcefile" workaround seems to not trigger an error, at least not
straight away and at least on XFS, but instead speeds up the operation and
stops writing more data to the target file. Observation
https://bugzilla.samba.org/show_bug.cgi?id=8682
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.samba.org/show_bug.cgi?id=8682
--- Comment #4 from Christian Kujau ---
If this ever gets implemented: instead of (interactively) pressing a key to
interrupt the current transfer of a particular object, I'd like it to also
react to a signal (e.g. SIGUSR1) that can be sent to rsync
https://bugzilla.samba.org/show_bug.cgi?id=8682
--- Comment #3 from roland ---
that would be a quite useful feature.
i`d recommend that this feature should be activated with a commandline option
for safety purpose. and skipping should then be repeated while the key is
pressed down, so one could
https://bugzilla.samba.org/show_bug.cgi?id=8682
--- Comment #1 from martin f. krafft ---
A hack is to save the file on the backedu up host, and overwrite the inode,
e.g. "echo > file". This will then cause BackupPC to move on and log an error.
But indeed, having the information about
- which
https://bugzilla.samba.org/show_bug.cgi?id=8682
--- Comment #2 from martin f. krafft ---
(the hack is courtesy of Ronny Aasen)
--
You are receiving this mail because:
You are the QA Contact for the bug.
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscrib
