similar to: Flush delete command on rsync exit with --remove-source-files

# HG changeset patch # User inakoshi.hiroya@jp.fujitsu.com # Date 1191287395 -28800 # Node ID 5543e74774a826b1781893982ed5052312b820fc # Parent 83239b2890723e0c06bad507bb273a970784b18e Flush stdout when xentop -b gets SIGINT and SIGTERM. It is useful when you stop xentop -b by keyboard interrupt or by other programs such as killall from a batch script. You would have missed the bottom part of

What is the order that rsync uses to set permissions? Time Machine directories have ACL permissions that basically prohibit making any changes of any kind. In order to make a backup of the directory, you would need to set those permissions after copying everything in the subdirectories. Is rsync smart enough to do it in that order? On 2018-03-19, at 10:44 PM, Andre Althoff via rsync <rsync

https://bugzilla.samba.org/show_bug.cgi?id=9882 Summary: Incorrect exit code when sender over SSH is killed with SIGTERM Product: rsync Version: 3.1.0 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

That doesn’t work too. :-( Last login: Mon Mar 19 19:18:16 on console iMac:~ andre$ mount /dev/disk0s2 on / (hfs, local, journaled) devfs on /dev (devfs, local, nobrowse) map -hosts on /net (autofs, nosuid, automounted, nobrowse) map auto_home on /home (autofs, automounted, nobrowse) /dev/disk2 on /Volumes/G-DRIVE Thunderbolt 3 (hfs, local, nodev, nosuid, journaled, noowners) iMac:~ andre$

Hi, I''m wondering why SIGINT and SIGTERM both were chosen for the quick shutdown? I agree with SIGINT but not with SIGTERM. A lot of unix tools send SIGTERM as default (kill, runit among some) and it seems to be the standard way of telling a process to quit gracefully but not among Ruby people (there are a few other ruby processes behaving the same way). I just think it''s weird

Hi all, I'm using rsync to replicate a cvs repository, it is working quite good except that I occassionnaly see rsync stucked after having transfered a file, it is always on a big ,v file containing multiple version of big binary file. I haven't gathered the netstat information on the frozen process (it is not easy to reproduce the problem), but I have the strace information : - the

Hi R developers, I observed that system(timeout=) may still return exit code 0, when killing the process due to timeout. In src/unix/sys-unix.c there is #define KILL_SIGNAL1 SIGINT #define KILL_SIGNAL2 SIGTERM #define KILL_SIGNAL3 SIGKILL #define EMERGENCY_TIMEOUT 20 After little bit of debugging I observed that total time of system call is provided timeout value + 20s. That means

hi, please test this. if ssh is called with SIGINT ignored (e.g. from a backup system, with rmt) then ssh should not overwrite set it's own handler. Index: clientloop.c =================================================================== RCS file: /cvs/src/usr.bin/ssh/clientloop.c,v retrieving revision 1.104 diff -u -r1.104 clientloop.c --- clientloop.c 22 Aug 2002 19:38:42 -0000 1.104 +++

https://bugzilla.samba.org/show_bug.cgi?id=9502 Summary: Deamon deadlock at stop (SIGINT caught) Product: rsync Version: 3.0.7 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: jurij at ocslab.com

sh-3.2# /Users/andre/Desktop/Skripte/rsync_tm Kopiere Time Machine Backup ... rsync: chgrp "/Volumes/G-DRIVE Thunderbolt 3/Backups.backupdb/.RecoverySets/0/com.apple.recovery.boot/boot.efi" failed: Operation not permitted (1) rsync: failed to set times on "/Volumes/G-DRIVE Thunderbolt 3/Backups.backupdb/iMac": Operation not permitted (1) rsync: symlink "/Volumes/G-DRIVE

The default path is /var/run/tftpd-hpa.pid, which can be overridden by the newly introduced -P option. On normal termination (SIGTERM or SIGINT) the pid file is automatically removed. Moved setting the umask later, right before entering the select loop, so that it does not affect the permissions of the pid file. Signed-off-by: Ferenc Wagner <wferi at niif.hu> --- tftpd/tftpd.c | 38

I'm attempting to maintain a mirror of a remote database, ~ 66Gb on a FreeBSD platform. I do not have direct access to the database except by rsync, anon. ftp etc. I'm running rsync nightly from crontab, with the cmd /usr/local/bin/rsync -avvv --port=33444 ftp.filesource.org::ftp . >> rsynclog generated the following in the cron report First error [1] rsync error: received SIGINT,

Hi all, when running backups, rsync sometimes does not terminate. I finally managed to create a small test case which reproduces this behaviour (another night without sleep, so sorry for the bad English...): Using rsync 3.1.0 [no change in a quick test I ran after compiling 3.1.1] on Linux (x86_64) the following sequence causes rsync not to terminate: > mkdir srclt2

I have a script that normally runs my snapshot that I haven't used for the past several days because something seemed to be going wrong and I wanted to run things manually. But running the script twice today, I got: > snaphome Found 15 mounted dated, snaps or snap archives ?[snapper#2120]base_mp=/home 1 snap dated today. (Use: '--force=force_create_snap' to force another snap.)

From: Matt Fleming <matt at console-pimps.org> Uncovered a bug in avr32 signal handling, might come handy in testing other archs signal. Signed-off-by: Matt Fleming <matt at console-pimps.org> Signed-off-by: maximilian attems <max at stro.at> --- Seen on lmkl, any objections to add your test to klibc: http://git.kernel.org/?p=libs/klibc/klibc.git;a=summary We know archs were

https://bugzilla.samba.org/show_bug.cgi?id=4139 Summary: Generator process (running as daemon) hangs after kill SIGINT. Product: rsync Version: 2.6.8 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Hello everyone, I am searching and searching and can't find an answer. I try to register a sighandler in my extension's C code. But my sighandler is never called. Is there anything preventing extensions to receive signals? I register like this: [.. some code that works ..] // register the sigint listeners. if (signal(SIGTERM, killReceiver) == SIG_ERR) {

Trying to do something like this, in Ubuntu 11.10/12.04: Location A (work occurs changing files) rsync --write-batch /media/bkup/foo.rsb /path/to/files/ /path/to/copy/ Location B rsync --read-batch /media/bkup/foo.rsb /path/to/files/ rsync --read-batch /media/bkup/foo.rsb /path/to/copy/ (work occurs changing files) rsync --write-batch /media/bkup/foo.rsb /path/to/files/ /path/to/copy/

Hi, As the man page says, the --partial flag is to "keep partially transferred files". I'm assuming if I don't have partial flag any partially transferred files should be deleted. However this is not what I'm seeing. Example: (Using a big file so that rsync times a while to run. This gives me time to hit CTRL-C for the SIGINT). > mkdir example > dd if=/dev/zero

This is more a question than a serious proposal. The name of the pid file should probably be configurable, and it should be unlinked on normal termination, but no such thing exists in standalone mode. SIGTERM and SIGINT should be catched and considered normal, I guess. Signed-off-by: Ferenc Wagner <wferi at niif.hu> --- tftpd/tftpd.c | 7 +++++++ 1 files changed, 7 insertions(+), 0