-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: set TSS log level per logging module #49
Comments
Sweet. I'm doing a major re-write at the moment. I'll make sure to get this in there. Thanks! |
We don;t have a log in the rewrite to CFFI yet, but we will add it. |
Nice, I did some preliminary work on this. That includes an (already merged) PR for redirecting logging to a file (which could be a pipe) on TSS side, see tpm2-software/tpm2-tss#1976 |
I don't think this is going to make 1.0 and we need to finalize the tss C code approach. We can't do per-ctx logging because much of the submodules don't have context parameters, like libmu. See: |
Unfortunately, there seems to be no mechanism to set the TSS log level at runtime besides via the env variable
TSS2_LOG
, e.g.TSS2_LOG=all+ERROR,fapi+TRACE
, as documented here. What do you think of having a function setting this variable, maybe from a dict?Example:
We might want to use enums instead of strings(?). In case you wonder, modules and log levels are parsed case insensitive.
Complete list of TSS log levels (as defined here):
Complete list of TSS log modules (grepped):
The text was updated successfully, but these errors were encountered: