This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH v2] PR23891: Make sure stap and staprun respond to SIGTERM when stderr/stdout are blocked

From: Yichun Zhang <yichun at openresty dot com>
To: systemtap at sourceware dot org
Date: Fri, 23 Nov 2018 16:13:44 -0800
Subject: Re: [PATCH v2] PR23891: Make sure stap and staprun respond to SIGTERM when stderr/stdout are blocked
References: <20181122071643.66485-1-yichun@openresty.com> <20181123220647.30966-1-yichun@openresty.com>

Hello!

On Fri, Nov 23, 2018 at 3:02 PM Yichun Zhang (agentzh) wrote:
>
> When stderr/stdout are blocked (the write buffers are full), write()
> syscalls in stap's signal handler and staprun's stp_main_loop() might
> prevent these processes from responding to signals like SIGTERM.
>

Committed.

Best,
Yichun

References:
- [PATCH] PR23891: Make sure stap and staprun respond to SIGTERM when stderr/stdout are blocked
  - From: Yichun Zhang (agentzh)
- [PATCH v2] PR23891: Make sure stap and staprun respond to SIGTERM when stderr/stdout are blocked
  - From: Yichun Zhang (agentzh)

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]