After setting up your Chrony NTP Server and Client, we are now ready to configure authentication using randomly generated symmetric keys. This is an important option beyond the allow/deny rules within your /etc/chrony.conf file to maintain the integrity of the service.
Continue reading RHEL 8 and Chrony – Part 3
In Part 1, we discussed setting up Chrony from a client perspective. This post will show how to configure the server side and investigate some of the options available within the /etc/chrony.conf configuration file.
Install the Chrony package
Continue reading RHEL 8 and Chrony – Part 2
The Network Time Protocol or NTP is essential for synchronizing system clocks across your environment. Having a reliable and accurate time service is not only important for many different applications but for logging and auditing as well. In RHEL 8, Chrony is used for implementing NTP. In Part 1, we will review setting this service up as a client and look at the basic functionality of the chronyc command to interact with the chrony daemon, chronyd.
Continue reading RHEL 8 and Chrony – Part 1
Sometimes, due to some new specific server requirements, you will find it necessary to increase your swap space. Even if your swap partition is setup as a Logical Volume, your requirements may exceed what is available. This is where creating a new swap file is the best option. In this example, we are going to add a new 12GB swap file.
Verify the total amount of used and free physical and swap memory with the free command and the -h human-readable flag
# free -ht
total used free shared buff/cache available
Mem: 755G 321G 3.0G 62G 430G 670G
Swap: 4G 1G 3G
Total: 771G 322G 6G
Display the swap usage summary by device using swapon. Same as cat /proc/swaps
Continue reading Add a Swap File to RHEL/CentOSAlthough most of my test servers are registered with RackSpace, I thought that it would be a good idea to review AWS for some of my less technical colleagues that are interested in gently stepping into the Cloud Server arena. AWS offers a free tier service for 12 months using the t1.micro instance for 750 hours. However, a credit card will be required to setup an account so they may easily charge you if you decide to upgrade to another service level. Although this straightforward 25 step process will help you get up running with a RHEL 6.4 server, you should read the AWS documentation and FAQs to understand how the system works and pricing levels.
1. Go to the Amazon website and click “Get Started for Free“,
