Experimental Physics and Industrial Control System
Till,
Completely agree with your assessment of the situation, and your fix. In my
defense, what actually occurs when one calls exit() has been evolving quite
a bit with each new release of R3.14.
Jeff
-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Till Straumann
Sent: Sunday, June 10, 2007 1:38 PM
To: TECHTALK tech-talk
Subject: CA client on unix bug
I found the following problem (tested on
linux, solaris, base-3.14.9, base-3.14.8.2)
with the CA client on unix:
Scenario:
IF
- no caRepeater is running
- CA client tries to fork a caRepeater
but the 'exec' syscall fails (e.g., because the
caRepeater is not found in PATH)
THEN
the forked process may end up blocking
for an event that never happens and hence
may never exit (see attached test program for
more details) and therefore never release system
resources.
FIX: libCom/osi/os/posix/osdProcess.c:osiSpawnDetachedProcess()
should call _exit() rather than exit() if execle() fails.
REPRODUCE: try attached code (comments contain analysis
of the problem).
-- Till
- References:
- CA client on unix bug Till Straumann
- Navigate by Date:
- Prev:
Re: CA client on unix bug Andrew Johnson
- Next:
RE: CA client on unix bug Jeff Hill
- 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: CA client on unix bug Jeff Hill
- Next:
GigE Vision-compliant cameras Malitsky, Nikolay D
- 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