similar to: Signals to AGI scripts

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 folks, man page says "By default, rsync will delete any partially transferred file if the transfer is interrupted" I have (reproducible) a partial file left, if I do CTRL-C source-dir: mounted LVM XFS dest-dir: see source-dir Ubuntu 12.04.1 (LTS) kernel 3.2.0-39-generic command: rsync -a

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

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,

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.)

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) {

FWIW, now that privsep is mandatory I have no objection to including signal support in sshd. On Wed, 25 Jul 2018, Yonathan Bleyfuesz wrote: > Hi all, > > I would like to propose some ideas to revivify this subject. > > -First, we could add support on the client to send signal thanks to the escape characters. > (code :

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

# 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

Dear rsync users, I'm trying to copy my Time Machine Backup from my old USB hard drive to a new one. I got error messages, because rsync don't create group and other permissions. I use rsync 3.1.3. Did I use the correct parameters? Who has an idea, what mistake? Thanks! Best, André -- The bash script: #!/bin/bash source=/Volumes/LaCie\ d2\ Quadra\ v3/Backups.backupdb

Hi, I search in archive list if there any reason why is removed in openssh newer than 2.9.9 from function 'void session_close_by_channel(int id, void *arg)' sending of SIGTEMR and SIGHUP signals to child as was in 2.9.9 version? See follow sniped code from 2.9.9 sources: ---- openssh-2.9.9/session.c ---------------------------------------- void session_close_by_channel(int id, void

Hi, >>> It would be nice to know what the precise technical issues are that have >>> prevented support for this from being added. From what I recall, it >>> seemed like the delay was largely due to details of the client >>> behaviour, and possibly some feature creep. It would indeed be really great to have some details on this point. Concerning the test of

Hi, This is my current patch queue. The patches are independent, AFAIK, so feel free to cherry-pick or reject them independently. The bottom one was needed for a successful build here; the top one contains all the modifications you requested on IRC, and more. Meanwhile I hit one of the four stray TABs in tftpd.c, and decided to get rid of them. Comments welcome. --- Ferenc Wagner (5):

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

https://bugzilla.samba.org/show_bug.cgi?id=5020 Summary: hang using RSYNC_CONNECT_PROG Product: rsync Version: 3.0.0 Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: Matt_Domsch@dell.com QAContact:

I have a continuous loop running in an external library that I am calling from C (R API). This loop is processing events in real time with the possibility of significant lag between events. When processing an event, I can make use of R_CheckUserInterrupt, but while the external library code is waiting on a new event, I don't have an opportunity to call this - my entry points are only on

https://bugzilla.samba.org/show_bug.cgi?id=8265 Summary: Long paths, hardlinks, 'special' files [was: Regression: sockets for 3.0.9pre1] Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P1 Component: core AssignedTo:

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

https://bugzilla.samba.org/show_bug.cgi?id=10675 Summary: rsyncing >2GB file onto fat32 partition should fail earlier Product: rsync Version: 3.1.0 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

Daniel: thought you'd like to know that I'm forwarding this to the vorbis-dev mailing list. <p><p>Hey vorbis-dev (after a very long time!), I got the attached message sent to just 3 of the people who have worked on ogg123, and thought it would probably due better good on the mailing list. It seems to concern http://bugs.xiph.org/show_bug.cgi?id=250 by casual search. For