Oracle ERP DBA

CODE Copy the below code snippet: ------------------------- COPY FROM BELOW ------------------------- <pre style="background-color: #eeeeee; border: 1px dashed rgb(153, 153, 153); color: black; font-family: Andale Mono, Lucida Console, Monaco, fixed, monospace; font-size: 12px; line-height: 14px; overflow: auto; padding: 5px; width: 100%; white-space: pre-wrap;"> <code style="color: black; overflow-wrap: normal; word-wrap: normal;"> INPUT YOUR CODE HERE (SHELL, PYTHON, JAVA etc.,) </code></pre> ------------------------- END OF COPY ------------------------- Shell Command (bash) example: $ sendEmail -t "&lt;TO_EMAIL&gt;" -f "&lt;FROM&gt;" -u "&lt;SUBJECT&gt;" [-cc "&lt;EMAIL_IN_CC&gt;" -bcc "&lt;EMAIL_IN_BCC&gt;"] -o message-content-type=html -o message-file="&lt;INPUT_FILE_NAME&gt;" -a "&lt;FILE_TO_BE_ATTACHED&gt;"

After any automation or scripting task is complete, I am sure some of them would need to email the output or alert to your mailbox. Linux does provide a few basic tools/utilities to cater to that requirement such as mailx or sendmail. However, their capabilities are limited to sending emails in text. But the need of the hour, if I may say so, is to have formatted emails with tables, highlighting and underlining words, attachments, the whole shebang! In other words, emails should be sent in HTML format which can have all these features and much more.  Though there are methods available to send emails using sendmail or mailx (using uuencode etc.,) they are quite cumbersome and convoluted. That's where "sendemail" utility comes in. It can send html emails so easily and with attachments as well. The software is described as "a lightweight tool written in Perl for sending SMTP email from the console". Some flavours of Linux provide it as a package (like Ubuntu, Kali

Ansible does provide a wonderful option to execute a module or command in only one host called run_once but the results and facts are applied to all the hosts involved in the play. See definition and working :     This blog has good information on how it can be used to in various scenarios.  However, I don't want to talk about how it can be used and how its working (well, the blog calls it magic 😄) is quite useful. Rather, I want to share an interesting anomaly of run_once, when used in conjunction with either include_roles or include_tasks.   My scenario is quite simple: set_fact with run_once: My playbook: $ cat run_once_set_fact.yml --- - hosts: all gather_facts: False tasks: - name: Set fact fact1 set_fact: fact1: "DUMMY" run_once: True - debug: msg: "fact1: {{ fact1 }}" Output: PLAY [all] *******************************************************************************************