search for: sigquit

On Thu, 29 Dec 2022, Philippe Cerfon wrote: > Hey. > > On Thu, Dec 29, 2022 at 1:28 AM Damien Miller <djm at mindrot.org> wrote: > > It's because the monitor process doesn't explicitly handle SIGQUIT. > > Are you going to merge the patch of yours? Does it solve your problem? -d

Hey. I've noticed the following behavior and wondered whether it's possibly a bug or why it behaves like this: When having a SSH connection, than it seems there may be two sshd processes for that, one running as root the other as the user. As far as I know this is because of privilege separation, like e.g.: ??sshd(2931)???sshd(10174)???bash(10180) ?

Hey. On Thu, Dec 29, 2022 at 1:28 AM Damien Miller <djm at mindrot.org> wrote: > It's because the monitor process doesn't explicitly handle SIGQUIT. Are you going to merge the patch of yours? Best wishes, Philippe.

...3.11.0 and LibVEX; rerun with -h for copyright info ==979== Command: /usr/lib/R/bin/exec/R --vanilla --quiet ==979== > 1+2 [1] 3 # At next prompt I press Ctrl-\. The same happens also when done in the middle of an entry. > ==979== ==979== Process terminating with default action of signal 3 (SIGQUIT) ==979== at 0x576C9C3: __select_nocancel (syscall-template.S:84) ==979== by 0x502EABE: R_SelectEx (in /usr/lib/R/lib/libR.so) ==979== by 0x502EDDF: R_checkActivityEx (in /usr/lib/R/lib/libR.so) ==979== by 0x502F32B: ??? (in /usr/lib/R/lib/libR.so) ==979== by 0x4F6988B: Rf_ReplIterati...

Thanks for these explanations - it all makes sense, that is, the default behavior for a process that does not capture SIGQUIT is to quit and perform a core dump (https://en.wikipedia.org/wiki/Unix_signal#SIGQUIT). Then the remaining question, as Luke says, is: should R handle this signal? For instance, in interactive mode, SIGQUIT could maybe bring up: Possible actions: 1: abort (with core dump, if enabled) 2: normal R...

Handle SIGQUIT by guestfish, so that it can't be terminated. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- fish/fish.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/fish/fish.c b/fish/fish.c index efd6b0b..b782b7c 100644 --- a/fish/fish.c +++ b/fish/fish.c @@...

We''re using unicornctl restart with the default before/after hook behavior, which is to reap old Unicorn workers via SIGQUIT after the new one has finished booting. Unfortunately, while the new workers are forking and begin processing requests, we''re still seeing significant spikes in our haproxy request queue. It seems as if after we restart, the unwarmed workers get swamped by the incoming requests. As far as...

...rieving revision 1.104 diff -u -r1.104 clientloop.c --- clientloop.c 22 Aug 2002 19:38:42 -0000 1.104 +++ clientloop.c 18 Nov 2002 11:33:45 -0000 @@ -888,10 +888,16 @@ client_init_dispatch(); - /* Set signal handlers to restore non-blocking mode. */ - signal(SIGINT, signal_handler); - signal(SIGQUIT, signal_handler); - signal(SIGTERM, signal_handler); + /* + * Set signal handlers, (e.g. to restore non-blocking mode) + * but don't overwrite SIG_IGN, matches behaviour from rsh(1) + */ + if (signal(SIGINT, SIG_IGN) != SIG_IGN) + signal(SIGINT, signal_handler); + if (signal(SIGQUIT, SIG_IG...

On command: #kill -9 `cat /var/run/sshd.pid` sshd leave pid file ! sshd.c code: =============== .... /* * Arrange to restart on SIGHUP. The handler needs * listen_sock. */ signal(SIGHUP, sighup_handler); signal(SIGTERM, sigterm_handler); signal(SIGQUIT, sigterm_handler); .... =============== Missing line is : signal(SIGKILL, sigterm_handler);

Hello, I''m using unicorn since a while, but now I try to run it the first time inside a FreeBSD jail. The initial start of unicorn works fine and it serves all the requests. But if I want to restart it using the USR2 signal, it (more or less) slowly starts using more and more CPU cycles. There is no error message in the logs and it quite hard to reproduce that error. In 1 of 20 tries,

...g herd (especially in the "preload_app false") case. Also comment on the per-worker listen usage in the RDoc, not just a hidden comment. --- I just pushed this out earlier, this example was inspired by Chris Wanstrath''s before_fork hook but modified to use SIGTTOU instead of SIGQUIT for all but the last worker to minimize memory explosions during upgrades. The :tries and :delay options were also inspired by Chris and will be in v0.93.0 which will probably be released. lib/unicorn/configurator.rb | 21 +++++++++++++++++---- 1 files changed, 17 insertions(+), 4 deletions...

...sten_socks) fatal("Cannot bind any address."); + if (options.protocol & SSH_PROTO_1) + generate_ephemeral_server_key(); + + /* Arrange to restart on SIGHUP. The handler needs listen_sock. */ + signal(SIGHUP, sighup_handler); + + signal(SIGTERM, sigterm_handler); + signal(SIGQUIT, sigterm_handler); + + /* Arrange SIGCHLD to be caught. */ + signal(SIGCHLD, main_sigchld_handler); + + /* Write out the pid file after the sigterm handler is setup */ if (!debug_flag) { /* * Record our pid in /var/run/sshd.pid to make it @@ -871,17 +884,6 @@ fclose(f); }...

...| 2 +- src/guestfs.c | 3 +++ 2 files changed, 4 insertions(+), 1 deletions(-) diff --git a/fish/fish.c b/fish/fish.c index 575fe99..fbacbb9 100644 --- a/fish/fish.c +++ b/fish/fish.c @@ -406,7 +406,7 @@ main (int argc, char *argv[]) sigaction (SIGINT, &sa, NULL); sigaction (SIGQUIT, &sa, NULL); - guestfs_set_pgroup (g, 1); + guestfs_set_pgroup (g, 0); } /* Old-style -i syntax? Since -a/-d/-N and -i was disallowed diff --git a/src/guestfs.c b/src/guestfs.c index 3493d79..2ff506b 100644 --- a/src/guestfs.c +++ b/src/guestfs.c @@ -143,6 +143,9 @@ guestfs_cre...

...f syslinux and change the following: * The test in syslxmod.c * Change each time I see SECTOR_SHIFT=9 in SECTOR_SHIFT=11 It's compile fine but when I use syslinux on the key # syslinux /dev/sda1 gives a segfault. An strace gives *** rt_sigaction(SIGINT, {SIG_DFL}, NULL, 8) = 0 rt_sigaction(SIGQUIT, {SIG_DFL}, NULL, 8) = 0 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0 --- SIGCHLD (Child exited) @ 0 (0) --- unlink("/tmp/syslinux-mtools-BIL09s") = 0 pread(3, "\353<\220mkdosfs\0\0\10\10\1\0\2\0\2\0\0\370=\0 \0@\0\0"..., 512, 0) = 512 --- SIGSEGV (Segmentation fault) @ 0 (...

So do a number of other interactive programs when working in a terminal (e.g. python) since it looks like your terminal is configured for those two actions to send the SIGQUIT signal. Whether R should ignore that signal, under some circumstances at least, is another question. Best, luke On Fri, 10 Feb 2017, Henrik Bengtsson wrote: > When running R from the terminal on Linux (Ubuntu 16.04), it core > dumps whenever / wherever I press Ctrl-4 or Ctrl-\. You get t...

...passwords. It's unlikely that these could have been used for practical attacks, especially because Dovecot delays and flushes all failed authentications in 2 second intervals. Also it could have worked only when passwords were stored in plaintext in the passdb. * master process sends SIGQUIT to all running children at shutdown, which instructs them to close all the socket listeners immediately. This way restarting Dovecot should no longer fail due to some processes keeping the listeners open for a long time. + auth: Add passdb { mechanisms=none } to match separate passdb loo...

...passwords. It's unlikely that these could have been used for practical attacks, especially because Dovecot delays and flushes all failed authentications in 2 second intervals. Also it could have worked only when passwords were stored in plaintext in the passdb. * master process sends SIGQUIT to all running children at shutdown, which instructs them to close all the socket listeners immediately. This way restarting Dovecot should no longer fail due to some processes keeping the listeners open for a long time. + auth: Add passdb { mechanisms=none } to match separate passdb loo...

...h a blocking process, the pid that is used by the ?killpg? function is the one of the shell. So it is this shell that catches the signal resulting in it: > - dying and leaving zombies > - dying and taking its child with him (SIGHUP and SIGKILL) > - ignoring the signal (SIGINT, SIGTERM, SIGQUIT). > > Example of ID?s when I connect to a server and launch the script test_signal.sh : > PID PPID PGID SID > 4060 1598 4060 1556 sshd sshd: root at pts/2 > 4062 4060 4062 4062 bash -bash > 4075 4062 4075 4062 sh sh test_signa...

Hi, We''ve just migrated one of our rails applications from nginx/passenger running on REE 1.8.7 Ubuntu 8.04 to unicorn running on MRI 1.9.3 on Ubuntu 10.04. The app makes a number of calls to internal services using curb. Our deployment script stops unicorn by sending SIGQUIT to the unicorn master, sleeps for a few seconds to ensure that HAProxy has taken the node out of service and then starts unicorn again. However, since the migration, we''ve started seeing a few errors on each deploy, when the workers receive the QUIT from the master: ERROR ( XXX) {&quot...

...ek(4, 0, SEEK_CUR) = 0 write(4, "MTOOLS_SKIP_CHECK=1\nMTOOLS_FAT_C"..., 92) = 92 close(4) = 0 munmap(0x7f5949c3c000, 4096) = 0 rt_sigaction(SIGINT, {SIG_IGN, [], SA_RESTORER, 0x7f5949688e50}, {SIG_DFL, [], 0}, 8) = 0 rt_sigaction(SIGQUIT, {SIG_IGN, [], SA_RESTORER, 0x7f5949688e50}, {SIG_DFL, [], 0}, 8) = 0 rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0 clone(child_stack=0, flags=CLONE_PARENT_SETTID|SIGCHLD, parent_tidptr=0x7fffded44270) = 6082 wait4(6082, [{WIFEXITED(s) && WEXITSTATUS(s) == 1}], 0, NULL) = 6082 rt_sigaction(S...