fixes gramm mistakes and adds extra chapters
This commit is contained in:
parent
a2c821a4f1
commit
10a5c587a7
|
@ -198,7 +198,7 @@ You can use `htop` as well to send signals!
|
||||||
Have a try at this with the same long list of sleep command and not the behavior of the processes.
|
Have a try at this with the same long list of sleep command and not the behavior of the processes.
|
||||||
By stopping and continuing a process you can probably explain me what the `S` column means now no?
|
By stopping and continuing a process you can probably explain me what the `S` column means now no?
|
||||||
|
|
||||||
## Nohup and disown
|
## Disown
|
||||||
|
|
||||||
Up until now all of the commands and examples should work in both `bash` and `zsh`.
|
Up until now all of the commands and examples should work in both `bash` and `zsh`.
|
||||||
To test the following command I advise you to take a `bash` shell because it's [posix](https://en.wikipedia.org/wiki/POSIX) compliant.
|
To test the following command I advise you to take a `bash` shell because it's [posix](https://en.wikipedia.org/wiki/POSIX) compliant.
|
||||||
|
@ -305,6 +305,10 @@ The practice will explain it a lot better than some codeblocks.
|
||||||
Now why is the process only changing parent once the original parent terminates?
|
Now why is the process only changing parent once the original parent terminates?
|
||||||
I'm asking you to look for an answer online but the solution can be found the realm of *signals*, especially the *hang up* [signal](https://en.wikipedia.org/wiki/SIGHUP).
|
I'm asking you to look for an answer online but the solution can be found the realm of *signals*, especially the *hang up* [signal](https://en.wikipedia.org/wiki/SIGHUP).
|
||||||
|
|
||||||
|
## Nohup
|
||||||
|
|
||||||
|
TODO
|
||||||
|
|
||||||
## Zombie processes
|
## Zombie processes
|
||||||
|
|
||||||
Yes, there are such things as zombie processes.
|
Yes, there are such things as zombie processes.
|
||||||
|
@ -376,7 +380,7 @@ Why do you think this is?
|
||||||
|
|
||||||
### Renice
|
### Renice
|
||||||
|
|
||||||
Nice values are that practical if we need to set them before we start a process no?
|
Nice values are not that practical if we need to set them before we start a process no?
|
||||||
That's where the `renice` program comes into play.
|
That's where the `renice` program comes into play.
|
||||||
It allows us to change the nice value of a running process with a very simple syntax.
|
It allows us to change the nice value of a running process with a very simple syntax.
|
||||||
I would advise you to use `sudo` when changing the nice values because otherwise you'll constantly run into either `operation not permitted` or `permission denied` errors.
|
I would advise you to use `sudo` when changing the nice values because otherwise you'll constantly run into either `operation not permitted` or `permission denied` errors.
|
||||||
|
@ -392,6 +396,10 @@ I would advise you to use `sudo` when changing the nice values because otherwise
|
||||||
➜ ~ git:(master) ✗
|
➜ ~ git:(master) ✗
|
||||||
```
|
```
|
||||||
|
|
||||||
|
## /proc virtual filesystem
|
||||||
|
|
||||||
|
TODO
|
||||||
|
|
||||||
## Exercises
|
## Exercises
|
||||||
|
|
||||||
To help you understand what happens to running and stopped processes I made a few python scripts you can download below.
|
To help you understand what happens to running and stopped processes I made a few python scripts you can download below.
|
||||||
|
|
Loading…
Reference in New Issue