Run playbook with Ansible: (-f switch allow the execution to be performed on multiple hosts parallel)
$ ansible-playbook telnetPlaybook.yaml -f 10
Ansible Modules (-m): These are few but there is huge list.
command – execute commands and this is default module of Ansible.
copy – copy files
shell – use remote shell to execute
file – file operations
ping – ping remote hosts
yum – Redhat package manager
git – use GIT
user – user creation, manipulation
service – manage services
My office environment like many others are providing us Internet via proxy, on Windows Machine/Servers as they are part of domain the policy is pushed and as you login with your domain account you will find it available.
However on Linux servers I always go ahead with doing the following:
And whenever the servers were required to reboot the proxy used to wipe out.
This time I made sure to make it static and plan to push it via Ansible to all the Linux babies I love.
Logged in from root account:
Save the file – Re-initialize the shell or logout and login back. You will not have to re-add it back again.
One of my monitor display was bothering my eyes, therefore I decided to change the colors being displayed on the monitor I am using, especially for the directory as it was dark blue and I had to dig myself inside the screen to actually read in that color. (my eyes are not week but I love small fonts)
I was not sure how to do it but knew it can be changed as I studied them long time ago, did some research and found out there are multiple ways to perform it.
As my environment is an Ansible lab therefore it did not click me to just change it for a specific user therefore I changed in environment base:
This is what I did: (from root user)
Just above DIR value, I found out FILE parameter but it was commented, so i edited it to
Now my terminal is displaying 96 = turquoise as DIR and 91 = light red as FILE and I like it !!
For you reference color codes:
0 = default colour
1 = bold
4 = underlined
5 = flashing text
7 = reverse field
31 = red
32 = green
33 = orange
34 = blue
35 = purple
36 = cyan
37 = grey
40 = black background
41 = red background
42 = green background
43 = orange background
44 = blue background
45 = purple background
46 = cyan background
47 = grey background
90 = dark grey
91 = light red
92 = light green
93 = yellow
94 = light blue
95 = light purple
96 = turquoise
100 = dark grey background
101 = light red background
102 = light green background
103 = yellow background
104 = light blue background
105 = light purple background
106 = turquoise background
I did not try it but if you are interested in changing it for specific user you can try this:
cp /etc/DIR_COLORS to $HOME/.dir_colors
once copied, edit you local copy i.e .dir_colors and play with it.
Don’t forget you need to re-initialize the shell or logout and login back for changes to take affect.
First find the path of binary and configuration files, following is my example:
grep sudoers /var/sadm/install/contents
/opt/sfw/etc/sudoers f none 0440 root root 589 50133 1104945433 SFWsudo /opt/sfw/man/man4/sudoers.4 f none 0444 root bin 57547 31697 1104945433 SFWsudo /usr/local/share/vim/vim73/ftplugin/sudoers.vim f none 0644 bin bin 426 36373 1285497623 SMCvim /usr/local/share/vim/vim73/syntax/sudoers.vim f none 0644 bin bin 19276 64681 1285497623 SMCvim
Now my I can see that my configuration file i.e. sudoers is in /opt/sfw/etc/sudoers and for sudo it is always in the same path but in /bin directory i.e. /opt/sfw/bin/sudo
Steps for sudo to work properly:
Add /opt/sfw/bin in your PATH if it is not available – check with echo $PATH
Sudoers file default permission will be read only, for making changes you will need to first change the permission of sudoers file and edit your changes and revert back the permission of sudoers file to (chmod 440)
Sudo binary which is in /opt/sfw/bin should have the sticky bit set permission i.e. (chmod u+s )