We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I need the XXXsslkey.log file, but it wasn't generated as default. (v3.4.0)
I started the AMF with the following option: ./bin/amf -l log/amf.log
By doing this, the following two files were generated log/amf.log log/key/amfsslkey.log
I find it counterintuitive that log/key/amfsslkey.log is generated with -l log/amf.log. Is this the expected behavior?
I think it would be better to have sslkey.log created by default or to have a more intuitive option for specifying its creation.
The text was updated successfully, but these errors were encountered:
Hello,
By doing this, the following two files were generated log/amf.log log/key/amfsslkey.log Is this the expected behavior?
Yes, it's the current behavior for each NF now.
Thanks for the advice. We would consider refactoring each NF to have a more intuitive way to generate log files.
Sorry, something went wrong.
No branches or pull requests
I need the XXXsslkey.log file, but it wasn't generated as default. (v3.4.0)
I started the AMF with the following option:
./bin/amf -l log/amf.log
By doing this, the following two files were generated
log/amf.log
log/key/amfsslkey.log
I find it counterintuitive that log/key/amfsslkey.log is generated with -l log/amf.log.
Is this the expected behavior?
I think it would be better to have sslkey.log created by default or to have a more intuitive option for specifying its creation.
The text was updated successfully, but these errors were encountered: