| 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 2025 | Index | 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: Weird CAS hangup on IOC |
| From: | Torsten Bögershausen via Core-talk <core-talk at aps.anl.gov> |
| To: | Ralph Lange <ralph.lange at gmx.de>, EPICS Core Talk <core-talk at aps.anl.gov> |
| Date: | Fri, 7 Feb 2020 15:22:34 +0000 |
|
From: Core-talk <core-talk-bounces at aps.anl.gov> on behalf of Ralph Lange via Core-talk <core-talk at aps.anl.gov> >Fair starting point, yes. Sounds like a nice codeathon project for next week, actually.
> would probably restrict the re-looping to the case of listen() failing because of EADDRINUSE - > don't want to get into infinite loops on other unrelated errors. Yes, >Maybe the listen() now happening in the spawned-off receive thread will have to be moved over... Yes. > Does calling listen() twice work?
Does it do any harm? No - yes. I think this is what happens today - 2 processes listen to the same socket. There can only be one, so the second one failes, right. https://bugs.launchpad.net/epics-base/+bug/1862328 Cheers, ~Ralph
|