Experimental Physics and
Industrial Control System

Hi,

just posting a note on an issue we have come across in case it is helpful to anybody else. We are using Cygwin procServ on Windows to start IOCs (Windows 7 / EPICS BASE 3.14.12.2) and, although stdout was appearing when we typed commands in the telnet window, stderr was not. When the IOC exited, however, the stderr output appeared so it seems that stderr was being buffered. I added the line:

    setvbuf (stderr, NULL, _IONBF, BUFSIZ);

to the IOC main and stderr output then appeared as expected - I think stdout was appearing OK as epicsReadline() does a flush(stdout) after writing the prompt. A "google" on the subject returned some references to this sort of behaviour when the Windows runtime does not recognize the connection as a "terminal" - running the IOC directly in a console windows certainly work OK

Regards,

Freddie

-- 
Scanned by iCritical.

Replies:

Re: stdout/stderr buffering on Windows Andrew Johnson

Navigate by Date:

Prev: RE: DLS EtherCAT scanner and unmatched datagrams [SEC=UNCLASSIFIED] ronaldo.mercado

Next: Re: stdout/stderr buffering on Windows Andrew Johnson

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: aSub and "user defined structures" ? Andrew Johnson

Next: Re: stdout/stderr buffering on Windows Andrew Johnson

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