CentOS

If you want to delete an object in the Squid proxy server cache, all you can do is manually and automatically delete the Squid proxy cache, here we will discuss how to maintain our proxy machine, the following methods can be run manually or automatically in removing the cache your squid proxy.

Manually delete the squid proxy cache;
1. Stop/stop the running Squid process

# /etc/init.d/squid stop

2. Clean all of Squid’s swap directory cache

On this occasion, we will discuss the process of installing Youtube Video Cache with Squid and Nginx on RHEL / CentOS where in previous writings more often used Ubuntu server in terms of creating a proxy server, but this time we will use OS Linux RHEL / CentOS 6 where to further explore our knowledge (I am personally) in terms of Linux networking: D. However, if you are still using the proxy world (ubuntu server), maybe this is one alternative in making proxy servers on RPM-based machines.
Install the packages needed in the squid installation process:

On this occasion, the Techsoftcenter web will share a little about “Clusters” where according to the title above is “High Availability: Linux Clustering on RHEL6 / CentOS6 with Luci and Ricci”. as we know that to do clustering can use several methods but for the opportunity this time we learn a little “High Availability – Linux Clustering using Luci and Ricci on OS Linux RHEL6 / CentOS6” To equalize perception, this time topology information uses Host Server: IP 192.168,100,250, has several VMs as follows:
arrif-base: IP 192.168,100,120 (arrif-base)
arrif-vm1: IP 192.168.100.102 (node1)
arrif-vm1: IP 192.168.100.103 (node2)
IP: 192.168.100.121 (virtual IP that is automatically formed by Ricci on the active node)
Where for the storage media to use the hard drive, if you don’t have a storage media, you can start creating an iSCSI target / multipath initiator on RHEL6 / CentOS6 Linux first on the article link.
First, do / configure / etc / hosts or you can use DNS server, configuration / etc / hosts

Under Linux NIC naming rules: eth0, eth1. First Ethernet card, and the second block. lo is the loopback interface, its fixed IP address is 127.0.0.1, mask 8. It represents your machine itself.

Ifconfig is the view card information

ifconfig [Interface]

The interface is optional, and if not this information is displayed for all network cards in the system. If you add this option to display the specified card information.

For example; ifconfig eth0

There are several ways in which resource limits can be applied to the docker container. Majorly below 3 ways can be used to set resource limits globally or individually for each container.

Setting Global limits for all containers

1. In docker 1.6 or later, we could set ulimit in /etc/sysconfig/docker as:

# vi /etc/sysconfig/docker
OPTIONS='--insecure-registry=172.30.0.0/16 --selinux-enabled --default-ulimit nproc=1024:2048'

This will set a soft limit of 1,024 and a hard limit of 2,048 child processes for all containers.