Experimental Physics and Industrial Control System
Hello
I noticed that the commands 'date' as well as 'epicsTimeShow' seem to
produce garbage, at least in our current setup which is:
* EPICS 3.14.8.2
* Motorola mv2100 (ppc603)
* VxWorks 5.4.2 (Tornado-2.0.2)
We have installed drvTS (from module apsEvent; default configuration,
i.e. no hardware event support) and /do/ get correct timestamps in the
records:
aragon: .../MLS-Controls/work > camonitor POP5C:rdbk
POP5C:rdbk 2007-01-11 11:01:59.551278 0.503876
POP5C:rdbk 2007-01-11 11:02:00.351295 0.503829
POP5C:rdbk 2007-01-11 11:02:00.751304 0.503876
....
However,
iocTESTIOC1C> date
2038/01/19 04:14:08.108797
iocTESTIOC1C> epicsTimeShow
epicsTime: THU JUL 17 2098 16:58:11.426730067
Has anyone observed this or something similar before? Is there some
initialization we forgot?
BTW, we have set the timezone stuff like this (Berlin):
putenv "TIMEZONE=MET::-60:033102:102702"
putenv "EPICS_TS_MIN_WEST=-60"
Cheers
Ben
--
Mutable state is actually another form of manual memory management:
every time you over-write a value you are making a decision that the old
value is now garbage, regardless of what other part of the program might
have been using it. (Paul Johnson)
- Navigate by Date:
- Prev:
string and array buffering in soft IOCs Kurt Biery
- Next:
RE: string and array buffering in soft IOCs Jeff Hill
- 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: string and array buffering in soft IOCs Jeff Hill
- Next:
CA on cygwin port is slower than native windows port Jeff Hill
- Index:
2002
2003
2004
2005
2006
<2007>
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024