aboutgitcodebugslistschat
path: root/tap.c
diff options
context:
space:
mode:
authorStefano Brivio <sbrivio@redhat.com>2024-06-14 19:00:27 +0200
committerStefano Brivio <sbrivio@redhat.com>2024-06-21 15:32:31 +0200
commit8c2f24a5604ad908d6d65b64bf7675e04e2d7277 (patch)
tree69138860d6e3d34be8b7bb0f61c13554fdccf94e /tap.c
parentbca0fefa32e083ab46a49989f225ec34e7cdbb8c (diff)
downloadpasst-8c2f24a5604ad908d6d65b64bf7675e04e2d7277.tar
passt-8c2f24a5604ad908d6d65b64bf7675e04e2d7277.tar.gz
passt-8c2f24a5604ad908d6d65b64bf7675e04e2d7277.tar.bz2
passt-8c2f24a5604ad908d6d65b64bf7675e04e2d7277.tar.lz
passt-8c2f24a5604ad908d6d65b64bf7675e04e2d7277.tar.xz
passt-8c2f24a5604ad908d6d65b64bf7675e04e2d7277.tar.zst
passt-8c2f24a5604ad908d6d65b64bf7675e04e2d7277.zip
conf, log: Instead of abusing log levels, add log_conf_parsed flag
We currently use a LOG_EMERG log mask to represent the fact that we don't know yet what the mask resulting from configuration should be, before the command line is parsed. However, we have the necessity of representing another phase as well, that is, configuration is parsed but we didn't daemonise yet, or we're not ready for operation yet. The next patch will add that notion explicitly. Mapping these cases to further log levels isn't really practical. Introduce boolean log flags to represent them, instead of abusing log priorities. Signed-off-by: Stefano Brivio <sbrivio@redhat.com> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'tap.c')
0 files changed, 0 insertions, 0 deletions