similar to: can't manage to get --link-dest working.

https://bugzilla.samba.org/show_bug.cgi?id=4693 Summary: Amazon S3 storage interface for rsync Product: rsync Version: 3.0.0 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: rsync.20.bdixon@xoxy.net

Lets say you had 4 servers and you wanted to setup replicate and distribute. What methoid would be better: server sdb1 xen0 brick0 xen1 mirror0 xen2 brick1 xen3 mirror1 replicate block0 - brick0 mirror0 replicate block1 - brick1 mirror1 distribute unify - block0 block1 or server sdb1 sdb2 xen0 brick0 mirror3 xen1 brick1 mirror0 xen2 brick2 mirror1 xen3 brick3 mirror2 replicate block0 -

Hello guys, I have two mirrors. I need to compare files and directories on both mirrors and as a result print list of those which are missing on mirror 2 What i did find /data > find.mirror1 find /data > find.mirror2 Now i need to get list of those directories which are missing in mirror1. Thanks in advance! David -------------- next part -------------- An HTML attachment was

Hello, I would like to use rsync client over ftp. I know how to use it with ssh but it just can't work with ftp or ncftp. The purpose of usign it with ftp is simple: most webhosting soft. like cpanel or plesk don't monitor ssh bandwidth usage. You need to monitore it in order to suspend an over-quota account. I tried the following: rsync -avze '/usr/bin/ftp -nv' /tmp/testdir

Hi: I have attempted to following some instructions to use --link-dest in order to preserve space for multiple backups. I'm using rsync on Cygwin with a NAS (ext4) which does support hard-links on the filesystem. I've written a short program that does attempt to create a hard-link on this NAS from Cygwin and it does look to be working. If I run ls -li on the NAS the inodes are the same.

Hi, I'm trying to use rsync from Windows to Unix. I've followed the directions on : http://optics.ph.unimelb.edu.au/help/rsync/rsync_pc1.html I can see ssh running on the windows machine, because I tested it using telnet localhost 22 and I can see the result "SSH-2.0-OpenSSH_3.4p1". But when I try "$ rsync -avz -e ssh user@windowsserver::/rsync/* ." from the Linux

https://bugzilla.samba.org/show_bug.cgi?id=13364 Bug ID: 13364 Summary: rsyncd clips trims relative symlinks outside of source tree Product: rsync Version: 3.1.3 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee:

Dear all Some computations gave a matrix. The single value decomposition of it worked fine previously, after an system upgrade I get the following error: ----- > La.svd(x,256,256) Error in La.svd(x, nu, nv) : BLAS/LAPACK routine 'DLASCL' gave error code -4 ----- Erroneous Matrix: ftp://usys-ftp.ethz.ch/ITES/STEP/nussbaum/R/matrix-lapack-error4.RData /.csv Operating System: Debian 8

Hi, I looked though documentation and also checked last 9 months of archives, but could not find the corresponding information. We are having an issue with incremental backup with arkeia. Arkeia checks if ctime/mtime of the file are changed, if so, it backs up. I realized that when I ran rsync from a cammnd line, it changed ctime, and preserved atime of the file in a destination as

I have 6 boxes with a client config (see below) across 6 boxes. I am using distribute across 3 replicate pairs. Since I am running xen I need to disable-direct-io and that slows things down quite a bit. My thought was to move the replicate / distribute to the backend server config so that self heal can happen on faster backend rather then frontend client with disable-direct-io. Does this

It looks like I need to elaborate further to get a feedback. I checked the rsync source code and it is using utime() to restore atime file attribute. It is fine to change ctime for that transferred file in this case. What we are having problem is that when rsync gets kicked off and transfers one file to the destination, this action changes ctime of "all" files in the same

Dear Debian Xen Team, The following possible problem(s) were detected in the package(s) you maintain in Debian: === xen-unstable: = This package has not been in testing for 353 days. = This package has not been able to migrate from unstable to testing for 353 days. See <http://bjorn.haxx.se/debian/testing.pl?package=xen-unstable> This is an automated mail. These mails are sent

Package: xen-unstable Version: 3.3-unstable+hg17879-1 Severity: serious User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20080702 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. Relevant part: > make[5]: Entering directory

Package: xen-utils-common Version: 3.0.3-0-1 Severity: serious Justification: makes package uninstallable Usertags: grid5000 Hi, During a piuparts run over all the packages in etch, I ran into a problem with your package: Setting up xen-utils-common (3.0.3-0-1) ... ln: creating symbolic link `/etc/udev/rules.d/z60_xen-backend.rules' to `../xen-backend.rules': No such file or directory

Source: xen Version: 4.0.1-2 Severity: serious Tags: wheezy sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20110313 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[3]: Entering directory `/build/user-xen_4.0.1-2-amd64-2x64p6/xen-4.0.1/debian/build/build-docs/docs' > latex

Greetings All, I've been thinking about the current behavior of the --link-dest=DIR option. In the absence of --delete, ALL members of DIR should be linked to the destination (aside from those that are changed). If not, there should at least be a --no-link-dest-delete option. (This latter option might be better to avoid disrupting the behavior of current rsync commands) My rational: This

Package: xen-unstable Version: 3.0-unstable+hg11561-1 Severity: serious Build-depends on linux-support-2.6.17-2, which is no longer available in sid. -- Stephen R. Marenka If life's not fun, you're not doing it right! <stephen@marenka.net> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size:

Source: xen Version: 4.1.2-3 Severity: serious Tags: wheezy sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20120321 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[7]: Entering directory `/?PKGBUILDDIR?/debian/build/build-utils_amd64/tools/firmware' > /usr/bin/make -C etherboot

On 03/11/16 19:37, Volker Lendecke wrote: > On Thu, Nov 03, 2016 at 07:11:12PM +0000, Alex Crow via samba wrote: >> >> On 03/11/16 14:28, Ralph Böhme wrote: >>>> Ah, my smb.conf is missing the "ctdb socket" parameter. According to "man >>>> smb.conf" this should be set, but I don't remember seeing it on the wiki >>>> pages.

Hi, AFAIK, the status of Xen in lenny is currently the following: - no dom0 kernel - domU kernel only for i386 (no domU kernel for amd64) I was told (I don't remember where) that this is because the vanilla kernel only supports domU for i386, and has no dom0 support, so distros have to port the patches to their kernels (please correct me if I'm wrong). However: - etch shipped with dom0