- **status**: accepted --> invalid
- **Comment**:
I was wrong when interpreting the code line for log filter.
Actually, in log AIS (A.02.01 - 3.4.2.2), there are 2 terms about filter.
1. Severity value – SaLogSeverityT
- Has value in range [0 – 6]
- Is used when writing log record
2. Severity bitmap – SaLogSeverityFlagsT
- Has value in range [1 – 127], seven bits [0 -7].
- Logsv will allow writing log whenever bit position [0 – 6] which
represents ‘severity value’ is set.
E.g: Severity bitmap = 5 (0’b101), logsv only allow `emergency` and `critical`
log record.
- saLogStreamSeverityFilter attribute shows `severity bitmap`. (not
`Severity value`)
---
** [tickets:#1397] logsv: Log filtering does not work correctly**
**Status:** invalid
**Milestone:** 5.0
**Created:** Mon Jun 29, 2015 09:20 AM UTC by Vu Minh Nguyen
**Last Updated:** Wed Jul 15, 2015 12:56 PM UTC
**Owner:** Vu Minh Nguyen
When setting saLogStreamSeverityFilter attribute to other value (other than
127),
the logsv will discard all even the log record is matched with the filter.
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
