-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
stdout/stderr to log #1531
Comments
Lego logs to $ lego ... 2>&1 | tee -a lego.log |
I would like to see the standard behaviour, that errors go to "stderr" and info and related to stdout. You can take advantage to cron with filtered stdout but enabled errors to receive an email with the error message when a error is logged on stderr. My knowledge in go is limited - but it seems new logger instance is needed? |
I support this. Errors are supposed to go to the stderr and stdout is for the rest. for example - this message goes to stderr, but it is expected behavior.
|
Are there any chances to get it implemented? |
I'm not an experienced Go developer, but it seems to work and fixes [go-acme#1531]
Welcome
How do you use lego?
Binary
Detailed Description
I am using the current LEGO port for mips and have now tried with logger and tee to log the bash output for later error analysis in case of problems.
But LEGO doesn't seem to output a classic stdout/stderr and I can't catch the output.
If there is no other way technically, a logging function would be nice :)
The text was updated successfully, but these errors were encountered: