-
Notifications
You must be signed in to change notification settings - Fork 36
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
Redirect mcollective_facts_yaml_refresh cron to /dev/null #208
Labels
Projects
Comments
hanej
added a commit
to hanej/puppet-mcollective
that referenced
this issue
Nov 16, 2018
ripienaar
added a commit
that referenced
this issue
Nov 16, 2018
(#208) Redirect cron output to /dev/null
Thank you @hanej releases should come in the next week or two |
I apologize @ripienaar, the commit I sent you doesn't property redirect stderr. It should either be |
oh yeah I totally missed that doh |
I reopened it - you can send another PR to fix it |
hanej
added a commit
to hanej/puppet-mcollective
that referenced
this issue
Nov 17, 2018
ripienaar
added a commit
that referenced
this issue
Nov 17, 2018
(#208) Properly redirect stderr and stdout
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The mcollective_facts_yaml_refresh cron job is sending emails when the refresh_facts.rb job generates warnings on stderr. The 99% of the time the warnings are environment related and are intermittent so they can be safely ignored.
Pull request #207 opened for this.
The text was updated successfully, but these errors were encountered: