EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: errlogPrintf from iocsh for soft IOCs?
From: Eric Norum <[email protected]>
To: "Allison, Stephanie" <[email protected]>
Cc: [email protected]
Date: Tue, 24 Feb 2009 11:06:25 -0600
Minor point of order.
The IOC shell does print the expanded macros when it executes commands from a script. Thus I don't really see the point of having two flavours ('console' and 'no-console') of command. The command prints before the IOC shell executes it so it will always be on the console.
So, my vote is for
	errlogMessage
or perhaps
	errlogEcho
only.
The command could take multiple arguments (like the unix 'echo' command -- hence my latter suggestion for the command name).


On Feb 24, 2009, at 10:49 AM, Allison, Stephanie wrote:

Hi Andrew,

Is there a way to send a message to errlog (via errlogPrintf without
arguments) by a user at the iocsh prompt? This can be done already at the Cexp prompt for RTEMS iocs - it would be nice to have similar functionality for soft iocs. I notice that errlogInit is registered at the iocsh but not errlogPrintf (or something that calls of errlogPrintf). Could this be added to base/src/libCom/iocsh/libComRegister.c? Otherwise, I'll add it to
devIocStats.

I think that's a quite reasonable thing to add to Base. The only question I
have is should it call errlogPrintf() or
errlogPrintfNoConsole()?  My guess
is the latter since the command should be printed out as it is being
executed, but admittedly that won't include the expanded value of any macros used in the message string. I guess it wouldn't be hard to provide both
options though.

Since we don't allow the "printf" arguments, to prevent someone from adding arguments thinking they'll be used, it's probably best to call these:
errlogMessage
and
errlogMessageNoConsole

We could provide just one routine "errlogMessage" with a second optional argument with the console/noconsole flag though that doesn't match the real errlogMessage prototype and could cause confusion. (Though maybe we could also change the errlogMessage function to add a second argument?). Maybe providing both is best even though it adds to the proliferation of registered functions.

Thanks,
Stephanie


--
Eric Norum <[email protected]>
Advanced Photon Source
Argonne National Laboratory
(630) 252-4793



References:
errlogPrintf from iocsh for soft IOCs? Allison, Stephanie
Re: errlogPrintf from iocsh for soft IOCs? Andrew Johnson
RE: errlogPrintf from iocsh for soft IOCs? Allison, Stephanie

Navigate by Date:
Prev: RE: errlogPrintf from iocsh for soft IOCs? Allison, Stephanie
Next: Re: soft device for ai record works as sscanf. Dirk Zimoch
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: RE: errlogPrintf from iocsh for soft IOCs? Allison, Stephanie
Next: soft device for ai record works as sscanf. Noboru Yamamoto
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  <20092010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 31 Jan 2014 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·