Clear Signals
Instead of just killing processes, professionals cleverly catch their communication and steer the computer's tasks in the right direction using signals.
|
Kirsty Pargeter, 123RF
Instead of just killing processes, professionals cleverly catch their communication and steer the computer's tasks in the right direction using signals.
In most cases, kill is used as a last resort. It ends a process without mercy. Systems administrators sometimes kill a process with the kill -9 <PID> command – using the signal 9, which means kill even if the signal is not catchable or ignorable) and the process ID (PID) argument. You can get the PID by using the ps command.
The standard Linux signals are listed in Table 1. Related systems, such as FreeBSD, have their own variations, with the signals 1, 3, 9, and 15 being the only uniform ones throughout.
You can determine which of the two methods your system uses with kill -l . You can use the kill command in the format kill -<number> <PID> or kill -s <signal_name> <PID> . When using the signal name, you don't need the preceding SIG , so you can either do:
[...]
Pages: 4
Programming loops allow one-time or multiple execution of instructions. The condition for the loop can exist both outside and inside it.
With the snazzy little program GNU Parallel, you can make use of the full power of your multicore CPUs through scripts.
Keeping an eye on possible changes to the filesystem can prove very beneficial. It can also help you to automate many processes.
With a small script, you can convert large amounts of scanned text into PDF files that you can then browse with typical Linux tools – all thanks to OCR.
Both init and systemd can be used to start, monitor, and shut down services on Linux systems, but these utilities differ in terms of configuration and operation.
© 2025 Linux New Media USA, LLC – Legal Notice