Skip to content

Do not spam OK-emails when running as a cron-job.#17

Open
DanielGeerts wants to merge 1 commit into
CESNET:masterfrom
DanielGeerts:master
Open

Do not spam OK-emails when running as a cron-job.#17
DanielGeerts wants to merge 1 commit into
CESNET:masterfrom
DanielGeerts:master

Conversation

@DanielGeerts

Copy link
Copy Markdown

When running pakiti-client as a cron-job with email notification set-up, every OK-reply from the server would be printed to STDOUT, leading to an email for every single run and for every single machine. This is quite spammy.

This pull requests silences the STDOUT-printing if:
(a) STDOUT is not connected to a terminal. This is the case for cron-jobs. This check means that when running pakiti-client from a terminal, the printing behavior is unchanged, and the user gets feedback that the report was successfully received.
AND
(b) if the response from the server is NOT exactly "OK" (give or take trailing line-feeds). This check makes sure that if the server returns a warning followed by an OK, or any output without an OK, it is still printed, and thus cron will still report it.

People may be using these emails to verify that the pakiti-client cron-job ran. This can still be done on the pakiti-server. In fact, there's automatic highlighting build into its web-interface it specifically for that purpose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant