similar to: [PATCH] ssh-agent: exit 0 from SIGTERM under systemd socket-activation

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:

comments? alternatives: sigsetjmp(ugly) and pselect(not portable, available) drawback: additional filedescriptors. Index: serverloop.c =================================================================== RCS file: /home/markus/cvs/ssh/serverloop.c,v retrieving revision 1.82 diff -u -r1.82 serverloop.c --- serverloop.c 10 Oct 2001 22:18:47 -0000 1.82 +++ serverloop.c 11 Oct 2001 18:06:33 -0000 @@

This adds support for systemd socket-based activation in the ssh-agent. When using socket activation, the -a flag value must match the socket path provided by systemd, as a sanity check. Support for this feature is enabled by the --with-systemd configure flag. --- Something tells me upstream would not be interested in this patch, but as it may be useful on linux, I'm submitting it here.

Hi! I'm investigating the seccomp filter in openssh and I wanted to know whether the following system calls should be added to the filter: 1. getgroups - do_authentication2->dispatch_run_fatal->sshpkt_fatal->logdie->cleanup_exit->do_cleanup->temporarily_use_uid->getgroups 2. setgroups -

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

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 @@

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

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

http://bugzilla.mindrot.org/show_bug.cgi?id=1029 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED ------- Comment #8 from dtucker at zip.com.au 2006-10-07 11:40 ------- Change all RESOLVED bug to CLOSED with the exception

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

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

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

Hi, Unicorn is saying it''s terminating but it''s not actually. Check out the gist:?https://gist.github.com/1104930 Using: - Ruby 1.9.2p180 - unicorn 4.0.1 - kgio 2.6.0 - bundler 1.0.15 - Linux maynard 2.6.38-10-generic #46-Ubuntu SMP Tue Jun 28 15:07:17 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux Please let me know if there''s any other info I can provide. Thanks, Jesse

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

# 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 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

Socket activation (aka systemd socket activation) is a simple protocol that lets you pass in an opened, listening socket to a server. Supporting socket activation allows you to use a modern superserver to serve infrequent NBD requests without needing nbdkit to be running the whole time. Although the protocol was invented by systemd, it has been implemented in a few other places, and the protocol

https://bugzilla.samba.org/show_bug.cgi?id=8967 Summary: rsync returns with non-zero exit code when killed by SIGTERM Product: rsync Version: 3.0.9 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org

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

Let me start this with the disclaimer that I am a Linux lover that only pretends to have any clue about coding. I grabbed the latest version of OpenSSH (v2.9p1) and went to install it on my Sparc (RH 6.2, v2.4.2). Unlike OpenSSH 2.5.2p2, however, when I tried to compile it I got the following error: ... <compiling away> ... gcc -g -O2 -Wall -I. -I. -I/usr/local/ssl/include