What is linux swp file
Linux swp file is a file with the suffix ".swp". This file is generated when using vi or vim to edit a file. When the editing is completed and exits normally, the file will be automatically deleted. ; The swp file is a hidden file and can only be viewed by using "ls -al" in the directory.
The operating environment of this article: Centos 7.6 system, Dell G3 computer.
What is a linux swp file?
The generation and solution of .swp files in Linux:
We use vi Command to edit the nginx.conf configuration file, and the prompt shown in the figure will appear. At this time, we can also directly press the E key to edit normally, but it may still occur next time. So what is the cause of this problem.
The following are two situations that will occur
(1) Another program may be editing the same file. If this is the case, be careful not to end up with two different instances of the same file when making changes. Quit, or continue with caution. (2) An edit session for this file crashed. If this is the case, use ":recover" or "vim -r nginx.conf" to recover the changes (see ":help recovery"). If you did this already, delete the swap file ".nginx.conf.swp" to avoid this message
Explain that this situation occurs because this file generates a swap file, that is, a file with the suffix .swp
1: When we edit a file and another person is also editing,
2 will appear: When we edit the file, there is a sudden power outage or sudden disconnection from the Internet. In order to prevent data loss, this will also appear. This kind of file
.swp file is swap (swap partition). When you use vi or vim to edit a file, it is generated. When the editing is completed and you exit normally, this file It will be automatically deleted. The .swp file is a hidden file. You can use ls -al in the directory to view it
When this file is generated, we can directly rm -f .nginx. conf.swp delete this swp file, otherwise a prompt will appear every time you edit it. However, if an abnormal exit occurs after editing the file, our configuration is not saved in the nginx.conf file at this time. We need to use vi -r nginx.conf to restore, as shown in the figure to restore the file, and then press Enter, the configuration will be restored from .swp to nginx.conf, and then delete the .swp file
If we change the settings for generating .swp files, we can add the set noswapfile command to the vim configuration (/etc/vimrc) to prevent this file from being generated during editing (set swapfile generates this file). However, it is recommended that everyone learn to use this file normally. Linux developers are more thoughtful and fully consider the mechanism under system abnormality to avoid data loss under system abnormality.
Recommended study: "linux video tutorial"
The above is the detailed content of What is linux swp file. 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

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

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



How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)

The reasons for the installation of VS Code extensions may be: network instability, insufficient permissions, system compatibility issues, VS Code version is too old, antivirus software or firewall interference. By checking network connections, permissions, log files, updating VS Code, disabling security software, and restarting VS Code or computers, you can gradually troubleshoot and resolve issues.

VS Code is available on Mac. It has powerful extensions, Git integration, terminal and debugger, and also offers a wealth of setup options. However, for particularly large projects or highly professional development, VS Code may have performance or functional limitations.

VS Code is the full name Visual Studio Code, which is a free and open source cross-platform code editor and development environment developed by Microsoft. It supports a wide range of programming languages and provides syntax highlighting, code automatic completion, code snippets and smart prompts to improve development efficiency. Through a rich extension ecosystem, users can add extensions to specific needs and languages, such as debuggers, code formatting tools, and Git integrations. VS Code also includes an intuitive debugger that helps quickly find and resolve bugs in your code.

How to back up VS Code configurations and extensions? Manually backup the settings file: Copy the key JSON files (settings.json, keybindings.json, extensions.json) to a safe location. Take advantage of VS Code synchronization: enable synchronization with your GitHub account to automatically back up all relevant settings and extensions. Use third-party tools: Back up configurations with reliable tools and provide richer features such as version control and incremental backups.
