similar to: [Bug 8967] New: rsync returns with non-zero exit code when killed by SIGTERM

https://bugzilla.samba.org/show_bug.cgi?id=8416 Summary: Please include systemd service file 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: michael+samba at stapelberg.de

https://bugs.freedesktop.org/show_bug.cgi?id=50175 Bug #: 50175 Summary: [regression kernel 3.4] : nouveau detects internal laptop display as "disconnected" / screen is turned off Classification: Unclassified Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version:

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

https://bugzilla.mindrot.org/show_bug.cgi?id=3531 Bug ID: 3531 Summary: Ssh will not exit when it receives SIGTERM before calling poll in client_wait_until_can_do_something until some events happen. Product: Portable OpenSSH Version: 9.1p1 Hardware: Other OS: Linux Status:

If SIGTERM is blocked in the main program, then it ends up still being blocked in the subprocess after we fork. This means that we cannot kill qemu by sending SIGTERM to it. This commit fixes the problem by unblocking SIGTERM unconditionally after fork. Thanks: wtfuzz on IRC for reporting and analysis. --- lib/launch-direct.c | 15 +++++++++++++++ lib/launch-uml.c | 11 +++++++++++ 2 files

We''ve got a small daemon we run on our servers, which looks something like this require File.dirname(__FILE__) + ''/../config/boot'' require File.dirname(__FILE__) + ''/../config/environment'' ActiveRecord::Base.establish_connection do m = Message.next_pending if m m.do_something else sleep 5 end end Stuff gets place in this queue

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

http://bugzilla.mindrot.org/show_bug.cgi?id=1029 Summary: SIGTERM and cleanup of wtmp files Product: Portable OpenSSH Version: 4.0p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org ReportedBy: senthilkumar_sen

# 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

Hi I am using QEMU 0.12.1 as the hypervisor in my RHEL installation of 6.5. I wanted to know if there are any side-effects with respect to VM image corruption when i use SIGTERM signal to kill a qemu-kvm process which effectively stops my VM running on the host. Appreciate if you can provide me some valuable information in this regard. Thanks Jatin

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

Hello! Try to use libvirt with lxc. I use latest centos6 amd64 as a libvirt host (libvirt from xen4 repo) libvirt-daemon-1.2.15-3.el6.x86_64 In container I also use latest centos6 amd64. Container starts with /sbin/init. CentOS 6 came with upstart as default init. My problem is that I could not shutdown container correctly with libvirt. virsh -c lxc:/// shutdown test Domain test is being

If one is using the pidfile as an indicator of sshd's status, it is possible to kill sshd before the sigterm handler gets installed, since the pidfile is written out before the signal handlers are setup. The solution is to simply write the pidfile after the signal handlers are setup. Here's the patch. Rob --- sshd.c.orig Fri Jun 22 11:16:41 2001 +++ sshd.c Fri Jun 22 11:18:32 2001 @@

Found nmbd down with this in the log; [2001/02/27 19:21:36, 0] libsmb/nmblib.c:send_udp(755) Packet send failed to 192.168.113.255(138) ERRNO=Network is unreachable [2001/02/27 19:21:36, 0] libsmb/nmblib.c:send_udp(755) Packet send failed to 192.168.22.255(138) ERRNO=Network is unreachable [2001/02/27 19:22:18, 0] libsmb/nmblib.c:send_udp(755) Packet send failed to 192.168.3.1(137) ERRNO=Network

Hi Jatin, Your guest will have a dirty shutdown… Probably not the best way to shutdown a guest… For the host and other guests, no worries. Greetings, Dominique. Van: Jatin Davey [mailto:jashokda@cisco.com] Verzonden: woensdag 8 april 2015 10:25 Aan: libvirt-users@redhat.com Onderwerp: [libvirt-users] SIGTERM signal to qemu-kvm process Hi I am using QEMU 0.12.1 as the hypervisor in my RHEL

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

Try : apt-get remove libbsd-dev restart samba, now is the message gone? Gr. Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens BasSamba via > samba > Verzonden: woensdag 15 maart 2017 16:09 > Aan: samba at lists.samba.org > Onderwerp: [Samba] samba: setproctitle not initialized, please either call >

The two systems I'm referring to are on different domains, different locations. No connection whatsoever except me being the one administering both. According to oEMInformation the server was provisioned by 4.3.3. I just checked the Samba log file and it seems that version 4.7.4 was running before the update. I'm now looking at the logs right before the upgrade and indeed, there have

https://bugzilla.mindrot.org/show_bug.cgi?id=2158 Bug ID: 2158 Summary: Race condition in receiving SIGTERM Product: Portable OpenSSH Version: 6.2p1 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org

On 08.04.2015 10:24, Jatin Davey wrote: > Hi > > I am using QEMU 0.12.1 as the hypervisor in my RHEL installation of 6.5. > > I wanted to know if there are any side-effects with respect to VM image > corruption when i use SIGTERM signal to kill a qemu-kvm process which > effectively stops my VM running on the host. It's equivalent to plugging the power cord from a