Open-source News

Alibaba Proposes A Group Balancer For The Linux Kernel Scheduler  Phoronix

France loves open source so much, even its cinema borks have Linux behind the scenes  The Register

The Linux kernel could soon be 50 to 80% faster to build  CNX Software

A decade old patch is set to be mainlined in the upcoming Linux 5.17 that has been carried by Google's Chrome OS kernel build for years and can help with security on Linux systems not relying upon systemd's udev...

Is Maui Shell the future of the Linux desktop?  TechRepublic

Is Maui Shell the future of the Linux desktop?  TechRepublic

Git is an indispensable part of the code-sharing development workflow. Be you a beginner or an expert, this powerful version control system is the first thing you are expected to learn when working with open source code. You don't need to know everything under the sun when it comes to Git, but knowing specific hacks makes sharing your code a lot easier on platforms like GitLab, so you can collaborate with developers far and near. If there's something you're not sure about, git --help can come to your rescue.

read more

Anyone can get started in programming. We all started somewhere, and you don't need to have a computer science background to learn to code. That's the power of Linux and open source—anyone can learn a bit of coding.

If you want to learn a new programming language, we have several great articles to get you started. Below are a few of our most popular articles to help you.

read more

What is CloudReady? Is it a Viable Alternative to Chrome OS?  It's FOSS

Embedded Real-Time Operating Systems for IoT Market to Witness Widespread Expansion during 2022-2028 – Linux, Amperex Technology Ltd. (ATL), IXYS Corporation – Industrial IT  Industrial IT

It was nearly one year ago that Arm announced the Armv9 architecture as the successor to ARMv8 that was introduced a decade ago. Since then Arm has been working on adding Armv9 support to the open-source compilers such as GCC and LLVM/Clang. That initial Armv9 support has been in place for months now while on the LLVM/Clang today it received support for Armv9.3-A as the latest iteration...

Splitting files on Linux by context  Network World

PinePhone official keyboard case is finally available to purchase  XDA Developers

K-12 Mobile Computing Shipments Operating system Market Size, Scope, Forecast to 2029 | Key Players – Windows, Mac OS, Linux, iOS, Chrome OS, Android – Industrial IT  Industrial IT

Embedded Linux Market Recovery and Impact Analysis Report – Mitsubishi, Advantech, Mentor Graphics – Industrial IT  Industrial IT

AMD Threadripper 3990X + RX 5700 XT System76 Thelio Major Performance After 2 Years  Phoronix

Next month marks two years since AMD introduced the Ryzen Threadripper 3990X 64-core / 128-thread processor. All of our testing of the 3990X on Linux over the past two years has been with the System76 Thelio Major, which continues holding up well with that US-assembled workstation with hand-crafted enclosure from Colorado. With System76 having recently released Pop!_OS 21.10 as the latest update to their Ubuntu Linux derived operating system and upcoming two year anniversary of the 3990X, it made for an interesting time to see how the performance of the Ryzen Threadripper 3990X and Radeon RX 5700 XT within that workstation has evolved.

Cleaning up the Linux kernel's 'Dependency Hell': This developer is proposing 2,200 commit changes  ZDNet

This is a classic article written by Jack Wallen from the Linux.com archives. For more great SysAdmin tips and techniques check out our free intro to Linux course.

Picture this: You’ve launched an application (be it from your favorite desktop menu or from the command line) and you start using that launched app, only to have it lock up on you, stop performing, or unexpectedly die. You try to run the app again, but it turns out the original never truly shut down completely.

What do you do? You kill the process. But how? Believe it or not, your best bet most often lies within the command line. Thankfully, Linux has every tool necessary to empower you, the user, to kill an errant process. However, before you immediately launch that command to kill the process, you first have to know what the process is. How do you take care of this layered task? It’s actually quite simple…once you know the tools at your disposal.

Let me introduce you to said tools.

The steps I’m going to outline will work on almost every Linux distribution, whether it is a desktop or a server. I will be dealing strictly with the command line, so open up your terminal and prepare to type.

Locating the process

The first step in killing the unresponsive process is locating it. There are two commands I use to locate a process: top and ps. Top is a tool every administrator should get to know. With top, you get a full listing of currently running process. From the command line, issue top to see a list of your running processes (Figure 1).

Figure 1: The top command gives you plenty of information.

From this list you will see some rather important information. Say, for example, Chrome has become unresponsive. According to our top display, we can discern there are four instances of chrome running with Process IDs (PID) 3827, 3919, 10764, and 11679. This information will be important to have with one particular method of killing the process.

Although top is incredibly handy, it’s not always the most efficient means of getting the information you need. Let’s say you know the Chrome process is what you need to kill, and you don’t want to have to glance through the real-time information offered by top. For that, you can make use of the ps command and filter the output through grep. The ps command reports a snapshot of a current process and grep prints lines matching a pattern. The reason why we filter ps through grep is simple: If you issue the ps command by itself, you will get a snapshot listing of all current processes. We only want the listing associated with Chrome. So this command would look like:

ps aux | grep chrome

The aux options are as follows:

• a = show processes for all users

• u = display the process’s user/owner

• x = also show processes not attached to a terminal

The x option is important when you’re hunting for information regarding a graphical application.

When you issue the command above, you’ll be given more information than you need (Figure 2) for the killing of a process, but it is sometimes more efficient than using top.

Figure 2: Locating the necessary information with the ps command. Killing the process

Now we come to the task of killing the process. We have two pieces of information that will help us kill the errant process:

• Process name
• Process ID

Which you use will determine the command used for termination. There are two commands used to kill a process:

• kill – Kill a process by ID
• killall – Kill a process by name

There are also different signals that can be sent to both kill commands. What signal you send will be determined by what results you want from the kill command. For instance, you can send the HUP (hang up) signal to the kill command, which will effectively restart the process. This is always a wise choice when you need the process to immediately restart (such as in the case of a daemon). You can get a list of all the signals that can be sent to the kill command by issuing kill -l. You’ll find quite a large number of signals (Figure 3).

Figure 3: The available kill signals.

The most common kill signals are:

Signal Name

Single Value

Effect

SIGHUP

1

Hangup

SIGINT

2

Interrupt from keyboard

SIGKILL

9

Kill signal

SIGTERM

15

Termination signal

SIGSTOP

17, 19, 23

Stop the process

What’s nice about this is that you can use the Signal Value in place of the Signal Name. So you don’t have to memorize all of the names of the various signals.
So, let’s now use the kill command to kill our instance of chrome. The structure for this command would be:

kill SIGNAL PID

Where SIGNAL is the signal to be sent and PID is the Process ID to be killed. We already know, from our ps command that the IDs we want to kill are 3827, 3919, 10764, and 11679. So to send the kill signal, we’d issue the commands:

kill -9 3827 kill -9 3919 kill -9 10764 kill -9 11679

Once we’ve issued the above commands, all of the chrome processes will have been successfully killed.

Let’s take the easy route! If we already know the process we want to kill is named chrome, we can make use of the killall command and send the same signal the process like so:

killall -9 chrome

The only caveat to the above command is that it may not catch all of the running chrome processes. If, after running the above command, you issue the ps aux|grep chrome command and see remaining processes running, your best bet is to go back to the kill command and send signal 9 to terminate the process by PID.

Ending processes made easy

As you can see, killing errant processes isn’t nearly as challenging as you might have thought. When I wind up with a stubborn process, I tend to start off with the killall command as it is the most efficient route to termination. However, when you wind up with a really feisty process, the kill command is the way to go.

The post Classic SysAdmin: How to Kill a Process from the Linux Command Line appeared first on Linux Foundation.

Starting off a new year Intel's open-source compute stack developers have published the Intel Graphics Compiler (IGC) 1.0.9933 release that is used for their OpenCL / oneAPI Level Zero support on Linux and also used by their graphics driver on Windows...