similar to: [patch] Add `--link-by-hash' option (rev 2).

This patch adds the --link-by-hash=DIR option, which hard links received files in a link farm arranged by MD4 file hash. The result is that the system will only store one copy of the unique contents of each file, regardless of the file's name. (rev 3) * Don't link empty files. * Roll over to new file when filesystem maximum link count is reached. * If link fails for another reason, leave

This patch adds the --link-by-hash=DIR option, which hard links received files in a link farm arranged by MD4 file hash. The result is that the system will only store one copy of the unique contents of each file, regardless of the file's name. (rev 4) * Updated for committed robust_rename() patch, other changes in CVS. (rev 3) * Don't link empty files. * Roll over to new file when

This patch adds the --link-by-hash=DIR option, which hard links received files in a link farm arranged by MD4 file hash. The result is that the system will only store one copy of the unique contents of each file, regardless of the file's name. (rev 5) * Fixed silly logic error. (rev 4) * Updated for committed robust_rename() patch, other changes in CVS. (rev 3) * Don't link empty

This patch adds the --link-by-hash=DIR option, which hard links received files in a link farm arranged by MD4 file hash. The result is that the system will only store one copy of the unique contents of each file, regardless of the file's name. Anyone have an example of an MD4 collision so I can test that case? :) Patch Summary: -1 +1 Makefile.in -0 +304 hashlink.c (new)

Hi, I have written a 'smallish' patch to implement the --inplace option as discussed on this mailing list at various points in the past. It makes a small modification to the sender algorithm so that it won't ask the receiver to relocate blocks from earlier in the file when running with the --inplace option. I would appreciate any testing and feedback people can provide! I

Hi Ralph, On 05.01.15 15:00, Ralph B?hme wrote: >> [Programs] >> path = /server/shares/programs >> valid users = some users >> read only = No >> force create mode = 0660 >> force directory mode = 0770 >> vfs objects = fruit # tried without fruit vfs, no change > > on first reading I thought this sound

Hi List, I had a need recently to efficiently synchronise between some large LUNs (boot drive disks) at two different datacentres. Solutions like drbd and $proprietary_array_vendors_software were overkill - we only needed (wanted!) to periodically synchronise these LUNs whenever major changes were generated on the source. On the other hand however, re-sending the entire disk contents each time

Wayne, It's taken a little while for me to get more familiar with the code, but I think I've reached a good breakpoint in improving batch-mode. Let me highlight some of the changes in the attached patch: * --write-batch and --read-batch arguments are no longer passed from client to server. This fixes the current problem that causes the server threads to die when the client

Dear List, the attached patch makes rsync of local folders almost as fast as cp. when rsync client and server has detected that they are working in local_server mode, they use local_socket, a unix domain socket pair, to pass the file descriptors of the synced files. the server uses the file descriptor it receives from the client to fast copy from src to dst file. on completion of every file fast

Help! I wanted to make a ruby interpreted variable <%= @variable %> to be the linkname of my <%= link_to "linkname", {options" %> expression. How can I do that? -- Anime ni naruttebayo!!! Uchiha Itachi''s Trashcan@ptoys http://ptoys.proboards40.com/index.cgi?board=showroom&action=display&thread=1108620582 -------------- next part -------------- An

hello, all of users: sorry, resend it again for clarifying the message. I have implemented cha_ss7 in china. initially, the chan_ss7 can not support the call group. i modify the code. now the problem is that, both sides can hear the ring, but i can not hear the voice from each other. i think the ss7 does not send the voice steam to the destination. in chan_ss7, i added:

I want to make you aware of a possible bug in the reflink handling of btrfs: When I reflink a file larger 2GB (on the same subvol), the reflinking fails. But it works fine for files smaller 2GB in size. I was able to track this down to btrfs with great support of Martin Raiber who created a small demo code: Source: https://urbackup.atlassian.net/secure/attachment/10201/reflink.cpp Compile: g++

Hi All, I''ve configured a mutlipath as detailed in the HOWTO. For the most part it''s great, but when the cheap DSL line drops it''s connection, as it regularly does, the outbound routing doesn''t automatically use the remaining path for internal outbound traffic. Ip route show lists no default route once the default path dies, and if the ppp connection is

Hi, Pradeep: I believe you had some questions about modifying bandwidth for flows/VNICs. I believe that should be fine in the recently released bits, could you please check and lets know if you still have any questions about this. Bandwidth limits can be modified using: links: dladm set-linkprop -p maxbw=<value> linkname flows: flowadm set-flowprop -p maxbw=<value> flowname (I

https://bugzilla.samba.org/show_bug.cgi?id=4899 Summary: When a mounted dir cannot be visited, rsync will halt there and the shell is halted, even "ctrl -c" can't quit it. Product: rsync Version: 2.6.9 Platform: x86 OS/Version: Linux Status: NEW Severity: normal

I can''t explain where those differences come from. In one Project I can use the link_to without any problems. Like this: <%= link_to "LINKNAME", :action => "destroy", :id => ID %> But in another project... That happens <%= link_to "delete", :action => "destroy", :id => ticket.id %> <%= link_to "edit", :action

Yes, it's time once again to return to the subject of moving files. With the recent changes to the communications code between the receiver and the generator, there is now a non-clogging channel that we can use to signal the sender when a file has been successfully transferred, which allows us delete the original for all transferred files. I have in the past waffled on whether this feature

https://bugzilla.samba.org/show_bug.cgi?id=6293 Summary: rsync crashes when transferring files Product: rsync Version: 3.0.5 Platform: x86 OS/Version: Mac OS X Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: dirk.samba@miriup.de

Hi all. I have just finished a small patch that adds support for multiple --compare-dest or --link-dest args. Its primary usage is to do incremental backups on top of eachother. (My current backup system stores each incremental as a single diff of the latest full.) Example: First full backup: rsync -a somedir full-20040415/ First incremental: rsync -a --compare-dest=../full-20040415 \

On Thu, 10 Sep 2015 10:55:04 +0300 Imran Zaman via Syslinux <syslinux at zytor.com> wrote: > devname is put on heap for all cases to avoid memory > leak, and ease of use in future as well > > Signed-off-by: Imran Zaman <imran.zaman at intel.com> Reviewed-by: Paulo Alcantara <pcacjr at zytor.com> Thanks, Paulo > --- > extlinux/main.c | 44