Much to the chagrin of those who'd like to malign the Linux operating system, it's actually quite easy to use. Thanks to modern GUI desktop environments and applications, anyone could jump into the fray and know what they're doing. 

But on the rare occasion in which trouble arises, you might want to know a few commands to help you out. Theproblem is that there are so many commands available to you within the realm of Linux, which makes it challenging to know which commands are the best options.

Also: Thefirst 5 Linux commands every new user should learn

Sure, you could learn any of the commands that display system information (such as top, free, iostat, htop, vmstat, or iftop), but those tools will only get you so far. What is more valuable is skipping to the command that can really help you if something goes wrong.

And with that introduction out of the way, let's get to the commands.

1. dmesg

Back when I first started using Linux,dmesgwas my best friend. Essentially,dmesgis used to examine all messages that are created after the bootloader phase of the kernel. In other words, you might find a clue for anything you could possibly troubleshoot right here.

Unlike thedmesgof old, you now have to run the command with sudo privileges, so:

sudo dmesg

This will print quite a bit of output you can scroll through, making it a bit challenging to find what you're looking for, and much of what you read will most likely seem like gibberish. The good news is that errors print out in red, so you can quickly scroll to find anything that might be wrong.

Also: Why I use the Linux tree command daily - and what it can do for you

There's a way to make this even easier. Let's say you're experiencing an error, and you want to see if it is logged viadmesgas it happens. To do that, issue the command:

dmesg-w

This will display the output fromdmesg as it happens, so when an error occurs, you'll see it written in the terminal window and can troubleshoot from there.

2. tail

Speaking of following output, thetailcommand allows you to follow the output written to any log file. Let's say you're having issues with your Samba share and want to see what's happening in real time. The first thing you'd want to do is find out which log file to read. In that case, you could issue the command:

ls /var/log/samba

In that folder you'll find a number of log files (for the Samba server and any/all machines connected to the share). Let's say I want to view the content of the Samba daemon log. For that, I would issue the command:

tail -f /var/log/samba/log.smbd

As the errors happen, they'll be printed in the terminal. As you can see, I have an unknown parameter in my smb.conf file, namedshare modes. I can open that file, remove the parameter, restart Samba, and the error is no more.

Remember, to get out of the tail command, you have to use the Ctrl+c keyboard combination.

3. ps

For me,psis a gateway to other commands. Thepscommand displays a snapshot of any given current process. You could usepsto list every running process or feed it togrepto list only specific processes.

But what's it good for? 

Also: Two tricks that make using the Linux command line a lot easier

Let's say you have an application that has crashed and won't close. You click that little X in the upper right (or left) corner of the window, but it just won't go away. The first thing you need to do is find the PID of that process so you can then take care of the problem. That's wherepscomes in handy. Butpsby itself isn't very helpful. Why? If you just runpsit will only list the processes associated with the terminal you're using. Instead, you need to use some specific options, which are:

ps aux

• a - all processes
• u - processes owned by the user runningps
  
• x - prints applications that have not been started from the terminal
  

This command prints out a lot of information, all of it in columns. You'll see several columns, but the ones you'll want to pay attention to are PID and COMMAND. With the information from those two columns, you can locate the process's ID causing you problems. Once you've found that process, you can then killit.

If the output ofps auxis overwhelming, you can pipe that output togrepand list only certain processes. Let's say LibreOffice is causing you problems. You can list only those processes associated with LibreOffice like this:

ps aux | grep libreoffice| grep libreoffice

4. kill

The killcommand is very powerful. When you have a stubborn application that has crashed and won't close (or hasn't crashed but is consuming too much memory), thekill command will force that application to close.

Also: The best Linux laptops of 2024: Expert tested and reviewed

But to use thekillcommand, you must first have the PID of the application in question (which you locate with theps auxcommand). Let's say the PID of a wayward LibreOffice application is 604187. To kill that process, the command would be:

kill 604187

The app should close, and you're good to go.

5. systemctl

The systemctlcommand is not only good for starting and stoping applications, it can also help you troubleshoot. Let's say Samba isn't working as expected. Issue the command:

systemctlstatus smbd

The above command will list whether the service is running, its PID, the number of associated tasks, how much memory and CPU it's using, and the CGroups to which it belongs. Even better, if there are any issues with the process,systemctl will give you the information you need to troubleshoot the problem further(usually with the help ofjournalctl). 

There you have it. These five commands will serve as a great place to start with your Linux troubleshooting. Yes, there are quite a few more tools that are available, but for those just starting with Linux, you might want to know these commands first.

Featured

Every iPhone model that will get Apple's iOS 18 (and which ones won't)

How to reset Windows 11 without losing your apps, files, and settings

These 5 work-from-home essentials seriously upgraded my desk

What is Apple Intelligence: How the iPhone's on-device and cloud-based AI will work

• Every iPhone model that will get Apple's iOS 18 (and which ones won't)
• How to reset Windows 11 without losing your apps, files, and settings
• These 5 work-from-home essentials seriously upgraded my desk
• What is Apple Intelligence: How the iPhone's on-device and cloud-based AI will work