Archive | GNU/Linux

Recover deleted files on Linux (Beginners Tutorial)

Have you ever deleted any important files by mistake? Who doesn’t! Okay, but can I recover them? In this post, you will learn how to recover deleted files on Linux using various programs on different file systems. You will see how to recover deleted files from SD cards, HDDs, and deleted partitions on different Linux file systems such as EXT3, EXT4 and even from Windows file systems such as FAT32 & NTFS. This is quite a problem. Often, Linux users frequently install several systems at the same time and they may delete a partition bu mistake during the installation process. However, how to recover files from those deleted partitions? For this, we need to recover the partition using a tool called TestDisk. Testdisk is a powerful partition analysis and data recovery utility. It is shipped with a large number of Linux distributions such as Debian and Ubuntu. On the other hand, the application is cross-platform and supports a large number of partition tables such as Intel, MSDOS, and Mac. These are the most popular partition tables. Also, it supports many file systems such as NTFS, EXT4 and other nonpopular file systems such as BeOS and ReiserFS.

Continue Reading →

Recover files from deleted partition

When a file is deleted, the list of clusters occupied by the file is deleted, marking those sectors available for the use. If the clusters have not been overwritten, TestDisk can recover the files.

First, start the application like this:

$ testdisk

Next, you have the option to create a new file for the logs. If you want to create one, choose the create option and press Enter. If you don’t want a log file, select the No Log option.

Using testdisk

Next, the disks or partitions recognized by the system will be scanned. In this particular case, sda is the partition we want to recover.

Scan the devices

TestDisk recognizes various types of partition tables. It is usually Intel. Unless you are using a specialized one.

Select the partition table

In the next screen, you will see a series of options that the program has. For this particular case, we need to choose the Analyse option.

With this option, the program will exhaustively analyze the disk to find the structure.

Analyse the disk

Then, it will ask about the type of search you wish to do. Usually, choose the Quick Search option.

The partition structure

If you are lucky, you will see the deleted partition. If not, you will have to choose a deeper search.

Using TestDisk

Then, choose the Write option to write the partition table. When finished, restart the system and you will have your partition back!

Recover a partition

Reboot to apply the changes

Note that during these steps, it may take a long time. It depends on the disk size.

According to the type of file system, this partition may have, particular instructions will be followed. They will be detailed later.

Recover deleted files from an external drive

Now let us imagine we have an external flash drive and by mistake, you have deleted some files from it. How to restore them?

Thanks to TestDisk, the process becomes quite similar to that of a deleted partition. But there are some differences.

To start the program we will use the testdisk command. Also, we can add the flash drive as a parameter like this:

$ sudo testdisk /dev/sdb

TestDisk to recover files

Next, select proceed. Then, choose the partition table type.

Select the partition table

Then, select the Advanced options to recover files.

Advanced options on TestDisk

The next step is selecting the partition and the Undelete option.

Undelete files with TestDisk

Then, you will see all the deleted files on the partition.

Recover files with TestDisk

Now, select the destination folder to place the recovered files. You need to press C on the first option to place the files on the current directory.

Select the destination folder

Finally, you will see this message:

Everything OK with TestDisk

Congratulations! Files restored.

Recover deleted files from SD card

Usually, on an SD card, it is common to notice that they are used for multimedia files. Therefore, it is advisable to use a more specialized program for these files.

In this case, we will use the application called Photorec that comes incorporated in TestDisk.

First, insert the SD card on the PC. Next, run photorec as root:

$ sudo photorec [device]

Then, you will see the following image. Select the media and proceed and press Enter.

Using photorec to recover files from SD

Next, select the partition. And select Options and press enter.

Select the partition

There you will see the recovery options that will be performed on the SD card.

Photorec options

Press q to return to the previous screen. And there it is necessary to choose the types of files that we want to recover. This is achieved by selecting the File Opt option.

Formats to recover

Press the s key to select and deselect all formats. You can also select the types of files you want to recover using the right key. To save the selected options press the b key. Return to the main menu using the q key.

Then, on the main menu, choose the Search option to start the process. And choose the file system.

Select the file system

You will then be presented with two options. Free and Whole. Normally, Free is enough. If you want to do a deep analysis, choose Whole but keep in mind that it will slow down the process.

Now, it is necessary to choose the location where the files will be saved. To do this, press the c key.

Select the destination

After choosing the destination, the recovery process will start. Remember that the system will collapse and freeze. So be patient.

In the end, you will see a message informing you of everything that has happened.

Photorec report

Next, check the results.

Check the results

Recover deleted files from NTFS

NTFS is a Windows file system. If you are one of those who use both systems on the computer, then you may need to restore deleted files from a Windows partition with this file system.

To do this, we have a tool called ntfsundelete that is quite simple to use.

First, you need to scan the disk or partition. For example:

$ sudo ntfsundelete /dev/sda1

Using ntfsundelete

Then, we will be able to recover the deleted file with the following command:

$ sudo ntfsundelete [HD_Or_partition] -u -m [filename]

Recovering files using ntfsundelete 

 The recovered files now belong to the root user. The last step is to change the permissions and owners of the files using the chown command.

Recover Files from FAT32

Another common Windows file system is FAT32. You can recover files from FAT32 is by using TestDisk.

So again run testdisk as root user and pass the disk as a parameter:

$ sudo testdisk [partition/HD]

TestDisk is compatible with FAT32 

Then continue the steps as described above to restore of the files.

Recover on memory files (Using inode)

If you delete a file that is used by another process, you can restore it from the memory using inode.

To do this, some initial conditions must be established. First, the deleted file MUST remain open by another process. Then you have to verify the process and finally recover it and change its permissions.

In this case, I will create a file called example.txt using the nano editor and add some text:

$ nano example.txt

Then save the changes and open another terminal window and use the file. For example, with the less command.

$ less example.txt

Using the less command

 Open another terminal session, delete the file and make sure it’s deleted:

$ rm example.txt

$ ls example.txt

Delete the example file

As you can see, the file no longer exists. But we will be able to recover it. To do this, let’s get the number of the process associated with the inode of the file.

$ lsof | grep example.txt

Check the deleted file

You will notice the process and command that is using the file (the less command). From that image, we have to pay attention to the second and fourth values. These are the PID of the process and the descriptor of the file respectively.

Then, recover it with the following command:

$ ls -l /proc/2325/fd/4

Find the process of the deleted file

Then copy it to whatever location you want and that is enough to recover it.

$ sudo cp /proc/2325/fd/4 .

Next, check the results and open the file:

Recover a deleted file using inode  

This way we can recover a deleted file that still on memory and used by a process with the inode.

Recover Deleted Files from EXT4 (Using extundelete)

EXT4 is the default file system on most Linux distributions. It is quite fast and with technical features that are very well taken advantage of by the Linux kernel.

One of the used tools to recover files from EXT4 filesystem is extundelete.

Extundelete is an open-source application that allows recovering deleted files from a partition or a disk with EXT3 or EXT4 file system. It is simple to use and comes by default installed on most Linux distributions.

To recover a certain file, just use the following command:

$ sudo extundelete [device] -restore-file [pathfile]

For example:

$ sudo extundelete /dev/sdb1 -restore-file home/angelo/other.txt

If you want to recover all the files in a folder, use the wildcard character:

$ extundelete /dev/sda6 -restore-file home/angelo/*

But if you want to restore all files on the partition or disk, the next command would suffice:

$ extundelete /dev/sda6 -restore-all

Using extundelete to recover files

So, the recovered files will be on the RECOVERED_FILES directory. So this way, you can recover deleted files using extundelete.

Using debugfs

It is also possible to use the debugfs tool to recover deleted files. This tool also uses the inode number of the deleted file. However, it only works on EXT4 file systems.

Its operation is quite simple, too. First, you have to enter the partition or device.

$ debugfs [device]

For example,

$ sudo debugfs /dev/sdb1

Using debugfs

Then, after a while, you will be able to login to the debugfs console to search for recently deleted files.

$ debugfs: lsdel

inodes to recover

In the first column, you will see the inode number of the deleted files in that device. Then, restore it with the following command:

$ debugfs mi

And that is it. It is quite easy.

Using ext4magic

Another alternative way to recover deleted files on a disk with an Ext4 file system is to use Ext4magic. This application is also quite simple to use.

The most basic syntax of the application is the following:

$ sudo ext4magic [device] -f [folder_to_scan] -r -d [output_folder]

If I wanted to recover the deleted files from a folder called files, the command would be similar to this one:

$ sudo ext4magic /dev/sdb1 -r -d files

Using ext4magic to recover files

That is how easy it is to use ext4magic. All this thanks to the fact that Ext4 is a community and open source file system.

Recover overwritten files (Using Scalpel)

Scapel is another open-source tool that allows you to recover files from formatted drives, overwritten files and even damaged drives. It is well known for its speed and efficiency. In this sense, it emerges as an alternative to consider.

Scalpel carves files without the help of filesystems. It tries to extract headers and footers of files and tries to guess the entire file structure using some well-designed algorithms.

Like TestDisk, it is available in the official repositories of most Linux distributions. Therefore, its installation is reduced to the use of the terminal and the package manager of the distribution.

The fastest and easiest way to use Scapel is as follows:

$ scalpel [device] -o [output_folder]

The output_folder where scapel will place all recovered files. Note that Scalpel will create the output directory itself.

But how does Scapel know which files to recover? Well, that is defined in the application configuration file.

This configuration file is usually located at the following location:

/etc/scalpel/scalpel.conf

And you can open it with your favorite text editor and there you will only have to uncomment the lines to define the file formats to search.

Scalpel configuration file

The file formats you uncomment, Scalpel will search for it.

Next, run the full Scalpel command and in the output folder, you will see the recovered files.

$ sudo scalpel /dev/sdb1 -o recovered_files1

Using scalpel to recover files

Sometimes, Scalpel restores parts of the file. That depends on the health of the drive and how much data has been corrupted.

Also, there are many craving algorithms you can use, but we discussed here the basic way of craving data.

Recover files from a non-bootable system

This is a delicate case because we need to access from a Live cd of Ubuntu or another similar Linux distribution. Once we have boot, we could use TestDisk to try to recover the data.

In this case, we would have to use an external drive where to save the data. On the other hand, in case TestDisk can’t do the job, we can also try extundelete or ext4magic as long as the partition is Ext4.

If it does not work, you could try regenerating the partition using TestDisk as explained above.

Conclusion

It is possible to delete files accidentally. The idea is to know the appropriate tools and techniques to recover these files.

In this post, we have covered several circumstances and different file systems that could help avoid such problems.

Keep coming back.

Thank you.

0

Omarine 6.2 duyuruldu

Aslında bir sunucu projesi olan Vietnam kökenli GNU/Linux dağıtımı Omarine‘in 6.2 sürümü duyuruldu. Ayrıca GNOME, KDE Plasma, Xfce ve LXDE masaüstü ortamlarıyla bir masaüstü bilgisayarda da kullanılabilen Omarine, ilk başta Slackware Linux’a dayalı olarak üretilmiş olsa da artık bağımsız olarak çıkarılıyor. Sistemin virüslere karşı son derece korunaklı olarak üretildiği ifade ediliyor. Dahili bir güvenlik duvarı içeren sistem Security Enhanced Linux (SELinux) ile donatılmış bulunuyor. Yeni sürüm, Xfce 4.14 ve GNOME 3.32.2 masaüstü ortamları dışında BIND 9.14.4, MySQL 8.0.17, GnuCash 3.6 gibi güncel yazılımları içeriyor. Bu sürümdeki en önemli değişikliğin, sistemi otomatik olarak güncelleyen Omarine Update programı olduğu bildirilirken, güncellemelerin kullanıcıya bildirileceği, dileyen kullanıcının root olarak omarine-update komutunu kullanarak sistemi güncelleyebileceği belirtildi. Omarine 6.2 hakkında ayrıntılı bilgi edinmek için sistemin web sayfasını inceleyebilirsiniz.

Continue Reading →

Omarine 6.2 edinmek için aşağıdaki linkten yararlanabilirsiniz.

0

Endless OS 3.6.3 duyuruldu

GNOME 3’ten çatallanmış özelleştirilmiş bir masaüstü ortamını kullanarak, basitleştirilmiş ve düzenli bir kullanıcı deneyimi sunmayı amaç edinen Debian GNU/Linux tabanlı Endless OS‘nin 3.6.3 sürümü, Endless OS ekibi tarafından duyuruldu.  3.6 serisi için yeni bir güncelleme olarak gelen yeni sürüm, bilgisayar sahibinin sistemi kilitlemesine yardımcı olmak için birkaç yeni temel özellik sunuyor ve aynı zamanda önyükleme ve masaüstünde oturum açma ile ilgili bazı sorunları düzeltiyor. Artık kullanıcıların web tarayıcılarına ebeveyn denetimleriyle erişimlerini kısıtlamak olanağı olduğu bildiriliyor. 3.6.0 ve 3.6.2 arasında, önyükleme ve bilgisayarda oturum açmayı önleyebilecek bilinen iki sorun olduğu, her ikisinin de bu sürümde düzeltildiği ifade ediliyor. Debian 10 “Buster” tabanlı olarak gelen sistemde, pek çok paket en güncel sürümleriyle geliyor. Endless OS 3.6.3 hakkında ayrıntılı bilgi edinmek için sürüm duyurusunu inceleyebilirsiniz.

Continue Reading →

Endless OS 3.6.3 edinmek için aşağıdaki linklerden yararlanabilirsiniz.

0

Slax 9.11.0 duyuruldu

Debian’ın kararlı versiyonuna dayanan minimalist bir masaüstü live CD’si olarak kullanıma sunulan Slax‘ın 9.11.0 sürümü, Tomáš Matějíček tarafından duyuruldu. Yeni okul yılının başladığını söyleyen Matějíček; yeni Slax sürümünün de kullanıma hazır olduğunu belirtti. Sürümün, Debian 9.11 Jessie’den gelen tüm hata düzeltmelerini ve güvenlik güncellemelerini içerdiğini söyleyen Matějíček; konsol boşluğunun varsayılan olarak devre dışı olduğunu hatırlattı. Slax projesinin kararlı sürümün onbirinci güncellemesini duyurmaktan mutluluk duyduğunu söyleyen Matějíček; paralel indirme özelliği kullanılarak TFTP sunucusundan PXE önyüklemesinin şimdi 3 kat daha hızlı indirilebildiğini söyledi. Matějíček; Debian 10’a dayanan Slax için çalışmaların devam ettiğini, ancak henüz hazır olmadığını, hazır olması için en azından birkaç hafta gerektiğini söyledi. Slax 9.11.0 hakkında ayrıntılı bilgi edinmek için sürüm duyurusunu inceleyebilirsiniz.

Continue Reading →

Slax 9.11.0 edinmek için aşağıdaki linklerden yararlanabilirsiniz.

0

Expect command and how to automate shell scripts like magic

In the previous post, we talked about writing practical shell scripts and we saw how it is easy to write a shell script. Today we are going to talk about a tool that does magic to our shell scripts, that tool is the Expect command or Expect scripting language. Expect command or expect scripting language is a language that talks with your interactive programs or scripts that require user interaction. Expect scripting language works by expecting input, then the Expect script will send the response without any user interaction. You can say that this tool is your robot which will automate your scripts.

Continue Reading →

If Expect command if not installed on your system, you can install it using the following command:

$ apt-get install expect

Or on Red Hat based systems like CentOS:

$ yum install expect

Expect Command

Before we talk about expect command, Let’s see some of the expect command which used for interaction:

spawn                  Starting a script or a program.

expect                  Waiting for program output.

send                      Sending a reply to your program.

interact                Allowing you in interact with your program.

  • The spawn command is used to start a script or a program like the shell, FTP, Telnet, SSH, SCP, and so on.
  • The send command is used to send a reply to a script or a program.
  • The Expect command waits for input.
  • The interact command allows you to define a predefined user interaction.

We are going to type a shell script that asks some questions and we will make an Expect script that will answer those questions.

First, the shell script will look like this:

#!/bin/bash

echo "Hello, who are you?"

read $REPLY

echo "Can I ask you some questions?"

read $REPLY

echo "What is your favorite topic?"

read $REPLY

Now we will write the Expect scripts that will answer this automatically:

#!/usr/bin/expect -f

set timeout -1

spawn ./questions

expect "Hello, who are you?\r"

send -- "Im Adam\r"

expect "Can I ask you some questions?\r"

send -- "Sure\r"

expect "What is your favorite topic?\r"

send -- "Technology\r"

expect eof

The first line defines the expect command path which is #!/usr/bin/expect.

On the second line of code, we disable the timeout. Then start our script using spawn command.

We can use spawn to run any program we want or any other interactive script.

The remaining lines are the Expect script that interacts with our shell script.

The last line if the end of file which means the end of the interaction.

Now Showtime, let’s run our answer bot and make sure you make it executable.

$ chmod +x ./answerbot

$./answerbot

expect command

Cool!! All questions are answered as we expect.

If you get errors about the location of Expect command you can get the location using the which command:

$ which expect

We did not interact with our script at all, the Expect program do the job for us.

The above method can be applied to any interactive script or program.Although the above Expect script is very easy to write, maybe the Expect script little tricky for some people, well you have it.

Using autoexpect

To build an expect script automatically, you can the use autoexpect command.

autoexpect works like expect, but it builds the automation script for you. The script you want to automate is passed to autoexpect as a parameter and you answer the questions and your answers are saved in a file.

$ autoexpect ./questions

autoexpect command

A file is generated called script.exp contains the same code as we did above with some additions that we will leave it for now.

autoexpect script

If you run the auto generated file script.exp, you will see the same answers as expected:

autoexpect script execution

Awesome!! That super easy.

There are many commands that produce changeable output, like the case of FTP programs, the expect script may fail or stuck. To solve this problem, you can use wildcards for the changeable data to make your script more flexible.

Working with Variables

The set command is used to define variables in Expect scripts like this:

set MYVAR 5

To access the variable, precede it with $ like this $VAR1

To define command line arguments in Expect scripts, we use the following syntax:

set MYVAR [lindex $argv 0]

Here we define a variable MYVAR which equals the first passed argument.

You can get the first and the second arguments and store them in variables like this:

set my_name [lindex $argv 0]

set my_favorite [lindex $argv 1]

Let’s add variables to our script:

#!/usr/bin/expect -f

set my_name [lindex $argv 0]

set my_favorite [lindex $argv 1]

set timeout -1

spawn ./questions

expect "Hello, who are you?\r"

send -- "Im $my_name\r"

expect "Can I ask you some questions?\r"

send -- "Sure\r"

expect "What is your favorite topic?\r"

send -- "$my_favorite\r"

expect eof

Now try to run the Expect script with some parameters to see the output:

$ ./answerbot SomeName Programming

expect command variables

Awesome!! Now our automated Expect script is more dynamic.

Conditional Tests

You can write conditional tests using braces like this:

expect {

"something" { send -- "send this\r" }

"*another" { send -- "send another\r" }

}

We are going to change our script to return different conditions, and we will change our Expect script to handle those conditions.

We are going to emulate different expects with the following script:

#!/bin/bash

let number=$RANDOM

if [ $number -gt 25000 ]; then

echo "What is your favorite topic?"

else

echo "What is your favorite movie?"

fi

read $REPLY

A random number is generated every time you run the script and based on that number, we put a condition to return different expects.

Let’s make out Expect script that will deal with that.

#!/usr/bin/expect -f

set timeout -1

spawn ./questions

expect {

"*topic?" { send -- "Programming\r" }

"*movie?" { send -- "Star wars\r" }

}

expect eof

expect command conditions

Very clear. If the script hits the topic output, the Expect script will send programming and if the script hits movie output the expect script will send star wars. Isn’t cool?

If else Conditions

You can use if/else clauses in expect scripts like this:

#!/usr/bin/expect -f

set NUM 1

if { $NUM < 5 } {

puts "\Smaller than 5\n"

} elseif { $NUM > 5 } {

puts "\Bigger than 5\n"

} else {

puts "\Equals 5\n"

}

if command

Note: The opening brace must be on the same line.

While Loops

While loops in expect language must use braces to contain the expression like this:

#!/usr/bin/expect -f

set NUM 0

while { $NUM <= 5 } {

puts "\nNumber is $NUM"

set NUM [ expr $NUM + 1 ]

}

puts ""

while loop

For Loops

To make a for loop in expect, three fields must be specified, like the following format:

#!/usr/bin/expect -f

for {set NUM 0} {$NUM <= 5} {incr NUM} {

puts "\nNUM = $NUM"

}

puts ""

for loop

User-defined Functions

You can define a function using proc like this:

proc myfunc { TOTAL } {

set TOTAL [expr $TOTAL + 1]

return "$TOTAL"

}

And you can use them after that.

#!/usr/bin/expect -f

proc myfunc { TOTAL } {

set TOTAL [expr $TOTAL + 1]

return "$TOTAL"

}

set NUM 0

while {$NUM <= 5} {

puts "\nNumber $NUM"

set NUM [myfunc $NUM]

}

puts ""

user-defined functions

Interact Command

Sometimes your Expect script contains some sensitive information that you don’t want to share with other users who use your Expect scripts, like passwords or any other data, so you want your script to take this password from you and continuing automation normally.

The interact command reverts the control back to the keyboard.

When this command is executed, Expect will start reading from the keyboard.

This shell script will ask about the password as shown:

#!/bin/bash

echo "Hello, who are you?"

read $REPLY

echo "What is you password?"

read $REPLY

echo "What is your favorite topic?"

read $REPLY

Now we will write the Expect script that will prompt for the password:

#!/usr/bin/expect -f

set timeout -1

spawn ./questions

expect "Hello, who are you?\r"

send -- "Hi Im Adam\r"

expect "*password?\r"

interact ++ return

send "\r"

expect "*topic?\r"

send -- "Technology\r"

expect eof

interact command

After you type your password type ++ and the control will return back from the keyboard to the script.

Expect language is ported to many languages like C#, Java, Perl, Python, Ruby and Shell with almost the same concepts and syntax due to its simplicity and importance.

Expect scripting language is used in quality assurance, network measurements such as echo response time, automate file transfers, updates, and many other uses.

I hope you now supercharged with some of the most important aspects of Expect command, autoexpect command and how to use it to automate your tasks in a smarter way.

Thank you.

0

How to write practical shell scripts

In the last post, we talked about regular expressions and we saw how to use them in sed and awk for text processing, and we discussed before Linux sed command and awk command. During the series, we wrote small shell scripts, but we didn’t mix things up, I think we should take a small step further and write a useful shell script. However, the scripts in this post will help you to empower your scriptwriting skills. You can send messages to someone by phone or email, but one method, not commonly used anymore, is sending a message directly to the user’s terminal. We are going to build a bash script that will send a message to a user who is logged into the Linux system. For this simple shell script, only a few functions are required. Most of the required commands are common and have been covered in our series of shell scripting; you can review the previous posts.

Continue Reading →

Sending Messages

First, we need to know who is logged in. This can be done using the who command which retrieves all logged in users.

who

shell scripts who command

To send a message you need the username and his current terminal.

You need to know if messages are allowed or not for that user using the mesg command.

mesg

mesg command

If the result shows “is y” that means messaging is permitted. If the result shows “is n”, that means messaging is not permitted.

To check any logged user message status, use the who command with -T option.

who -T

If you see a dash (-) that means messages are turned off and if you see plus sign (+) that means messages are enabled.

To allow messages, type mesg command with the “y” option like this

mesg y

allow messages

Sure enough, it shows “is y” which means messages are permitted for this user.

Of course, we need another user to be able to communicate with him so in my case I’m going to connect to my PC using SSH and I’m already logged in with my user, so we have two users logged onto the system.

Let’s see how to send a message.

Write Command

The write command is used to send messages between users using the username and current terminal.

For those users who logged into the graphical environment (KDE, Gnome, Cinnamon or any), they can’t receive messages. The user must be logged onto the terminal

We will send a message to testuser user from my user likegeeks like this:

write testuser pts/1

write command

Type the write command followed by the user and the terminal and hit Enter.

When you hit Enter, you can start typing your message. After finishing the message, you can send the message by pressing the Ctrl+D key combination which is the end of file signal. I recommend you to review the post about signals and jobs.

Receive message

The receiver can recognize which user on which terminal sends the message. EOF means that the message is finished.

I think now we have all the parts to build our shell script.

Creating The Send Script

Before we create our shell script, we need to determine whether the user we want to send a message to him is currently logged on the system, this can be done using the who command to determine that.

logged=$(who | awk -v IGNORECASE=1 -v usr=$1 '{ if ($1==usr) { print $1 }exit }')

We get the logged in users using the who command and pipe it to awk and check if it is matching the entered user.

The final output from the awk command is stored in the variable logged.

Then we need to check the variable if it contains something or not:

if [ -z $logged ]; then

echo "$1 is not logged on."

echo "Exit"

exit

fi

I recommend you to read the post about the if statement and how to use it Bash Script.

Check logged user

The logged variable is tested to check if it is a zero or not.

If it is zero, the script prints the message, and the script is terminated.

If the user is logged, the logged variable contains the username.

Checking If The User Accepts Messages

To check if messages are allowed or not, use the who command with -T option.

check=$(who -T | grep -i -m 1 $1 | awk '{print $2}')

if [ "$check" != "+" ]; then

echo "$1 disable messaging."

echo "Exit"

exit

fi

Check message allowed

Notice that we use the who command with -T. This shows a (+) beside the username if messaging is permitted. Otherwise, it shows a (-) beside the username, if messaging is not permitted.

Finally, we check for a messaging indicator if the indicator is not set to plus sign (+).

Checking If Message Was Included

You can check if the message was included or not like this:

if [ -z $2 ]; then

echo "Message not found"

echo "Exit"

exit

fi

Getting the Current Terminal

Before we send a message, we need to get the user current terminal and store it in a variable.

terminal=$(who | grep -i -m 1 $1 | awk '{print $2}')

Then we can send the message:

echo $2 | write $logged $terminal

Now we can test the whole shell script to see how it goes:

$ ./senderscript likegeeks welcome

Let’s see the other shell window:

Send message

Good!  You can now send simple one-word messages.

Sending a Long Message

If you try to send more than one word:

$ ./senderscript likegeeks welcome to shell scripting

One word message

It didn’t work. Only the first word of the message is sent.

To fix this problem, we will use the shift command with the while loop.

shift

while [ -n "$1" ]; do

message=$message' '$1

shift

done

And now one thing needs to be fixed, which is the message parameter.

echo $whole_message | write $logged $terminal

So now the whole script should be like this:

If you try now:

$ ./senderscript likegeeks welcome to shell scripting

Complete message

Awesome!! It worked. Again, I’m not here to make a script to send the message to the user, but the main goal is to review our shell scripting knowledge and use all the parts we’ve learned together and see how things work together.

Monitoring Disk Space

Let’s build a script that monitors the biggest top ten directories.

If you add -s option to the du command, it will show summarized totals.

$ du -s /var/log/

The -S option is used to show the subdirectories totals.

$ du -S /var/log/

du command

You should use the sort command to sort the results generated by the du command to get the largest directories like this:

$ du -S /var/log/ | sort -rn

sort command

The -n to sort numerically and the -r option to reverse the order so it shows the bigger first.

The N command is used to label each line with a number:

sed '{11,$D; =}' |

sed 'N; s/\n/ /' |

Then we can clean the output using the awk command:

awk '{printf $1 ":" "\t" $2 "\t" $3 "\n"}'

Then we add a colon and a tab so it appears much better.

$ du -S /var/log/ |

sort -rn |

sed '{11,$D; =}' |

# pipe the first result for another one to clean it

sed 'N; s/\n/ /' |

# formated printing using printf

awk '{printf $1 ":" "\t" $2 "\t" $3 "\n"}'

Format output with sed and awk

Suppose we have a variable called  MY_DIRECTORIES that holds 2 folders.

MY_DIRECTORIES=”/home /var/log”

We will iterate over each directory from MY_DIRECTORIES variable and get the disk usage using du command.

So the shell script will look like this:

Monitor disk usage

Good!! Both directories /home and /var/log are shown on the same report.

You can filter files, so instead of calculating the consumption of all files, you can calculate the consumption for a specific extension like *.log or whatever.

One thing I have to mention here, in production systems, you can’t rely on disk space report instead, you should use disk quotas.

Quota package is specialized for that, but here we are learning how bash scripts work.

Again the shell scripts we’ve introduced here is for showing you how shell scripting work, there are a ton of ways to implement any task in Linux.

My post is finished! I tried to reduce the post length and make everything as simple as possible, hope you like it.

Keep coming back. Thank you.

0

Ubuntu 19.10 LZ4 sıkıştırma sayesinde daha hızlı başlatma sağlayacak

Ubuntu’nun çekirdek ekibi, açılış zamanlarını hızlandırmak için Ubuntu 19.10’dan itibaren LZ4 çekirdek kalıp sıkıştırmasına geçmeye karar verdi. Ubuntu geliştiricileri, çekirdek kalıbı için farklı sıkıştırma seçeneklerini değerlendirdikten sonra initramf’ler için desteklenen mimarilerde LZ4’ü kullanmaya karar verdi. Daha yavaş rotasyonel depolamada bile, LZ4’ün çok daha hızlı sıkıştırma süreleri sağladığı söyleniyor. Canonical’dan Colin Ian King; sıkıştırma zamanı bakımından LZ4’ün, GZIP’ten 7 kat ve LZO’dan ~ 1.25 kat daha hızlı olduğunu belirtti. Yavaş dönen medya ve yavaş CPU ile bile, LZ4 çekirdeğinin daha hızlı olduğunu belirten Ian King; sonuç olarak çok daha hızlı açma süresinin üstesinden gelebildiğini söyledi.

Continue Reading →

Ian King; medya hızlandıkça, GZIP, LZ4 ve LZO arasındaki yükleme süresi farkının azalacağını ve sıkıştırma süresinin net kazananı LZ4 ile baskın hız faktörü ortaya çıkar diye konuştu. Colin Ian King’in konuya ilişkin olarak yazdığı yazıyı burada bulabilirsiniz.

0