Hi,
We have the same issue that Mark described, in that we're using procServ along with conserver to log from our IOCs. I agree that filtering should be part of any log server. But I think there's a place for it in clients too. For example, we already do rate limiting of alarms from records using things like hysteresis fields.
Yes, Asyn itself probably isn't the best place for it though.
Cheers,
Matt
________________________________________
From: [email protected] [[email protected]] on behalf of Eric Norum [[email protected]]
Sent: 17 April 2012 16:39
To: [email protected] Talk
Subject: Re: log message filter in Asyn
On Apr 17, 2012, at 8:26 AM, Mark Rivers wrote:
> You can also turn off asynTrace messages for a particular device with
>
> asynSetTraceMask(port, addr, 0)
>
> But I see the utility of what Matt is proposing. We use procServ to run our IOCs, both soft IOCs and vxWorks IOCs. On vxWorks the procServ is controlling a telnet session to an Ethernet terminal server, which is connected to the vxWorks console port. For logging we just use the log file capability of procServ, not a special logging program. If a device becomes unavailable the log file can quickly grow very large with asynTrace error messages.
>
> Of course we could manually set the asynTrace mask to 0, as shown above. But it would be nice to have the capability that Matt proposes, to automatically reduce the number of messages in the log file if they are all just repeats.
Agreed, but I'm holding to my opinion that this capability belongs in the log server, not in all the log clients. It certainly does not belong in the ASYN layer. In the errlogPrintf layer, perhaps, but really this belongs in the log server.
--
Eric Norum
[email protected]
--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
- Replies:
- Re: log message filter in Asyn Ralph Lange
- References:
- log message filter in Asyn matthew.pearson
- Re: log message filter in Asyn Andrew Johnson
- RE: log message filter in Asyn Mark Rivers
- Re: log message filter in Asyn Eric Norum
- Navigate by Date:
- Prev:
Re: Channel Access problem over SSH Andrew Johnson
- Next:
RE: Channel Access problem over SSH Hill, Jeffrey O
- 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: log message filter in Asyn nick.rees
- Next:
Re: log message filter in Asyn Ralph Lange
- 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
|