-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
add env var LOGWATCH_SENDER
#2362
add env var LOGWATCH_SENDER
#2362
Conversation
I've fixed the issue's description because I just noticed that |
What do you mean by "bubble"?
Sure :) |
I mean that the value of a variable will also set another variable if it's not explicitly set otherwise.
Will do. |
Don't forget to adjust |
Isn't it enough that they're set up in |
I think you are right. I find it always confusing, when default vars are defined in two places 😕 |
Very true. I guess the variables in |
Not sure about the failing test. Is it related to my changes? Edit: Interesting... now the failure is gone. 😮 |
Documentation preview for this PR is ready! 🎉 Built with commit: 267c872 |
Sometimes, although not too often, a test is flakey and does not behave well. Restarting the jobs solves these problems. |
Description
Follow-up to #2360, but using
/etc/logwatch/conf/logwatch.conf
as config file.Type of change
This might be considered to be a breaking change if someone relied on the fact that
REPORT_SENDER
wouldn't influence the sender address for logwatch reports. But when I started using this project, I was actually expecting it would.Checklist:
docs/
)