On Thursday 17 November 2005 18:47, Jeff Hill wrote:
> > PS: I see these two messages now whenever a client attaches to a
> > Linux
>
> IOC.
>
> > epicsThreadSetPriority called by non epics thread
> > epicsThreadSetPriority called by non epics thread
The following is probably completely unrelated, but the double message
above reminded me that I wanted to report this. It appears (at least)
with a soft ioc under R3.14.7 on a linux-x86 machine. For the purpose
of testing the ioc log I wanted to provoke some arbitrary error
message. To do so, I did:
ben@linux: .../projects/iocLogServer > caput franksenHost:aiExample.TIME
1
Channel connect timed out: 'franksenHost:aiExample.TIME' not found.
Old : New : ben@linux: .../projects/iocLogServer >
On the IOC (example app) this gives me:
epics> franksenHost:aiExample.TIME dbNameToAddr failed
franksenHost:aiExample.TIME dbNameToAddr failed
franksenHost:aiExample.TIME dbNameToAddr failed
franksenHost:aiExample.TIME dbNameToAddr failed
franksenHost:aiExample.TIME dbNameToAddr failed
Ben
- Replies:
- Re: multiple error messages Andrew Johnson
- References:
- RE: dbEvent.c line 665 Jeff Hill
- Navigate by Date:
- Prev:
posix thread priorities Jeff Hill
- Next:
Re: multiple error messages 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: epicsThreadSetPriority called by non epics thread Ernest L. Williams Jr.
- Next:
Re: multiple error messages 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
|