Linux Tips • Page 11 of 115 • Getting you up to speed!

Monitor Wireless Link Quality

If you’ve ever had issues with your wireless connection, and many of us have, you might have wanted to monitor wireless link quality. This is a good task for an article, so let’s learn together one way to monitor wireless link quality. This will be a pretty easy article to follow.

You need a wireless adapter and wireless connection to follow along with this article. It’s not complicated, but you will need those things. Even if you don’t use wireless often, you might want to learn how to monitor the link’s quality – just in case you’re put in a position where you’re using wireless. It’s better to be prepared!

Wireless connectivity issues have plagued many people. Some of those people will jump to it being a hardware problem, like a driver acting up. They’ll try all sorts of things before checking the link quality. I’d suggest checking link quality early on in the troubleshooting process.

If you don’t know, wireless signal strength is measured in decibel milliwatts (dBm). They’re measured between 0 and -100 dBm. In this case, higher is better. -30 is perfect and -90 is disconnected. In simple terms, -30 is closer to 0. I don’t have a great connection, but it’s adequate.

We won’t need to install any tools for this exercise. You have everything you need already installed and enabled, or you should. These are fairly basic low-level commands. They’ll be a part of any major distro for regular desktop use.

So, what will we be using?

The watch command:

The watch command is used with other applications, allowing you to monitor the process and to get continually updated information from that command. For example, the following command will watch your memory usage:

watch free -h

1	watch free -h

If you check the man page (with man watch), you’ll see that this is the correct tool for the job. You’ll also see that it’s not that difficult to learn how to use the watch command.

I’ve not yet written a watch article, but it’s pretty basic. In this case, we’ll introduce the -n flag but that’s just an indicator of frequency. You could simply use the watch command without any flag and it’ll refresh every two seconds. So, there’s that.

If you want to verify that watch is installed before going further, just run this:

which watch

1	which watch

The output should match this:

$ which watch
/usr/bin/watch

1 2	$ which watch /usr/bin/watch

Which is where these sorts of things belong.

By the way, I’ve covered the which command before:

Find A Command’s Binary

You could also use the ‘whereis’ command.

Another Way To Find The Binary For A Specific Command

See? Lots of information is available.

The cat Command:

We’ll also be using the cat command. The cat command is used to show the text in a file. When used in conjunction with the watch command, you can monitor a file to see if it changes. That’s exactly what we’ll be doing in this article.

Once again, you can check the man page ( man cat) for more information, but doing so will show you that the cat command is described as such:

cat – concatenate files and print on the standard output

The cat command is also useful for linking things together, such as the content from multiple files. We’re just concerned with the standard output (that’s what shows up in your terminal) and printing to said standard output.

You can verify that cat is installed with:

which cat

which cat

Of course, the output is:

$ which cat
/usr/bin/cat

1 2	$ which cat /usr/bin/cat

You can also read:

A Quick Look At The Cat Command

It’s not something you should have to install. Any desktop (or server) is going to include these two commands by default. They’re considered basic building blocks of a POSIX-compliant system. That’s something we all want!

Those are the only two tools you’ll need if you want to …

Monitor Wireless Link Quality:

If the commands mentioned in the intro section weren’t enough of a clue, this is one of those things you do in the terminal. That’s also something your distro came equipped with. Most folks should be able to open their default terminal emulator by pressing CTRL + ALT + T.

With your terminal open, you can check the current status of your wireless connection’s link quality. You simply need to run the following command:

cat /proc/net/wireless

1	cat /proc/net/wireless

That output is just for a single snapshot in time. If you’re having connectivity issues, you may want to monitor the state of your wireless connection over time. That’s why we use the watch command.

In its basic form, a command to monitor wireless link quality would look like:

watch cat /proc/net/wireless

1	watch cat /proc/net/wireless

That will run the cat /proc/net/wireless command every two seconds and output the results to your terminal (that is standard output). That’s all you need.

Of course, you can change that watch command a bit to change the frequency. You can make it more or less frequent, but the syntax is simple.

watch -n <time_in_seconds> cat /proc/net/wireless

1	watch -n <time_in_seconds> cat /proc/net/wireless

A reasonable interval might be every 10 seconds. That looks like this:

watch -n 10 cat /proc/net/wireless

1	watch -n 10 cat /proc/net/wireless

Every ten seconds, your system will run the command and output the results to the terminal you used to run said command. It’s quite basic, I’d think.

While you probably don’t want to do so for this command, you could use decimal values. If you wanted the command to run 5 times every second, your input would be:

watch -n 0.2 cat /proc/net/wireless

1	watch -n 0.2 cat /proc/net/wireless

Here’s an example of that command. Yes, I made you a video!

The quality of the link is as a percentage. No, I do not know why. If you know why, leave a comment. The noise is measured according to dBm. If you’ve ever heard the expression ‘signal to noise ratio’ this is a good example of this. You want more signal and less noise, so you want a higher signal-to-noise ratio – which is something people often get backward when used conversationally.

This just shows you something you can do with just two basic Linux commands. That’s just two commands that you have installed already and you can use them to monitor wireless link quality. There’s nothing fancy here. There’s nothing advanced here. You can perform this sort of troubleshooting without any additional applications being installed – and you probably should do so if you’re having wireless connectivity issues.

Oh, before I forget, you can exit the watch command by pressing CTRL + C. That’s about all you’ll really need to know.

Closure:

One of the reasons why I wrote this article was because I wanted to show something that looks advanced but isn’t. This isn’t something that requires much. You only need the tools you have installed already. These tools are going to be available on any Linux desktop (and server) you are likely to touch.

It also seems like a good idea to share how you can monitor wireless link quality in the Linux terminal. It’s something everyone can do and it’s something you can remember easily enough. If you’re having wireless issues, check to ensure that you have a good signal. It’s as basic as checking to make sure the power cord is plugged in and the device is turned on.

Don’t forget that you can sponsor an article. LOL You can do this even without something to promote. It’d pretty much be a donation, but you’d get a cool message and a link to almost anything you want. (If it’s just a donation and a personal thing, you can do so for much cheaper than the listed price.) I’m hoping to turn this sponsorship thing into a thing, meaning no more of the ads folks are used to and block.

Thanks for reading! If you want to help, or if the site has helped you, you can donate, register to help, write an article, or buy inexpensive hosting to start your site. If you scroll down, you can sign up for the newsletter, vote for the article, and comment.

How To: Lock Out A User Account

This will probably be a short article and one that’s not all that complicated as we discuss how to lock out a user account. Unless you’re a fairly advanced home user, this probably won’t be of much interest to you. If you’re looking to advance your career and work in IT, this will be more valuable to you.

I’ve somehow covered creating a new user twice. I’ll link to one article:

How To: Create A New User

That’s the most recent version. The first one was a couple of years prior, so you can see why there’d be a duplicate. That’s a long time and that’s a whole lot of articles between the two. It happens.

Let’s say you’re firing Peter because Peter has been drinking on the job. You’d work in tandem with human resources and security. What you’d do is you’d wait for Peter to be called into HR and then you’d lock out Peter’s account. You wouldn’t delete it yet, you’d just prevent him from logging in. After that and Peter’s official firing, security would escort him out of the building.

Then again, you could have a shared server with someone. That someone might be acting fishy and you might want to take time to check on their account. That’s when you lock out a user account. You lock out the account (killing any processes owned by them) and do your investigation.

In short, there are a bunch of excellent reasons why you’d want to lock out a user account. Knowing how to do so is just good security. Knowing when to do so is just good administration. So, let’s learn to do so…

The passwd Command:

The tool we’ll be using is one that you certainly have installed by default. You won’t need to install anything fancy. Your version of Linux will come with the appropriate account management tools.

That tool? That tool is the passwd command. You can verify that passwd is properly installed with the following command:

which passwd

1	which passwd

The output should probably match this:

$ which passwd
/usr/bin/passwd

1 2	$ which passwd /usr/bin/passwd

If you check the man page (with man passwd) you’ll see that there are plenty of options but it’s nothing too complicated. Assuming you’ve generated a spare user account, you can play around with the various commands in a mostly harmless way. Mostly…

We’re interested in the -l flag. You can also just use the --lock flag if you prefer to spell it out. Both flags will perform the same. I suppose you can use the longer flag if you’re sharing the command with other people. That way they’ll have an idea of what the command is doing.

Sponsorship:

This article is sponsored by Hilkom Digital

Most website owners realize the value of search engine optimization (SEO) within their website. You may have put a lot of effort into it, but bad links could still be lingering and affecting your rankings. These links can make Google punish your website and lower your search engine ranking, which means fewer people will visit your website. What’s a bad link? How can you find them, clean them up, and get your site back on track?

With our free service, you do not need to take any action by yourself, let experts handle all the tasks for you. We will scan all the backlinks that point to your site and remove only the most harmful ones, the links that have a high spam score, and high toxicity, and links that come from penalized or non-ranking sites. We will send you complete instructions on how to upload the clean-up file to Google, so you won`t have to share any access details with us. Once uploaded, the clean-up is complete and your site ranks will start recovering its ranks in Google in just a few weeks.

Click to Get Your Free Backlinks Report

Lock Out A User Account:

You will need an open terminal, of course. If you’re in a position where you’re going to lock out a user account, you probably already know how to access the terminal. If not, most of you can just press CTRL + ALT + T to open up your terminal.

To lock out a user account, the syntax is simple:

sudo passwd -l <username>

1	sudo passwd -l <username>

Or, as mentioned above, you can use -lock instead:

sudo passwd --lock <username>

1	sudo passwd --lock <username>

For example, you can lock that Peter dude out easily:

sudo passwd -l peter

1	sudo passwd -l peter

If it turns out that Peter wasn’t to blame, or your co-admin wasn’t doing anything fishy, you can easily undo this. This is one of the reasons why you don’t delete the account immediately. If you lock the account, you can undo it. If you delete the account, it’s a whole lot of work to recreate it beyond just basic account creation.

To do that whole unlock a user account, the syntax is pretty much the same. This time around, we’re using the -u flag. Of course, you can use the --unlock flag if you prefer.

Again, the syntax is simple:

sudo passwd -u <username>

1	sudo passwd -u <username>

Or, if you prefer to spell it out:

sudo passwd --unlock <username>

1	sudo passwd --unlock <username>

Using the aforementioned Peter above, an example would look like this:

sudo passwd -u peter

1	sudo passwd -u peter

I’m sure you know that all user accounts must be in lowercase letters. It follows that these commands are also case-sensitive. Linux is like that. Case matters a great deal in Linux. Unless you’ve set up some sort of alias, CD is not the same as cd. So, remember that in your Linux travels!

Closure:

If you ever need to know how to lock out a user account, you can refer to this article. You should be able to easily find it using the search function here on the site. It seemed like a good topic to write about and a good time to test the sponsorship features.

That’s right. The astute among you will have noticed some sponsorship. Those same astute people may have noticed that you’re not seeing any other ads. Funding the site is not essential, but it is nice. We’ve got to pay the bills one way or another. Right now, I shoulder most of those bills. ‘Snot like folks donate consistently (or often, for that matter). So, we’ll try this sponsorship for a while and see how things go. If you don’t like sponsored content, you can just skip that section of the page.

View Disk Usage

This article might seem like it has been written before but this is an entirely new way to view disk usage. To write this article I had to write two other articles. Tell me that that doesn’t sound like fun!

So, let’s see here… And, yes, I’m aware that they’re not disks anymore.

Yup. It’s official. There are too many ways to view disk usage in Linux – especially in the terminal. Why am I writing yet another article on the subject of disk usage? Because I can! I love showing how there are many ways to do the same thing in Linux. This is great because you can pick and use your favorite methods.

As for the subject of monitoring disk usage…

Monitor Disk Usage With GDU
Show Disk Usage With ‘ncdu’
A Few Ways To Visualize Disk Usage In Linux
How To: Check Disk Usage With ‘df’
Yet Another Way To Check Filesystem Space Use

Those are just the first five links when I searched for ‘disk usage’. That’s just five ways to check disk usage in Linux. I’m willing to bet that we can easily come up with five more ways to do this.

What’s special about this way of viewing disk usage?

Well, today we’ll be monitoring your drive space with a tool written in Python. You’ll need to enable PIP, a Python packaging tool. Once you’ve done that, this is universal. It will work in any distro that supports PIP – which, as you’ll see, is just about every major distro on the planet.

Read the following before going further:

Install Python’s PIP Part One
Install Python’s PIP Part Two

If you haven’t already installed Python’s PIP, this article will be of no use to you. You’ll need PIP enabled to proceed. You should also add the $PATH as defined in the second article. From here on out, the article will assume you’ve done both of those things.

View Disk Usage With Vizex:

The tool we’ll be using is known as Vizex. You can see the Vizex project page here. If you bother going there, you’ll see that Vizex is indeed the correct tool for the job. You’ll see that this is (one of the many) correct tools for the job.

vizex is the terminal program for the UNIX/Linux systems which helps the user to visualize the disk space usage for every partition and media on the user’s machine. vizex is highly customizable and can fit any user’s taste and preferences.

Hmm… It is at this point that I noticed that they don’t capitalize it. I’m going to capitalize it because it’s keeping the system from saying I didn’t spell it properly.

Anyhow, as you’re using PIP, you’ll need an open terminal. You can use your GUI to open your terminal. On many systems, just press CTRL + ALT + T and your default terminal will open.

To install Vizex, run the following command:

pip install vizex

1	pip install vizex

If you’ve never installed a Python package with PIP before, then be sure to keep an eye on the screen. It’s a fascinating process and watching stuff happen in the terminal is pretty sweet!

Now that you have Vizex installed, you simply run that command in the terminal. If you didn’t follow the 2nd part of the Python PIP article you’ll have to specify the path. That’s just silly. Follow the 2nd article (it’s really easy) and you don’t have to deal with that.

Using Vizex:

Anyhow, that command is simply:

vizex

vizex

It will even color-code your drives. If they’re close to full, they’ll be red and blink (missed in the screenshot below). If you’re moderately full, they’ll be listed in the yellow. I wanted to use Vizex to view a computer will all sorts of drives, so I did! That’s how you ended up with this screenshot:

If that isn’t one of the easiest ways to view disk usage, I don’t know what is. This is just one of the many reasons why you should have Python’s PIP installed. There’s a bunch of software that’s available if you just know where to look. It took a while, but I finally got around to sharing this information. In my defense, it did take a couple of articles to share it properly.

Closure:

There are all sorts of ways to view disk usage. This is just another way, though it’s an interesting way. I’m quite sure that I’ll cover this very same subject again in another article. For now, I’ve covered a way to do so with Python and that’s something different than you’ve previously seen on the site.

I may not place ads on the site and just opt to accept sponsored articles as a way to cover the bills. That seems like a good thing to do. Some stuff may already be in the works, so look for that in the future. If you’re interested in sponsoring an article, be sure to hit me up. We get good traffic and rank well in the search engines. So, get some extra traffic and some SEO benefits by sponsoring an article!

Mastering Efficiency: Unleashing the Power of Bash Aliases

In the realm of command-line prowess, efficiency is king, such as Bash aliases. Every keystroke saved is a victory, and every shortcut mastered is a step toward domination over the terminal.

Among the arsenal of tools at your disposal, one weapon stands out as a champion of efficiency: Bash aliases. These humble shortcuts can transform your command-line experience from mundane to magnificent, allowing you to wield the power of complex commands with the simplicity of a single word.

Join us on a journey as we delve into the world of Bash aliases and unlock their full potential.

What are Bash Aliases?

Bash aliases are custom shortcuts or abbreviations that you can create to simplify and speed up your command-line tasks. They allow you to define your own commands or override existing ones with your preferred options or parameters.

Think of them as your personal command-line assistant, ready to execute your commands at a moment’s notice.

Why Use Bash Aliases?

The benefits of Bash aliases are manifold:

Speed: With aliases, you can execute complex commands with just a few keystrokes, saving valuable time and effort.
Simplicity: Long and convoluted commands can be distilled into concise aliases, making your command-line interactions more intuitive and less error-prone.
Customization: Aliases are highly customizable, allowing you to tailor your command-line environment to suit your specific needs and preferences.
Productivity: By automating repetitive tasks, aliases can significantly boost your productivity and streamline your workflow.

How to Create Bash Aliases

Creating Bash aliases is a breeze. Open your .bashrc file, located in your home directory, using your favorite text editor (such as Nano). Then, add your alias definitions to the file using the following syntax:

alias shortcut='command'

1	alias shortcut='command'

Replace shortcut with the alias you want to create and command with the command you want to associate with the alias. For example:

alias ll='ls -alF'

1	alias ll='ls -alF'

This alias allows you to list all files in the current directory in a long listing format with file details.

Once you’ve added your aliases, save the .bashrc file and either restart your terminal or run source ~/.bashrc to apply the changes.

Examples of Useful Bash Aliases

Here are some examples of useful Bash aliases to get you started:

# Navigation
alias ..='cd ..'
alias ...='cd ../..'
alias ....='cd ../../..'

# Listing
alias ls='ls --color=auto'
alias ll='ls -alF'

# Git
alias gs='git status'
alias ga='git add'
alias gc='git commit'
alias gp='git push'

# Navigation

alias ..='cd ..'

alias ...='cd ../..'

alias ....='cd ../../..'

# Listing

alias ls='ls --color=auto'

alias ll='ls -alF'

# Git

alias gs='git status'

alias ga='git add'

alias gc='git commit'

alias gp='git push'

Best Practices for Bash Aliases

To make the most of Bash aliases, keep the following best practices in mind:

Choose meaningful names: Use descriptive names for your aliases to make them easy to remember and understand.
Avoid overriding existing commands: Be cautious when overriding existing commands with aliases to prevent confusion and unintended consequences.
Document your aliases: Consider adding comments to your .bashrc file to document your aliases and their purposes for future reference.
Stay organized: Group related aliases together and organize them logically within your .bashrc file for easier management.

Conclusion

In the fast-paced world of the command line, efficiency reigns supreme. Bash aliases empower you to wield the full power of the terminal with unparalleled speed and simplicity.

By mastering the art of aliases, you can elevate your command-line prowess to new heights and easily conquer even the most daunting tasks. So go forth, fellow command-line warriors, and unleash the power of Bash aliases upon the digital realm!

Can you tell that this was written by AI? The prompt I used for this was:

Write an article about Bash Aliases in the style of linux-tips.us.

It didn’t do very well at nailing my style and it used a lot of headers. It also rambled on quite a bit, but I do that too. I’m not sure how much time this saved. I still had to do quite a bit of formatting. A simple cut-and-paste would not match the mostly consistent formatting I have used as of late. That meant quite a bit of formatting.

I also ran the article through Grammarly. It’s too bad that they won’t accept me into the affiliate program. I quite like what they do for my writing. They make me look almost literate!

Install Python’s PIP Part Two

This article may also seem a bit unusual because I covered how to install Python’s PIP in the last article. This article is the second part of that. This is something that seemed like it should be two articles, so it is two articles.

Additionally, I share this information so that I can write future articles. So, by themselves, these two articles won’t accomplish much by themselves. They will come in handy for future reference and that’s the point of this.

In the previous article about how to install Python’s PIP, you learned the basics. In that article, you learned how to install PIP. That’s all well and good, but then you might be confused when you go to install a package installed by PIP.

During the package installation, you may see a warning that looks like this:

Consider adding this directory to PATH

1	Consider adding this directory to PATH

This is because PIP installs the packages somewhere like your ~/local/.bin directory. If you then try to run the package from the terminal, it won’t be found.

For the record, this is for people using Bash. I’m not sure about other shells.

You can still use PIP packages just fine, you just have to specify the path. That’s a pain in the butt and not something you should have to do. Instead, we’re going to add the path as suggested. If you’ve done that, you can just type the package name into the terminal to run your PIP-installed Python applications.

So, let’s do that…

Install Python’s PIP Part Two:

By now it should be obvious that this requires an open terminal. You did read the first article, right? As such, you can usually open your terminal with your keyboard, simply press CTRL + ALT + T, and your default terminal should open.

With your terminal open, we need to add some text to your ~/.bashrc file that sets the path. It’s pretty straightforward and we’ll be using Nano for this. Click that link if you’re not sure if you have Nano installed.

Let’s open the file for editing with this command:

nano ~/.bashrc

1	nano ~/.bashrc

Then scroll to the bottom.

At the bottom, add a new line.

Copy and paste the following:

# Python PIP Path
export PATH=$PATH:/home/$USER/.local/bin

1 2	# Python PIP Path export PATH=$PATH:/home/$USER/.local/bin

Next, we save the changes and exit Nano by pressing CTRL + X, then Y, and then ENTER on your keyboard.

No changes will have been made just yet. You could reboot or reload your desktop session if you wanted, but you can tell the shell to reload the file and thus have the changes take effect. To do that, you’d enter this:

source ~/.bashrc

1	source ~/.bashrc

At that point, you can install PIP packages and have them run when you just type the command into the terminal. There’s no need to add anything else to the command. This sets the path that PIP was complaining about.

And now you’re ready to install Python PIP packages. This is an important step after you install Python’s PIP. It should serve you well, assuming you want Python packages installed in a pretty simple manner.

IMPORTANT: Read Part 1 to install Python’s PIP.

Closure:

As you can tell by the length, there’s a reason that this is a second article. I’ll have to remember to edit the first article when this article gets published. It’s not that it’s complicated, it’s just long.

So, it seemed best to turn this into a second article – especially because it’s not technically a necessary step. You can comfortably run Python packages by using the file path, but this is much easier.