


Detailed explanation of various uses of xargs command techniques in Linux
xargs is a filter for passing parameters to commands, and is also a tool for combining multiple commands. The following article mainly introduces to you the relevant information about the usage of xargs command in linux. Friends who need it can refer to it. Let’s take a look with the editor.
Preface
The xargs command reformats the received data and then provides it as a parameter to other commands. The xargs command is introduced below. Let’s take a look at various techniques for using commands.
1. Convert multi-line input into single-line input:
[root@host1 test]# echo -e "1 2 3 4 5 \n6 7 8 \n9 10 11 12" >example.txt [root@host1 test]# cat example.txt 1 2 3 4 5 6 7 8 9 10 11 12 [root@host1 test]# cat example.txt |xargs 1 2 3 4 5 6 7 8 9 10 11 12
Convert single-line input into multi-line output:
[root@host1 test]# cat example.txt | xargs -n 3 1 2 3 4 5 6 7 8 9 10 11 12
Customize the delimiter for conversion (the default delimiter is a space):
[root@host1 test]# echo "Hello:Hello:Hello:Hello" | xargs -d : -n 2 Hello Hello Hello Hello
2. Use it in the script:
[root@host1 test]# cat echo.sh #!/bin/bash echo $* '^-^'
When the parameters are passed to echo.sh
, it will print out these parameters and end with "^-^":
[root@host1 test]# echo -e "Tom\nHarry\nJerry\nLucy" > args.txt [root@host1 test]# cat args.txt | xargs bash echo.sh Tom Harry Jerry Lucy ^-^ [root@host1 test]# cat args.txt | xargs -n 2 bash echo.sh Tom Harry ^-^ Jerry Lucy ^-^
In the above example, we The parameter sources are put into the args.txt file, but in addition to these parameters, we also need some fixed parameters, such as:
[root@host1 test]# bash echo.sh Welcome Tom Welcome Tom ^-^
During the execution of the above command, Tom is the variable , the rest are constants, we can extract the parameters from "args.txt" and provide them to the command in the following way:
[root@host1 test]# bash echo.sh Welcome Tom [root@host1 test]# bash echo.sh Welcome Herry [root@host1 test]# bash echo.sh Welcome Jerry [root@host1 test]# bash echo.sh Welcome Lucy
At this time we need to use xargs -I command:
[root@host1 test]# cat args.txt | xargs -I {} bash echo.sh Welcome {} Welcome Tom ^-^ Welcome Harry ^-^ Welcome Jerry ^-^ Welcome Lucy ^-^
-I {} specifies the replacement of string. For each command parameter, the string {} will be replaced by the parameters read from stdin. ,
When -I is used, the command is executed in a loop. If there are 4 parameters, the command will be executed 4 times together with {}, in each execution {} will be replaced with the corresponding parameters.
3. Use with find
xargs and find are a very good combination, but we usually use it in the wrong way Ways to use them, such as:
[root@host1 test]# find . -type f -name "*.txt" -print | xargs rm -f
This is dangerous, sometimes delete unnecessary files, if the file name contains a space character (' '), then xargs It is possible to think that they are delimiters (e.g. file text.txt will be mistaken for file and text.txt by xargs).
If we want to use the output of find as the input of xargs, we must use -print0 in conjunction with find to separate the output with the characters null ('\0'), and use find to find out All .txt files, and then use xargs to delete these files:
[root@host1 test]# find . -type f -name "*.txt" -print0 | xargs -0 rm -f
This way you can delete all .txt files, xargs -0
Use \0 as the input delimiter.
4. Use the while statement and subshell
[root@host1 test]# cat files.txt | (while read arg ;do cat $arg;done)
This command is equivalent to:
[root@host1 test]# cat files.txt | xargs -I {} cat {}
In while loop, cat $arg
can be replaced with any number of commands, so that we can execute multiple commands on the same parameter, or we can use The output is passed to other commands. This technique is suitable for a variety of problem scenarios. Multiple commands within subshellOperator can be run as a whole.
Summarize
The above is the detailed content of Detailed explanation of various uses of xargs command techniques in Linux. 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



The key differences between CentOS and Ubuntu are: origin (CentOS originates from Red Hat, for enterprises; Ubuntu originates from Debian, for individuals), package management (CentOS uses yum, focusing on stability; Ubuntu uses apt, for high update frequency), support cycle (CentOS provides 10 years of support, Ubuntu provides 5 years of LTS support), community support (CentOS focuses on stability, Ubuntu provides a wide range of tutorials and documents), uses (CentOS is biased towards servers, Ubuntu is suitable for servers and desktops), other differences include installation simplicity (CentOS is thin)

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).

CentOS has been discontinued, alternatives include: 1. Rocky Linux (best compatibility); 2. AlmaLinux (compatible with CentOS); 3. Ubuntu Server (configuration required); 4. Red Hat Enterprise Linux (commercial version, paid license); 5. Oracle Linux (compatible with CentOS and RHEL). When migrating, considerations are: compatibility, availability, support, cost, and community support.

CentOS installation steps: Download the ISO image and burn bootable media; boot and select the installation source; select the language and keyboard layout; configure the network; partition the hard disk; set the system clock; create the root user; select the software package; start the installation; restart and boot from the hard disk after the installation is completed.

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).

Docker uses Linux kernel features to provide an efficient and isolated application running environment. Its working principle is as follows: 1. The mirror is used as a read-only template, which contains everything you need to run the application; 2. The Union File System (UnionFS) stacks multiple file systems, only storing the differences, saving space and speeding up; 3. The daemon manages the mirrors and containers, and the client uses them for interaction; 4. Namespaces and cgroups implement container isolation and resource limitations; 5. Multiple network modes support container interconnection. Only by understanding these core concepts can you better utilize Docker.

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)

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.
