Sorry folks for introducing a VxWorks query, but after two weeks of
frustration trying to make the EPICS log server work I have returned
to simple file i/o (fopen, fprintf, etc) on an mv167 IOC running
VxWorks 5.2. It would be useful to be able to examine the output on
the fly but no file ever appears until fclose is called. fflush does
not do the business. In general our applications never exit - they
simply run and run until a reboot, so there is never a time when
fclose should be called. One clumsy attempt at a solution was to
fopen the host file with "w+" access and to close it periodically and
reopen it with "a+" access. Now this works fine under Unix, and
should do on the mv167 according to the VxWorks manual, but in fact
VxWorks complains that the file already exists, which it must.
Does anybody know what is going on? Is our VxWorks broken or what?
Len
==============================================================================
Len Lawrence Tel. : +44 (0)131 668 8255 (direct)
Royal Observatory +44 (0)131 668 8100 (switchboard)
Blackford Hill [email protected]
Edinburgh EH9 3HJ aka [email protected]
UK WWW : http://www.roe.ac.uk/lclwww/
- Replies:
- Re: VxWorks file i/o problem Philip Taylor
- Re: VxWorks file i/o problem Jeff Hill
- Navigate by Date:
- Prev:
Re: Problems with Alh & Channel Access (R3.13.0b4). Nick Patavalis
- Next:
Re: VxWorks file i/o problem Philip Taylor
- 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: MVME177 and vxWorks John R. Winans
- Next:
Re: VxWorks file i/o problem Philip Taylor
- 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
|