>>In addition it would help if any write action to the IOC's could be logged on a
>>file. This would help to keep track and analyse problems. This would need an
>>output channel from the CA-server on the IOC to a (i.e.) NFS-mounted disk.
>>The output would look like:
>>date time user@machine changed record from value to value
>
>This must of been discussed in the past. Sorry if this is a rehash.
Yes, this is something I asked about 2 years ago -- a "write hook" to catch all
external writes to the database (which would catch all operator changes). But I
prefer to do server side logging so that poorly behaved clients can't interfere
with the data integrity. As to the knobbing problem, it is simple enough to
implement something to collapse repeated writes to the same channel into a
single log output. (see also: previous discussions of err logging and filtering
repeating error messages).
Chip
- References:
- Logging of Write Actions 415
- Navigate by Date:
- Prev:
Logging of Write Actions 415
- Next:
dm display arguments declaration Jeff Hill
- 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:
Logging of Write Actions 415
- Next:
dm display arguments declaration Jeff Hill
- 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
|