Make more sense of the FT logging capabilities/options
Issue #150
resolved
A more syslog-style level of logging filtering would be appreciated. So moving away from enable/disable on a process basis and allow for critical errors to be always logged.
Comments (4)
-
-
reporter Yes this would be good indeed. Of course it has a dependency on individual application/processes logging at the right priority level (not a given).
Also my point in the post refers to the application logging verbosity which not always can be tweaked and even if so it rarely covers the 8 different levels of priority.
-
Done, added to my PR:
https://bitbucket.org/pedro311/freshtomato-arm/pull-requests/65 -
reporter - changed status to resolved
Resolved with this Pull Request:
https://bitbucket.org/pedro311/freshtomato-arm/pull-requests/65
- Log in to comment
I think we can easily use this function from syslogd:
This will bring us another layer of filtering. Quite interesting that it hasnt been implemented so far.
Just wonder why there are 8 levels of priority?
EDIT:
According to this:
https://sites.uclouvain.be/SystInfo/usr/include/sys/syslog.h.html
IN fact syslog supports up to 8 priority levels, so it is ok