Skip to main content

How to uncomment a conf file in Linux via ansible

How to uncomment or enable a setting in a config file in Linux using Ansible?

Ansible is quite a good tool,  as it helps to make a lot of changes on a few servers with a minimal effort.

Of course, the challenge is you need to know what you want. And also create an Ansible yaml file that will accomplish the task.

Example YAML file for Ansible below is able to make some changes on the Linux logrotate.conf file.

On Linux logrotate.conf, it has some text like the string below. Note this is just an example and you can tweak it to other settings as desired.

# uncomment this if you want your log files compressed

#compress

The logrotate.conf file, the compress setting is commented. To enable the setting the # or the comment key must be removed.

How to remove the comment in order to enable the setting?

Well, if there's only a single server do it the simple way. Login to the server and edit the file using vim or nano or other text editor.

However, if there are quite a few servers. Ansible is a better solution to do this task.

Here's the YAML Ansible code snippet that will uncomment or enable the settings for logrotate.conf file.

---

 - name: Uncomment line from /etc/logrotate.conf

  hosts: server.007.locals:server008.locals:server009.locals:server010.locals

  tasks:

          - lineinfile:

              path: /etc/logrotate.conf

              regexp: '^#\s*compress.*$'

              line: 'compress'

              backrefs: yes

The server is defined manually, ideally it should point to an Ansible inventory file. If need to select just a few servers defining the server manually on the Ansible file is okay.

Save the code snippet as "log_change.yml" and if you just want to test without making any changes run:

ansible-playbook log_change.yml --check

--check will simulate what's going to happen or what changes will be done.

So, it's always a good idea to test before rolling out any permanent changes.

The code above is inspired from this StackOverflow post: Replace a line in a config file with ansible - Stack Overflow



Cheers! Take care. Till next Time.

Stay safe! and Keep things up! 

Do ASAP, Always Say A Prayer...

Practice O.T.G. = Obedience To God

Make time for Prayer and Meditation.

================================

Free Android Apps:

Click  links below to find out more:

Free Android Apps:

Click  links below to find out more:

Excel Keyboard guide:

https://play.google.com/store/apps/details?id=chrisjoms.myexcelapplicationguide

Heaven's Dew Fall  Prayer app for Android :

https://play.google.com/store/apps/details?id=soulrefresh.beautiful.prayer

Catholic Rosary Guide  for Android:

Pray the Rosary every day, countless blessings will be showered upon your life if you recite the Rosary faithfully. 

https://play.google.com/store/apps/details?id=com.myrosaryapp

Divine Mercy Chaplet Guide (A Powerful prayer) BFF = Be Filled Faith:

https://play.google.com/store/apps/details?id=com.dmercyapp   

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...
Post a Comment
Read more

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...
Post a Comment
Read more