Ben,
I did think of one issue. This is using non blocking IO after the connect
completes. It appears that a delta is that the logRestart thread is now
doing the periodic flush for *multiple* logging circuits. Therefore, if one
of the log circuits isnt flowing for whatever reason (disk full, marginal
circuit, server system power off, etc), then all of the other log circuits
will not be flushed untill logClientSend is called and the specified message
will not fit (the buffers capacity is exceeded). Since the internal IP
kernel timeouts for circuit disconnect can be quite long this might prove to
be problematic.
Jeff
> -----Original Message-----
> From: Benjamin Franksen [mailto:[email protected]]
> Sent: Wednesday, November 16, 2005 10:17 AM
> To: [email protected]
> Subject: Re: R3.14.8 Status/logClient patch
>
>
> On Wednesday 16 November 2005 14:03, Benjamin Franksen wrote:
> > What should I do?
>
> Ok, problem solved. Everything is completely backward compatible now.
> See release notes snippet for details. The relevant section for the
> AppDevGuide is not yet done (it didn't contain anything until now).
> BTW, what is the source format for that, or is plain text ok?
>
> Ben
>
> PS: Attached tar file can be unpacked inside
> /path/to/base/src/libCom.
> It contains a patched Makefile and a snippet for the release notes.
>
- Replies:
- Re: R3.14.8 Status/logClient patch Benjamin Franksen
- Re: R3.14.8 Status/logClient patch Benjamin Franksen
- References:
- Re: R3.14.8 Status/logClient patch Benjamin Franksen
- Navigate by Date:
- Prev:
epicsAtExit Marty Kraimer
- Next:
Re: epicsAtExit Andrew Johnson
- 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: R3.14.8 Status/logClient patch Benjamin Franksen
- Next:
Re: R3.14.8 Status/logClient patch Benjamin Franksen
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|