On 7/17/20 9:33 AM, Michael Davidsaver wrote:
> The python subprocess module shouldn't let this happen though since it does
> fork() and then execv(), and the situation which I describe is only possible
> if fork() is not followed by execv().
Oh wait. CAProcess (which I've not seen previously) is using
the multiprocessing module, which can do fork() without exec().
In fact, this is the default on *NIX. So this is likely or
problem. I think you'll need to use the 'spawn' or 'forkserver'
method.
https://docs.python.org/3.7/library/multiprocessing.html#contexts-and-start-methods
https://github.com/pyepics/pyepics/blob/1f795c647458435cca0cf11b984b34fc11180c25/epics/multiproc.py
- Replies:
- Re: Pure Python IOC (CAProcess issue) Matt Newville via Tech-talk
- Re: Pure Python IOC (CAProcess issue) Simon Reiter via Tech-talk
- References:
- Pure Python IOC (CAProcess issue) Simon Reiter via Tech-talk
- Re: Pure Python IOC (CAProcess issue) Michael Davidsaver via Tech-talk
- Re: Pure Python IOC (CAProcess issue) Michael Davidsaver via Tech-talk
- Navigate by Date:
- Prev:
Re: Pure Python IOC (CAProcess issue) Michael Davidsaver via Tech-talk
- Next:
Re: Pure Python IOC (CAProcess issue) Matt Newville via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
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: Pure Python IOC (CAProcess issue) Michael Davidsaver via Tech-talk
- Next:
Re: Pure Python IOC (CAProcess issue) Matt Newville via Tech-talk
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
<2020>
2021
2022
2023
2024
|