search for: sigterm

Displaying 20 results from an estimated 676 matches for "sigterm".

2017 Jun 10
1
[PATCH] lib: direct, uml: Unblock SIGTERM in the hypervisor and recovery processes (RHBZ#1460338).
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. ---...
2013 Sep 22
0
gpresult returns "ERROR: The RPC server is unavailable."
...20:01:30.191185, 0] ../source4/smbd/server.c:121(sig_term) [2013/09/21 20:01:30.191208, 0] ../source4/smbd/server.c:121(sig_term) [2013/09/21 20:01:30.191223, 0] ../source4/smbd/server.c:121(sig_term) [2013/09/21 20:01:30.191223, 0] ../source4/smbd/server.c:121(sig_term) Exiting pid 30885 on SIGTERM Exiting pid 30882 on SIGTERM [2013/09/21 20:01:30.191221, 0] ../source4/smbd/server.c:121(sig_term) [2013/09/21 20:01:30.191225, 0] ../source4/smbd/server.c:121(sig_term) Exiting pid 30877 on SIGTERM Exiting pid 30876 on SIGTERM Exiting pid 30879 on SIGTERM Exiting pid 30880 on SIG...
2015 Apr 20
0
Joining 2008 R2 to Samba4 AD DC
...s keep me from joining the Samba domain on this server? I'm going to pursue resolving it regardless. I've also checked all the Samba logs I can find, and the only error I see is the following: [2015/04/17 14:59:31.114933, 0] ../source4/smbd/server.c:121(sig_term) Exiting pid 4528 on SIGTERM [2015/04/17 14:59:31.118968, 0] ../source4/smbd/server.c:121(sig_term) [2015/04/17 14:59:31.122492, 0] ../source4/smbd/server.c:116(sig_term) SIGTERM: killing children [2015/04/17 14:59:31.125133, 0] ../source4/smbd/server.c:121(sig_term) Exiting pid 4514 on SIGTERM [2015/04/17 14:59:31.12...
2013 Apr 25
4
Why doesn't SIGTERM quit gracefully?
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 behavin...
2017 Mar 15
1
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
...i, > Ubuntu server edition 16.04.1 > samba 4.3.11-ubuntu > Samba server role = Active directory domain controller > The following log is recurring at /var/log/samba/log.samba > How to resolve it. > > ---------------------------------------------------- > Exiting pid 3013 on SIGTERM > Exiting pid 3015 on SIGTERM > Exiting pid 3014 on SIGTERM > Exiting pid 3023 on SIGTERM > Exiting pid 3018 on SIGTERM > Exiting pid 3025 on SIGTERM > Exiting pid 3020 on SIGTERM > Exiting pid 3028 on SIGTERM > [2017/03/10 16:03:22.478704, 0] ../source4/smbd/...
2023 Feb 01
14
[Bug 3531] New: Ssh will not exit when it receives SIGTERM before calling poll in client_wait_until_can_do_something until some events happen.
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: NEW Severity: enhancement...
2006 Jul 04
1
ActiveRecord write stops script from responding to SIGTERM
...tion do m = Message.next_pending if m m.do_something else sleep 5 end end Stuff gets place in this queue through other interactions with our web application and this guy processes them. This part all works fine. The problem is when we try and stop the daemon running by sending a SIGTERM. If the daemon never found any message to process it exits fine, but if it did then it doesn not respond to the sigterm and we have to kill -9 it. After a bit of investigation we found that our process would respond to SIGTERM properly as long as we had not done any ActiveRecord writes (readin...
2014 Apr 14
1
Samba 4.1.6 huge security flaw
Hi all, I've been running Samba 4.1.6 in production for 2 weeks now and it's been great. However I noticed a huge security flaw today that I hit only once. I access Samba4 shares over the VPN that is irrelevant since the security access is user-based, not IP based. What happens right after the connection, Windows tries to read the shares and some are empty, but they are not supposed to
2018 Dec 23
2
After upgrade to 4.9.4, internal DNS no longer working
...39; not found (required by /usr/lib/libsamba-util.so.0) [2018/12/22 19:13:45.004497, 0] ../source4/dsdb/kcc/kcc_periodic.c:693(samba_kcc_done) ../source4/dsdb/kcc/kcc_periodic.c:693: Failed samba_kcc - NT_STATUS_ACCESS_DENIED [2018/12/22 19:31:48.283948, 0] ../source4/smbd/process_standard.c:86(sigterm_signal_handler) Exiting pid 391 on SIGTERM [... error above repeats about 10 times ...] [2018/12/22 19:31:48.446449, 0] ../source4/smbd/server.c:131(sig_term) SIGTERM: killing children [2018/12/22 19:31:48.447387, 0] ../source4/smbd/server.c:131(sig_term) SIGTERM: killing children [20...
2005 May 03
5
[Bug 1029] SIGTERM and cleanup of wtmp files
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 Reporte...
2018 Dec 26
0
After upgrade to 4.9.4, internal DNS no longer working
...r/lib/libsamba-util.so.0) > [2018/12/22 19:13:45.004497, 0] > ../source4/dsdb/kcc/kcc_periodic.c:693(samba_kcc_done) > ../source4/dsdb/kcc/kcc_periodic.c:693: Failed samba_kcc - > NT_STATUS_ACCESS_DENIED > [2018/12/22 19:31:48.283948, 0] > ../source4/smbd/process_standard.c:86(sigterm_signal_handler) > Exiting pid 391 on SIGTERM > > [... error above repeats about 10 times ...] > > [2018/12/22 19:31:48.446449, 0] ../source4/smbd/server.c:131(sig_term) > SIGTERM: killing children > [2018/12/22 19:31:48.447387, 0] ../source4/smbd/server.c:131(sig_term...
2015 Apr 17
2
Joining 2008 R2 to Samba4 AD DC
We have a Samba4 AD DC running on an Ubuntu 14.04 VM [ smb.conf ] # Global parameters [global] workgroup = MEADORANDCO realm = meadorandco.com netbios name = SOGO server role = active directory domain controller dns forwarder = 192.168.121.1 idmap_ldb:use rfc2307 = yes passdb backend = samba allow dns updates = nonsecure
2018 Mar 20
4
rsync time machine backup permissions
...10209" failed: Operation not permitted (1) rsync: recv_generator: mkdir "/Volumes/G-DRIVE Thunderbolt 3/Backups.backupdb/André Althoffs iMac/2016-04-11-130912" failed: Operation not permitted (1) *** Skipping any contents from this failed directory *** ^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(700) [sender=3.1.3] rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(504) [generator=3.1.3] iMac:~ andre$ mount /dev/disk0s2 on / (hfs, local, journaled) devfs on /dev (devfs, local, nobrowse) map -hosts on /net (autofs, nosuid, automounted, nobrows...
2001 Jun 22
1
PATCH: pidfile/sigterm race
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 @@ -857,6 +857,1...
2012 May 31
5
[Bug 8967] New: rsync returns with non-zero exit code when killed by SIGTERM
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 ReportedBy: mus.svz at gmail.com QAContact:...
2007 Oct 02
3
[PATCH] SIGTERM and SIGINT handler to flush xentop -b outputs
# 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 xentop outputs without this patch. Signed-off-by: INAKOSHI Hiroya <inakoshi.hiroya@jp.fujitsu.com> diff -r 83239b289072 -r 5543e7477...
2018 Jan 23
8
Sending Signal to remote process
I want ssh to forward the SIGTERM signal to the remote command. Example: ssh root at localhost /root/print-signal.py Get PID of ssh: ps aux| grep print-signal Kill the matching ssh process: kill pid-of-ssh Unfortunately only the ssh process itself gets the signal, not the remote command (print-signal.py). The...
2015 Apr 08
4
SIGTERM signal to qemu-kvm process
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
2018 Mar 20
0
rsync time machine backup permissions
...led: Operation not permitted (1) > rsync: recv_generator: mkdir "/Volumes/G-DRIVE Thunderbolt 3/Backups.backupdb/André Althoffs iMac/2016-04-11-130912" failed: Operation not permitted (1) > *** Skipping any contents from this failed directory *** > ^Crsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(700) [sender=3.1.3] > rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(504) [generator=3.1.3] > iMac:~ andre$ mount > /dev/disk0s2 on / (hfs, local, journaled) > devfs on /dev (devfs, local, nobrowse) > map -hosts on /net (autofs, nos...
2018 Dec 23
2
After upgrade to 4.9.4, internal DNS no longer working
I was too quick to send my previous email. It can't really be a problem of the package since I have, as mentioned, another system with the exact same setup and the exact same package versions and it all works there... On Sun, 23 Dec 2018 at 11:18, Viktor Trojanovic <viktor at troja.ch> wrote: > Yes, I tried running dbcheck (see first email), it showed 0 errors from > the start, I