


How to set up swap on Linux cloud server
Step one: Confirm the status of swap
Use the following command to check the memory status:
free -m
If the result shows that swap is 0, it means that swap does not exist and you need to create swap.
total used free shared buffers cached Mem: 1840 1614 226 15 36 1340 -/+ buffers/cache: 238 1602 Swap: 0 0 0
Or you can use this command to view it. If no results are output, swap does not exist.
swapon -s
Step 2: Create swap
We use the following command to create a swap file with a size of 2GB.
dd if=/dev/zero of=/swapfile count=2048 bs=1M
The output results are as follows:
2048+0 records in 2048+0 records out 2147483648 bytes (2.1 GB) copied, 10.5356 s, 204 MB/s
Step 3: Activate swap
swap will not be automatically recognized by default. We need to set appropriate permissions before it can be used normally. Execute the following command to set the permissions of the swap file to 600, which means it can be read and written by the root user.
chmod 600 /swapfile
Activate swap:
mkswap /swapfile
The output results are as follows:
Setting up swapspace version 1, size = 2097148 KiB no label, UUID=ff3fc469-9c4b-4913-b653-ec53d6460d0e
Step 4: Enable swap
Execute the following command to enable swap
swapon /swapfile
By default, the swap file will not be automatically started with the system, so it needs to be written to the file system.
vi /etc/fstab
Add the following code at the end:
/swapfile none swap sw 0 0
After saving with the :wq command, swap will be started with the system.
Finally, we can use the free command to confirm whether swap is set successfully.
free -m
The output results are as follows. You can see that swap is no longer 0, indicating that swap has been set successfully.
total used free shared buffers cached Mem: 1840 1754 86 16 23 1519 -/+ buffers/cache: 210 1630 Swap: 2047 0 2047
The above is the detailed content of How to set up swap on Linux cloud server. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



Steps to start Nginx in Linux: Check whether Nginx is installed. Use systemctl start nginx to start the Nginx service. Use systemctl enable nginx to enable automatic startup of Nginx at system startup. Use systemctl status nginx to verify that the startup is successful. Visit http://localhost in a web browser to view the default welcome page.

How to confirm whether Nginx is started: 1. Use the command line: systemctl status nginx (Linux/Unix), netstat -ano | findstr 80 (Windows); 2. Check whether port 80 is open; 3. Check the Nginx startup message in the system log; 4. Use third-party tools, such as Nagios, Zabbix, and Icinga.

Starting an Nginx server requires different steps according to different operating systems: Linux/Unix system: Install the Nginx package (for example, using apt-get or yum). Use systemctl to start an Nginx service (for example, sudo systemctl start nginx). Windows system: Download and install Windows binary files. Start Nginx using the nginx.exe executable (for example, nginx.exe -c conf\nginx.conf). No matter which operating system you use, you can access the server IP

The server does not have permission to access the requested resource, resulting in a nginx 403 error. Solutions include: Check file permissions. Check the .htaccess configuration. Check nginx configuration. Configure SELinux permissions. Check the firewall rules. Troubleshoot other causes such as browser problems, server failures, or other possible errors.

How to fix Nginx 403 Forbidden error? Check file or directory permissions; 2. Check .htaccess file; 3. Check Nginx configuration file; 4. Restart Nginx. Other possible causes include firewall rules, SELinux settings, or application issues.

Answer to the question: 304 Not Modified error indicates that the browser has cached the latest resource version of the client request. Solution: 1. Clear the browser cache; 2. Disable the browser cache; 3. Configure Nginx to allow client cache; 4. Check file permissions; 5. Check file hash; 6. Disable CDN or reverse proxy cache; 7. Restart Nginx.

In Linux, use the following command to check whether Nginx is started: systemctl status nginx judges based on the command output: If "Active: active (running)" is displayed, Nginx is started. If "Active: inactive (dead)" is displayed, Nginx is stopped.

The error log is located in /var/log/nginx (Linux) or /usr/local/var/log/nginx (macOS). Use the command line to clean up the steps: 1. Back up the original log; 2. Create an empty file as a new log; 3. Restart the Nginx service. Automatic cleaning can also be used with third-party tools such as logrotate or configured.
