| commit | b217b9b3e597e96c0541c4493f8f4ded28ed7804 | |
| author | Vadim Yanitskiy <axilirator@gmail.com> | |
| Wed, 8 Apr 2020 21:59:20 +0000 (9 04:59 +0700) | ||
| committer | Vadim Yanitskiy <axilirator@gmail.com> | |
| Wed, 8 Apr 2020 22:13:59 +0000 (9 05:13 +0700) | ||
| tree | f98aca5b39b6dfac3962669d778250764e2a03f7 | treesnapshot (tar.gz zip) |
| parent | 75ae23674c3c74bc83361559db0e218432562098 | commitdiff |
trxcon/logging: print category, level and extended timestamp
Since we're heavily using trxcon in ttcn3-bts-test, the logging
output should contain as much information as possible. Ideally
we should introduce the VTY interface (see OS#3666) and get
logging configuration options as a bonus. But let's just use
some beneficial hard-coded defaults for now:
- print category and level (huh, we use NOTICE everywhere?),
- do not print category-hex (who needs it anyway?),
- print extended timestamp, so we're in synce with other logs.
P.S. This configuration is based on my own debugging experience.
Change-Id: Ie3d259f3255d8af80e6780f850b808fa243f97b4
Since we're heavily using trxcon in ttcn3-bts-test, the logging
output should contain as much information as possible. Ideally
we should introduce the VTY interface (see OS#3666) and get
logging configuration options as a bonus. But let's just use
some beneficial hard-coded defaults for now:
- print category and level (huh, we use NOTICE everywhere?),
- do not print category-hex (who needs it anyway?),
- print extended timestamp, so we're in synce with other logs.
P.S. This configuration is based on my own debugging experience.
Change-Id: Ie3d259f3255d8af80e6780f850b808fa243f97b4
| src/host/trxcon/trxcon.c | diffblobblamehistory |