On Thursday 17 November 2005 23:06, Andrew Johnson wrote:
> Benjamin Franksen wrote:
> > please re-read my message. I explicitly said I did this to provoke
> > an error message on the IOC console. I merely wondered if this is
> > such a severe error that the IOC must report this five times, when
> > (IMHO) once would have been enough ;-)
>
> My apologies for not completely reading your message, however the IOC
> is merely reporting the error every time it occurs, i.e. once every
> time the CA client retries the name search. Your client gives up
> searching after trying for 1 second, during which time there are 5
> searches. If I ask caget to wait 10 seconds, I get rather more
> messages.
Ah, this makes it perfectly clear. I didn't know that caput tries to
connect to a PV multiple times. Thanks for the explanation.
> Throttling the duplicates not a trivial problem however; it would be
> simple to remove the message completely (see src/db/db_access.c), but
> I can see it being occasionally useful to track down errant clients.
I have no problem with the current behavior. Just didn't know where it
came from and thought there might be something wrong, which obviously
isn't the case.
Ben
- References:
- RE: dbEvent.c line 665 Jeff Hill
- Re: multiple error messages Benjamin Franksen
- Re: multiple error messages Andrew Johnson
- Navigate by Date:
- Prev:
Re: posix thread priorities Ralph Lange
- 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
- Navigate by Thread:
- Prev:
Re: multiple error messages Andrew Johnson
- Next:
Re: [Fwd: R3.14.8 testing: epicsMessageQueueTestHost fails on linux-x86] Marty Kraimer
- Index:
2002
2003
2004
<2005>
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|