How To Use the AWK language to Manipulate Text in Linux

lufy

March 18, 2020

&nbsp;
from&nbsp;<a href="https://www.digitalocean.com/community/tutorials/how-to-use-the-awk-language-to-manipulate-text-in-linux">https://www.digitalocean.com/community/tutorials/how-to-use-the-awk-language-to-manipulate-text-in-linux</a>
<h3 id="introduction">Introduction</h3>
Linux utilities often follow the Unix philosophy of design. Tools are encouraged to be small, use plain text files for input and output, and operate in a modular manner. Because of this legacy, we have great text processing functionality with tools like&nbsp;<a href="https://www.digitalocean.com/community/articles/the-basics-of-using-the-sed-stream-editor-to-manipulate-text-in-linux">sed</a>&nbsp;and awk.
In this guide, we will discuss awk. Awk is both a programming language and text processor that can be used to manipulate text data in very useful ways. We will be discussing this on an Ubuntu 12.04 VPS, but it should operate the same on any modern Linux system.
<a name="basic-syntax" data-unique="basic-syntax"></a><a name="basic-syntax" data-unique="basic-syntax"></a>
<h2 id="basic-syntax">Basic Syntax</h2>
The&nbsp;<code>awk</code>&nbsp;command is included by default in all modern Linux systems, so we do not need to install it to begin using it.
Awk is most useful when handling text files that are formatted in a predictable way. For instance, it is excellent at parsing and manipulating tabular data. It operates on a line-by-line basis and iterates through the entire file.
By default, it uses whitespace (spaces, tabs, etc.) to separate fields. Luckily, many configuration files on your Linux system use this format.
The basic format of an awk command is:
<pre>awk '/search_pattern/ { action_to_take_on_matches; another_action; }' file_to_parse
</pre>
You can omit either the search portion or the action portion from any awk command. By default, the action taken if the &ldquo;action&rdquo; portion is not given is &ldquo;print&rdquo;. This simply prints all lines that match.
If the search portion is not given, awk performs the action listed on each line.
If both are given, awk uses the search portion to decide if the current line reflects the pattern, and then performs the actions on matches.
<a name="simple-uses" data-unique="simple-uses"></a><a name="simple-uses" data-unique="simple-uses"></a>
<h2 id="simple-uses">Simple Uses</h2>
In its simplest form, we can use awk like&nbsp;<code>cat</code>&nbsp;to simply print all lines of a text file out to the screen.
Let&rsquo;s print out our server&rsquo;s fstab file, which lists the filesystems that it knows about:
<pre>awk '{print}' /etc/fstab
</pre>
<pre># /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# 
proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/vda1 during installation
UUID=b96601ba-7d51-4c5f-bfe2-63815708aabd / ext4 noatime,errors=remount-ro 0 1
</pre>
This isn&rsquo;t very useful. Let&rsquo;s try out awk&rsquo;s search filtering capabilities:
<pre>awk '/UUID/' /etc/fstab
</pre>
<pre># device; this may be used with UUID= as a more robust way to name devices
UUID=b96601ba-7d51-4c5f-bfe2-63815708aabd / ext4 noatime,errors=remount-ro 0 1
</pre>
As you can see, awk now only prints the lines that have &ldquo;UUID&rdquo; in them. We can get rid of the extraneous comment line by specifying that UUID must be located at the very beginning of the line:
<pre>awk '/^UUID/' /etc/fstab
</pre>
<pre>UUID=b96601ba-7d51-4c5f-bfe2-63815708aabd / ext4 noatime,errors=remount-ro 0 1
</pre>
Similarly, we can use the action section to specify which pieces of information we want to print. For instance, to print only the first column, we can type:
<pre>awk '/^UUID/ {print $1;}' /etc/fstab
</pre>
<pre>UUID=b96601ba-7d51-4c5f-bfe2-63815708aabd
</pre>
We can reference every column (as delimited by whitespace) by variables associated with their column number. The first column can be referenced by&nbsp;<code>$1</code>&nbsp;for instance. The entire line can by referenced by&nbsp;<code>$0</code>.
<a name="awk-internal-variables-and-expanded-format" data-unique="awk-internal-variables-and-expanded-format"></a><a name="awk-internal-variables-and-expanded-format" data-unique="awk-internal-variables-and-expanded-format"></a>
<h2 id="awk-internal-variables-and-expanded-format">Awk Internal Variables and Expanded Format</h2>
Awk uses some internal variables to assign certain pieces of information as it processes a file.
The internal variables that awk uses are:
<ul>
<li>FILENAME: References the current input file.</li>
<li>FNR: References the number of the current record relative to the current input file. For instance, if you have two input files, this would tell you the record number of each file instead of as a total.</li>
<li>FS: The current field separator used to denote each field in a record. By default, this is set to whitespace.</li>
<li>NF: The number of fields in the current record.</li>
<li>NR: The number of the current record.</li>
<li>OFS: The field separator for the outputted data. By default, this is set to whitespace.</li>
<li>ORS: The record separator for the outputted data. By default, this is a newline character.</li>
<li>RS: The record separator used to distinguish separate records in the input file. By default, this is a newline character.</li>
</ul>
We can change the values of these variables at will to match the needs of our files. Usually we do this during the initialization phase of our awk processing.
This brings us to another important concept. Awk syntax is actually slightly more complex than what we showed initially. There are also optional&nbsp;<code>BEGIN</code>&nbsp;and&nbsp;<code>END</code>&nbsp;blocks that can contain commands to execute before and after the file processing, respectively.
This makes our expanded syntax look something like this:
<pre>awk 'BEGIN { action; }
/search/ { action; }
END { action; }' input_file
</pre>
The BEGIN and END keywords are actually just specific sets of conditions just like the search parameters. They match before and after the document has been processed.
This means that we can change some of the internal variables in the BEGIN section. For instance, the&nbsp;<code>/etc/passwd</code>&nbsp;file is delimited with colons (:) instead of whitespace. If we wanted to print out the first column of this file, we could type:
<pre>sudo awk 'BEGIN { FS=":"; }
{ print $1; }' /etc/passwd
</pre>
<pre>root
daemon
bin
sys
sync
games
man
. . .
</pre>
We can use the BEGIN and END blocks to print simple information about the fields we are printing:
<pre>sudo awk 'BEGIN { FS=":"; print "User\t\tUID\t\tGID\t\tHome\t\tShell\n--------------"; }
{print $1,"\t\t",$3,"\t\t",$4,"\t\t",$6,"\t\t",$7;}
END { print "---------\nFile Complete" }' /etc/passwd
</pre>
<pre>User UID GID Home Shell
--------------
root 0 0 /root /bin/bash
daemon 1 1 /usr/sbin /bin/sh
bin 2 2 /bin /bin/sh
sys 3 3 /dev /bin/sh
sync 4 65534 /bin /bin/sync
. . .
---------
File Complete
</pre>
As you can see, we can format things quite nicely by taking advantage of some of awk&rsquo;s features.
Each of the expanded sections are optional. In fact, the main action section itself is optional if another section is defined. We can do things like this:
<pre class="code-pre "><code>awk 'BEGIN { print "We can use awk like the echo command"; }'
</code></pre>
<pre class="code-pre "><code>We can use awk like the echo command
</code></pre>
<a name="awk-field-searching-and-compound-expressions" data-unique="awk-field-searching-and-compound-expressions"></a><a name="awk-field-searching-and-compound-expressions" data-unique="awk-field-searching-and-compound-expressions"></a>
<h2 id="awk-field-searching-and-compound-expressions">Awk Field Searching and Compound Expressions</h2>
In one of the examples above, we printed the line in the&nbsp;<code>/etc/fstab</code>&nbsp;file that began with &ldquo;UUID&rdquo;. This was easy because we were looking for the beginning of the entire line.
What if we wanted to find out if a search pattern matched at the beginning of a&nbsp;field&nbsp;instead?
We can create a&nbsp;<code>favorite_food.txt</code>&nbsp;file which lists an item number and the favorite foods of a group of friends:
<pre class="code-pre "><code>echo "1 carrot sandy
2 wasabi luke
3 sandwich brian
4 salad ryan
5 spaghetti jessica" &gt; favorite_food.txt
</code></pre>
If we want to find all foods from this file that begin with &ldquo;sa&rdquo;, we might begin by trying something like this:
<pre class="code-pre "><code>awk '/sa/' favorite_food.txt
</code></pre>
<pre class="code-pre "><code>1 carrot sandy
2 wasabi luke
3 sandwich brian
4 salad ryan
</code></pre>
Here, we are matching any instance of &ldquo;sa&rdquo; in the word. This does exclude things like &ldquo;wasabi&rdquo; which has the pattern in the middle, or &ldquo;sandy&rdquo; which is not in the column we want. We are only interested in words&nbsp;beginning&nbsp;with &ldquo;sa&rdquo; in the&nbsp;second&nbsp;column.
We can tell awk to only match at the beginning of the second column by using this command:
<pre class="code-pre "><code>awk '$2 ~ /^sa/' favorite_food.txt
</code></pre>
<pre class="code-pre "><code>3 sandwich brian
4 salad ryan
</code></pre>
As you can see, this allows us to only search at the beginning of the second column for a match.
The &ldquo;^&rdquo; character tells awk to limit its searches to the beginning of the field. The &ldquo;field_num ~&rdquo; part specifies that it should only pay attention to the second column.
We can just as easily search for things that do&nbsp;not&nbsp;match by including the &ldquo;!&rdquo; character before the tilde (~). This command will return all lines that do&nbsp;not&nbsp;have a food that starts with &ldquo;sa&rdquo;:
<pre class="code-pre "><code>awk '$2 !~ /^sa/' favorite_food.txt
</code></pre>
<pre class="code-pre "><code>1 carrot sandy
2 wasabi luke
5 spaghetti jessica
</code></pre>
If we decide later on that we are only interested in lines where the above is true and the item number is less than 5, we could use a compound expression like this:
<pre class="code-pre "><code>awk '$2 !~ /^sa/ &amp;&amp; $1 &lt; 5' favorite_food.txt
</code></pre>
This introduces a few new things. The first is the ability to add additional requirements for the line to match by using the&nbsp;<code>&amp;&amp;</code>&nbsp;operator. Using this, you can combine an arbitrary number of conditions for the line to match.
We use this operator to add a check that the value of the first column is less than 5.
<a name="conclusion" data-unique="conclusion"></a><a name="conclusion" data-unique="conclusion"></a>
<h2 id="conclusion">Conclusion</h2>
By now, you should have a basic understanding of how awk can manipulate, format, and selectively print text files. Awk is a much larger topic though, and is actually an entire programming language complete with variable assignment, control structures, built-in functions, and more. It can be used in scripts to easily format text in a reliable way.
To learn more about how to work with awk, check out the great online resources for awk, and more relevantly, gawk, the GNU version of awk present on modern Linux distributions.
&nbsp;

How To Use the AWK language to Manipulate Text in Linux

Comments (0)

Leave a Comment