Autosave: 2024-06-21 07:00:04
This commit is contained in:
parent
007b9984d3
commit
a730d75f72
3 changed files with 6 additions and 1 deletions
BIN
.zk/notebook.db
BIN
.zk/notebook.db
Binary file not shown.
|
@ -27,3 +27,7 @@ processes. In this instance the child becomes an orphan. When this occurs in
|
||||||
#Linux, the orphan process is adopted by `init`.
|
#Linux, the orphan process is adopted by `init`.
|
||||||
|
|
||||||
## Related notes
|
## Related notes
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
|

|
||||||
|
|
|
@ -19,7 +19,8 @@ the parent of all processes: PID1. Whilst it does a lot of its work in quick
|
||||||
succession at boot time it is not limited to the this stage of the lifescycle
|
succession at boot time it is not limited to the this stage of the lifescycle
|
||||||
but runs continuously in reponse to new user events.
|
but runs continuously in reponse to new user events.
|
||||||
|
|
||||||
On Linux systems `systemd` is used to implement `init`.
|
On Linux systems `systemd` is used to implement `init` and therefore `systemd`
|
||||||
|
will always be listed as the first process (PID1)
|
||||||
|
|
||||||
`systemd` is directly accessible from user space and provides a straightforward
|
`systemd` is directly accessible from user space and provides a straightforward
|
||||||
way to enable/disable, start/stop system level processes
|
way to enable/disable, start/stop system level processes
|
||||||
|
|
Loading…
Add table
Reference in a new issue