similar to: [patch] Add `--link-by-hash' option.

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 2) * This revision is actually against CVS HEAD (I didn't realize I was working from a stale rsync'd CVS). * Apply permissions after

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 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 5) * Fixed silly logic error. (rev 4) * Updated for committed robust_rename() patch, other changes in CVS. (rev 3) * Don't link empty

https://bugzilla.samba.org/show_bug.cgi?id=8654 Summary: link-by-hash: Fix (non-exploitable) buffer overflow Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: chris at onthe.net.au

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

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

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

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> --- extlinux/main.c | 44 ++++++++++++++++++++++++++++++-------------- 1 file changed, 30 insertions(+), 14 deletions(-) diff --git a/extlinux/main.c b/extlinux/main.c index 55a1495..b7cdf92 100644 --- a/extlinux/main.c +++ b/extlinux/main.c @@

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> --- extlinux/main.c | 48 ++++++++++++++++++++++++++++++++---------------- 1 file changed, 32 insertions(+), 16 deletions(-) diff --git a/extlinux/main.c b/extlinux/main.c index 55a1495..7bb7443 100644 --- a/extlinux/main.c +++

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> --- extlinux/main.c | 50 +++++++++++++++++++++++++++++++++----------------- 1 file changed, 33 insertions(+), 17 deletions(-) diff --git a/extlinux/main.c b/extlinux/main.c index bc7ded3..74f8d1f 100644 --- a/extlinux/main.c +++

smbclient (and smbtar) in version 2.2.7a (and prior) has problems with large files (> 4GB). The following patch (against 2.2.7a) fixes all known problems with this. This code has been checked into the CVS tree in all branches as well. -- ====================================================================== Herb Lewis Silicon Graphics Networking Engineer

Full_Name: Jeff Hallman Version: 2.4.1 OS: Linux Submission from: (NULL) (132.200.32.34) When I filed this a few minutes ago, I left off the rewritten read.ssd(). I've included it at the end this time. read.ssd() invokes PROC COPY to create an xport file, but PROC COPY has some annoying limitations that read.ssd() should deal with. The first is that PROC COPY doesn't work with member

- fix names of arguments & optional arguments in C<..> markers - use https for URLs where possible - fix links to other guestfs APIs - use more C<..> markers for special tests, shell commands, values of arguments, and names of fields - link to command man pages where an explicit command is mentioned - fix few incorrect documentation bits --- generator/actions_augeas.ml