similar to: [patch] link-dest messages and max-size warnings (fwd)

Kevin, Thanks for your response. Some observations are inter-lined below. Rob. Regards Rob. Bell e-mail: Robert.Bell at csiro.au -- Dr Robert C. Bell, BSc (Hons) PhD Technical Services Manager Advanced Scientific Computing CSIRO IM&T Phone: +61 3 9669 8102 | Mobile: +61 428 108 333 | CSIRO 93 3810 Robert.Bell at csiro.au | http://www.csiro.au/ | http://www.hpsc.csiro.au/

Folks, Thinking again about the issue of changed attributes for a file in source that is identical in content to a file in destination that is hard linked get propagated to the --link-dest directories I would like to suggest a new flag, (perhaps called something like --preserve-linked-attributes), to allow callers to get the behaviour that is needed to allow the use of recycled

Folks, We faced a similar situation to that which Ken described - we recycle backup directories, for good reason. There is a patch to solve the problem. Our systems administrator provided the following description of the patches we use: ============================================================================ 1. rsync_link_dest improvement by Bryant Hansen Normally, existing files in

I want to manage remote libvirt , have run libvirtd in the dest host : [root@dest_host ~]# ps aux | grep libvirtd root 3293 0.0 0.1 923796 5856 ? Sl 12:59 0:00 libvirtd --daemon then I use the command in source host : 1. [root@source_host ~]# ssh -l root 211.87.***.97 ## login the dest host 2. [root@dest_host ~]# virsh -c qemu+ssh://127.0.0.1/system list

Way back: > > ---------- Forwarded message ---------- Date: Mon, 2 Jun 2003 > > 09:56:50 -0700 (PDT) From: Michael Rubel <mrubel at > > galcit.caltech.edu> To: rsync at lists.samba.org Subject: > > --link-dest when target and compare_dir both have file > > > > Hi J.W. et al, > > > > Kevin Everets was kind enough to inform me about some

tags 407143 +patch thanks On Fri, 2013-08-16 at 14:42 +0100, Ian Campbell wrote: > tags 688308 +patch > thanks > > A lot of /docs/ is pretty low-level and not all that interesting to be > installed by the packages. However some of it is, and in particular some > is referenced from the manpages. I've cherry-picked the bits which I > think are most interesting in that

rsync folks, Henri Shustak <henri.shustak at gmail.com> wrote: > LBackup always starts a new backup snapshot with an empty directory. I > have been looking at extending --link-dest options to scan beyond just > the previous successful backup to (failed backups / older backups). > However, there are all kinds of edge cases which are worth considering > with such a changes. At

Hi, The problem the other way around: IceS -> IceCast -> ShoutCast -> KiSS (the KiSS then decodes the mp3 to a RAW SPDIF stream, which is received by my sourround receiver). But the constallation is somewhat overkill and slightly unstable, so I would prefer just IceS -> IceCast -> KiSS But that does not work at all for unknown reasons (since shoutcast can do this, and the

tags 688308 +patch thanks A lot of /docs/ is pretty low-level and not all that interesting to be installed by the packages. However some of it is, and in particular some is referenced from the manpages. I've cherry-picked the bits which I think are most interesting in that context. Patch below. 8<--------------- commit 7f8ac283e684b7c713d52ed845cab0704a97abab Author: Ian Campbell <ijc

I have a function: source_dir <- function(path, pattern = "\\.[rR]$", chdir = TRUE) ... documented with ... \usage{source_dir(path, pattern="\\.[rR]$", chdir=TRUE)} ... But I get Codoc mismatches from documentation object 'source_dir': source_dir Code: function(path, pattern = "\\.[rR]$", chdir = TRUE) Docs: function(path, pattern =

On UNIX, I am executing an rsync command, from within a script. The command goes something like this: /usr/bin/rsync --verbose --progress --stats --compress --recursive --times --perms --links --safe-links source_dir/ user at target_machine:/parent_path/source_dir In other words, I am replicating source_dir on a remote machine. It ends up next to a lot of sibling, directories, like this: On

ZFS also does some fun things here if you want to build an SSD & spinning disk array - http://zfsonlinux.org/ On 11 January 2017 at 11:56, J Martin Rushton < martinrushton56 at btinternet.com> wrote: > Hmm, don't you just love changing terminology! I've been using HSM > systems at work since '99. BTW, DMAPI is the Data Management API which > was a common(ish)

I'm using a little shell script: BUILD_ROOT=/home/llvm-1.7/cfrontend PREFIX="$BUILD_ROOT/install" LOCAL_BUILD_DIR="$BUILD_ROOT/build" SOURCE_DIR="$BUILD_ROOT/src" echo $__me: Building $TARGET echo $__me: BUILD_ROOT == $BUILD_ROOT echo $__me: SOURCE_DIR == $SOURCE_DIR echo $__me: LOCAL_BUILD_DIR == $LOCAL_BUILD_DIR echo $__me: PREFIX == $PREFIX

HSM also stands for "Hardware security module" Maybe lvmcache would be interesting for you? HSM is more popularly known as "tiering". Cheers, Andrew On 11 January 2017 at 11:15, J Martin Rushton < martinrushton56 at btinternet.com> wrote: > I think there may be some confusion here. By HSM I was referring to > Hierarchical Storage Management, whereby there are

Hmm, don't you just love changing terminology! I've been using HSM systems at work since '99. BTW, DMAPI is the Data Management API which was a common(ish) extension used by amongst others SGI and IBM. Back to lvmcache. It looks interesting. I'd earlier dismissed LVM since it is block orientated, not file orientated. Probably because my mental image is of files migrating to

Hello, Any help on the following issue will be appreciated. How do I delete files or directories in my first level of directory that is specified as host. Here is an example : rsync -avz --delete ${SOURCE_HOST}:/mlinkfam/extract/sccs/pa/* /mlinkfam/extract/sccs/pa Giving above command I find redundant files or directory not getting deleted from the first level of target directory

Andrew, I have a software which need the following package but I can't find it in Internet. Could you advice me where I can download it? samba-3.0.10-1.4E6.HSM.2.i386 samba-common-3.0.10-1.3E.6.HSM.2 samba-client-3.0.10-1.4E.6.HSM.2 Thanks, Isaac Chan

Hello, OpenSSH supports PKCS#11 on the client side, but that does not extend to the server side. I would like to bring PKCS#11 support to sshd. I am working on embedded Linux systems with integrated HSM. The sshd host key is stored on the HSM. To have sshd using that key, we rely on the following chain: sshd -> OpenSSL -> OpenSSL Engine -> HSM Having PKCS#11 support in sshd, would

Some HSM's such as Safenet Network HSM do not allow searching for keys unauthenticated. To support such devices provide a mechanism for users to provide a pin code that is always used to automatically log in to the HSM when using PKCS11. The pin code is read from a file specified by the environment variable SSH_PKCS11_PINFILE if it is set. Tested against Safenet Network HSM. ---

On 11/16/16, 8:55 AM, "openssh-unix-dev on behalf of Juha-Matti Tapio" <openssh-unix-dev-bounces+uri=ll.mit.edu at mindrot.org on behalf of jmtapio at ssh.com> wrote: On Wed, Nov 16, 2016 at 12:54:44PM +0000, Blumenthal, Uri - 0553 - MITLL wrote: > I find this approach very bad in general. > > PKCS#11 standard says that *private* keys should not be