samba-bugs at samba.org
2011-Mar-23 14:47 UTC
[Bug 8036] New: rsync should refuse -B values larger than the maximum block size
https://bugzilla.samba.org/show_bug.cgi?id=8036 Summary: rsync should refuse -B values larger than the maximum block size Product: rsync Version: 3.0.7 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: informatique at numerigraphe.com QAContact: rsync-qa at samba.org The maximum value for -B does not seem to be enforced when parsing the command-line options: it will happily start working with larger values, often to fail with a protocol error after some blocks are transfered. The maximum value (2^17 if I'm not mistaken) should be enforced and reported to the user, all the more as it is mostly undocumented. Lionel Sausin. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
samba-bugs at samba.org
2011-Dec-24 20:19 UTC
[Bug 8036] rsync should refuse -B values larger than the maximum block size
https://bugzilla.samba.org/show_bug.cgi?id=8036 Wayne Davison <wayned at samba.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Version|3.0.7 |3.1.0 Resolution| |FIXED Severity|enhancement |minor --- Comment #1 from Wayne Davison <wayned at samba.org> 2011-12-24 20:19:57 UTC --- I'm checking in a fix for this. -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Reasonably Related Threads
- [Bug 8090] New: full_fname out of memory error on missing file SunOS 5.8
- DO NOT REPLY [Bug 7965] New: --max-size=0 is invalid (should transfer 0-byte files)
- [Bug 8411] New: invalid flist flag when using protocol 28 or 29
- DO NOT REPLY [Bug 7865] New: files or dirs with more than 16 ACLs are not rsynced correctly
- NUT 2.8.0-7 Can't claim USB device [2341:8036]@2/0: Invalid parameter using usbhid-ups