Experimental Physics and
Industrial Control System

On 6/19/19 9:00 AM, Michael Davidsaver wrote:
> On 6/19/19 8:29 AM, Ralph Lange via Core-talk wrote:
>> Question:
>> It seems (looking at start_routine() in libCom/osi/osd/posix/osdThread.c) that all threads that the IOC starts are blocking all signals.
>> Is that correct, or am I missing something?
>> If that's correct, why is it done?
>>
>> We have a case where a separate process started from an EPICS IOC subordinate (driver) thread - via fork() and execv() calls - seems to be "immune" against all attempts to kill it (except -9 obviously).
>>
>> Any ideas?
> 
> SIGKILL can't be blocked.  Maybe a "zombie" process
> which it's parent isn't wait()ing for it?

Forget this.  I was reading so fast that I missed "expect".

Attachment: signature.asc
Description: OpenPGP digital signature

References:

IOC Threads blocking all signals Ralph Lange via Core-talk

Re: IOC Threads blocking all signals Michael Davidsaver via Core-talk

Navigate by Date:

Prev: Re: IOC Threads blocking all signals Michael Davidsaver via Core-talk

Next: Re: [Merge] ~epics-core/epics-base/+git/Com:thread-join into epics-base:7.0 Andrew Johnson via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <2019>  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: Re: IOC Threads blocking all signals Michael Davidsaver via Core-talk

Next: Re: IOC Threads blocking all signals William Norum via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  <2019>  2020  2021  2022  2023  2024