similar to: Is there a way to get an rsync client to communicate over stdin/stdout?

Take a look at the lsh scripts that come with rsync. On 10/10/2018 02:53 PM, Parke via rsync wrote: > Hello, > > Is there a way to get an rsync client to communicate over stdin/stdout? > > I found these two emails from 2004. The second email mentions that > there might be a patch. > > https://www.mail-archive.com/rsync at lists.samba.org/msg09392.html >

Hello All, I want to use rsync in a process and for the i want it to take password from file instead of stdout. Is there any way to do it in rsync ? Thanks, -- Regards Garvit Sharma Computer Science and Engineering UG Third year LNM IIT, Jaipur *No Body is a Scholar by birth, its only hard work and strong determination that makes him master.* * * -------------- next part -------------- An

https://bugzilla.samba.org/show_bug.cgi?id=9246 Summary: Add chroot enablement option to rsync client Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: bmn at mailinator.com

Hi, I'm planning to embed R into an application, with the following context: - This application is written in Java (and managed with maven). I plan accessing R using JRI. - This application must be installable on several plateform (linux, mac os, windows). - The R engine must embed library, some of them having native code in C or Fortran. Does this sound reasonable? I would be very

Hi all, I need to know the details of "save transfer" command using rsync. What is the purpose of using this command. Can we save only the diffs of files using this command? Does it works on stand alone system? Please give me the syntax this command for stand alone system as i want to back up of one directory to another directory(these may be in different partition of hard disk).

I made some tests with smbclient and gzip, and it seems to me that what I'm doing should be safe, but I'd like to know if this kind of input and output redirection has some "hidden" drawbacks/problems: may it cause corruption of output files? backup: smbclient '\\server\share' -Tc - | gzip > file.tar.gz restore: gzip -dc file.tar.gz | smbclient

$ ./nbdkit ssh host=localhost /nosuchfile password=-0 --run 'qemu-img info $nbd' abc fcntl: Bad file descriptor The reason for this is that we close the file descriptor after reading the password. Closing stdin causes bad stuff to happen. --- docs/nbdkit-plugin.pod | 5 +++++ server/public.c | 4 ++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git

Hi, to make in/output on STDIN/STDOUT work on OS/2 this small patch is needed: ---cut--- diff -ruN o:src/speexdec.c src/speexdec.c --- o:src/speexdec.c 2007-12-08 05:01:08.000000000 +0100 +++ src/speexdec.c 2008-01-12 00:48:00.000000000 +0100 @@ -231,6 +231,8 @@ { #if defined WIN32 || defined _WIN32 _setmode(_fileno(stdout), _O_BINARY); +#elif defined OS2 +

> Yes, in that we changed the compile time default at some point between those two because pipes have better close semantics for what sshd wants to do. Thanks for quick reply, appreciate it. > That sounds a bit silly. Which daemons? At least python-daemon lib. Look here for functions is_process_started_by_superserver() and is_detach_process_context_required()

Hi, i'm using dovecot-1.0-stable. All my mail accounts are virtual accounts that come from pam with the following configuration in auth_default: passdb = pam userdb = static uid=5000 gid=5000 home=/var/mail/vhost/example.com/%n mail=/var/mail/vhost/example.com/%n for a user foo, if the directory /var/mail/vhost/example.com/foo already exists, then all is ok, but if the directory

So I've got this situation where I have two systems connected via a protocol that looks nothing at all like IP, and I'd like to be able to rsync between them. I can, though, open a perfectly normal looking socket through various magic and trickery. I've managed to get rsync to work by using the "rsync --rsh=mymagictransportprogram" style invocation, but for a number of

From: Matt Fleming <matt.fleming at intel.com> The location of __file_info[] and ansicon_counter are split between the core and ldlinux.c32. We can end up calling __ansicon_close (from fp->oop->close) in the process of reloading ldlinux.c32, and while ansicon_counter is set to its initialised data value of 0 when reloading ldlinux.c32, the core is never reloaded, and so __file_info[]

https://bugzilla.mindrot.org/show_bug.cgi?id=2476 Bug ID: 2476 Summary: ssh fails to report IO errors on stdin/stdout/stderr Product: Portable OpenSSH Version: 6.0p1 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P5 Component: ssh Assignee: unassigned-bugs at

Hi, I am runing rsync --backup --backup-dir=$BACKUPDIR where the BACKUPDIR=$(date +%d) to recycle the $BACKUPDIR in a month. But rsync does not clean the $BACKUPDIR before writing to it in cycling. I guess you have to clean it manually before the rsync can write to it. As my $BACKUPDIR is in remote machine, do you have to run ssh to delete it first before calling rsync in a script? Or if there

https://bugzilla.samba.org/show_bug.cgi?id=11166 Bug ID: 11166 Summary: running with -vvv causes a hang Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter: pskocik at

Hi all, I'm sending patch "Optimize silk_warped_autocorrelation_FIX() for ARM NEON" in an separate email. It is based on Tim’s aarch64v8 branch https://git.xiph.org/?p=users/tterribe/opus.git;a=shortlog;h=refs/heads/aarch64v8 Thanks for your comments. Linfeng

Hey, guys, I have a question about a difference between openssh 4.3 and 5.3. I have plenty of servers with RHEL5 and RHEL6. Most of RHEL5 servers have openssh-server version 4.3p2-72.el5_6.3 (kernel 2.6.39-100.7.1uek) And RHEL6 servers have 5.3p1-111.el6 (kernel 3.8.13-35.el6uek.x86_64) So there is the difference in assigning stdin and stdout for ssh connections. Openssh 4.3 assigns socket (I

Hi again! While investigating the bug report [*] I found out that on unix, system2 does not quote its `stdin` argument while preparing the command line to launch. It does shQuote the `stdout` and `stderr` arguments, and also the `f <- tmpfile()` variable (which is used if `input` argument is provided), which seems to set a precedent. On Windows, stdin, stdout, and stderr are handled

Hello, I am very new to R but my question is with respect to the C API for working with an embedded R console. I have been able to start and stop an embedded R console from within a C program as well as use the API to execute commands in it. I am seeking a mechanism to individually send native R commands to an embedded console and then consume the output of these commands. Specifically, I

VDDK plugin + --run was broken because of the following sequence of events: (1) After .config_complete, server redirects stdin/stdout to /dev/null. (2) Server then calls vddk_get_ready which reexecs. (3) We restart the server from the top, but with stdin/stdout redirected to /dev/null. So saved_stdin/saved_stdout save /dev/null. (4) run_command is called which "restores"