EPICS Home

Experimental Physics and Industrial Control System


 
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  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 
<== Date ==> <== Thread ==>
Subject: Arbitrary limit on timeouts?
From: Eric Norum <[email protected]>
To: Andrew Johnson <[email protected]>, EPICS mailing list <[email protected]>
Date: Wed, 7 Jun 2017 09:50:34 -0700
Why are timeouts for things like epicsEventWaitWithTImeout() limited to 1 hour?
This is for R3.15.4, but I suspect the code is the same in lots of versions.

The code that applies the limit is in src/libCom/osi/os/posix/osdTime.cpp:
extern "C" epicsShareFunc void
    convertDoubleToWakeTime(double timeout,struct timespec *wakeTime)
{
    struct timespec wait;
    int status;

    if(timeout<0.0) timeout = 0.0;
    else if(timeout>3600.0) timeout = 3600.0;
#ifdef CLOCK_REALTIME
    status = clock_gettime(CLOCK_REALTIME, wakeTime);
#else
    {
. . .



-- 
Eric Norum
[email protected]

Replies:
Re: Arbitrary limit on timeouts? Michael Davidsaver
Navigate by Date:
Prev: Re: double crystal monochromator Mooney, Tim M.
Next: Re: Arbitrary limit on timeouts? Michael Davidsaver
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: double crystal monochromator Mooney, Tim M.
Next: Re: Arbitrary limit on timeouts? Michael Davidsaver
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