From d00386fc0b1cb57473ebbac73b1b7737825c2131 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Tue, 14 Jan 2020 14:29:02 +0100 Subject: [PATCH 1/4] man: add commas and reword a sentence On more careful reading, "exit status ... do not cause the unit to enter a failure state" is not gramatically or logically correct. --- man/systemd.scope.xml | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/man/systemd.scope.xml b/man/systemd.scope.xml index e4de2b0fd0..b624ac5f93 100644 --- a/man/systemd.scope.xml +++ b/man/systemd.scope.xml @@ -46,14 +46,14 @@ Control Group Interfaces for an introduction on how to make use of scope units from programs. - Note that unlike service units scope units have no "main" process, all processes in the scope are - equivalent. The lifecycle of the scope unit is thus not bound to the lifetime of one specific process but - to the existance of any processes in the scope. This also means that the exit status of these processes - do not cause the scope unit to enter a failure state. Scope units may still enter a failure state, for - example due to resource exhaustion or stop timeouts being reached, but not due to programs inside of them - terminating uncleanly. Since processes managed as scope units generally remain children of the original - process that forked them off it's also the job of that process to collect their exit statuses and act on - them as needed. + Note that, unlike service units, scope units have no "main" process: all processes in the scope are + equivalent. The lifecycle of the scope unit is thus not bound to the lifetime of one specific process, + but to the existence of at least one process in the scope. This also means that the exit statuses of + these processes are not relevant for the scope unit failure state. Scope units may still enter a failure + state, for example due to resource exhaustion or stop timeouts being reached, but not due to programs + inside of them terminating uncleanly. Since processes managed as scope units generally remain children of + the original process that forked them off, it is also the job of that process to collect their exit + statuses and act on them as needed. From 48f60ea9ad2e4b5fe634491e78ec9f2afae88644 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Tue, 14 Jan 2020 21:25:52 +0100 Subject: [PATCH 2/4] docs: remove markup from title Github uses a different background for backticked text, and this stands out (in a bad way) on the title page. --- docs/UIDS-GIDS.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/UIDS-GIDS.md b/docs/UIDS-GIDS.md index e70c23a362..ab26bc15f7 100644 --- a/docs/UIDS-GIDS.md +++ b/docs/UIDS-GIDS.md @@ -1,10 +1,10 @@ --- -title: Users, Groups, UIDs and GIDs on `systemd` Systems +title: Users, Groups, UIDs and GIDs on systemd Systems category: Concepts layout: default --- -# Users, Groups, UIDs and GIDs on `systemd` Systems +# Users, Groups, UIDs and GIDs on systemd Systems Here's a summary of the requirements `systemd` (and Linux) make on UID/GID assignments and their ranges. From 4e96d758f883f34eac1df3d8b38d65c6c0d693d1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Tue, 14 Jan 2020 21:35:24 +0100 Subject: [PATCH 3/4] docs: update old para with links to the blog stories They are of historical interest, but without links not very useful. --- docs/index.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/index.md b/docs/index.md index 0368417184..df50144752 100644 --- a/docs/index.md +++ b/docs/index.md @@ -8,8 +8,6 @@ systemd provides aggressive parallelization capabilities, uses socket and D-Bus Other parts include a logging daemon, utilities to control basic system configuration like the hostname, date, locale, maintain a list of logged-in users and running containers and virtual machines, system accounts, runtime directories and settings, and daemons to manage simple network configuration, network time synchronization, log forwarding, and name resolution. -See the introductory blog story and three status updates for a longer introduction. Also see the [Wikipedia article](https://en.wikipedia.org/wiki/systemd). - --- {% assign by_category = site.pages | group_by:"category" %} @@ -24,3 +22,8 @@ See the introductory blog story and three status updates for a longer introducti {% endif %} {% endfor %} +## See also + +* [Introductory blog story](http://0pointer.de/blog/projects/systemd.html) +* [Three](http://0pointer.de/blog/projects/systemd-update.html) [status](http://0pointer.de/blog/projects/systemd-update-2.html) [updates](http://0pointer.de/blog/projects/systemd-update-3.html) +* The [Wikipedia article](https://en.wikipedia.org/wiki/systemd). From 6af0a044280857eee753b05445579e1c09f09f60 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Tue, 14 Jan 2020 21:35:44 +0100 Subject: [PATCH 4/4] docs: add the systemd output example It is still nice... --- docs/index.md | 64 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 64 insertions(+) diff --git a/docs/index.md b/docs/index.md index df50144752..2795bc4e86 100644 --- a/docs/index.md +++ b/docs/index.md @@ -27,3 +27,67 @@ Other parts include a logging daemon, utilities to control basic system configur * [Introductory blog story](http://0pointer.de/blog/projects/systemd.html) * [Three](http://0pointer.de/blog/projects/systemd-update.html) [status](http://0pointer.de/blog/projects/systemd-update-2.html) [updates](http://0pointer.de/blog/projects/systemd-update-3.html) * The [Wikipedia article](https://en.wikipedia.org/wiki/systemd). + +
+Welcome to Fedora 20 (Heisenbug)!
+
+[  OK  ] Reached target Remote File Systems.
+[  OK  ] Listening on Delayed Shutdown Socket.
+[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
+[  OK  ] Reached target Paths.
+[  OK  ] Reached target Encrypted Volumes.
+[  OK  ] Listening on Journal Socket.
+         Mounting Huge Pages File System...
+         Mounting POSIX Message Queue File System...
+         Mounting Debug File System...
+         Starting Journal Service...
+[  OK  ] Started Journal Service.
+         Mounting Configuration File System...
+         Mounting FUSE Control File System...
+[  OK  ] Created slice Root Slice.
+[  OK  ] Created slice User and Session Slice.
+[  OK  ] Created slice System Slice.
+[  OK  ] Reached target Slices.
+[  OK  ] Reached target Swap.
+         Mounting Temporary Directory...
+[  OK  ] Reached target Local File Systems (Pre).
+         Starting Load Random Seed...
+         Starting Load/Save Random Seed...
+[  OK  ] Mounted Huge Pages File System.
+[  OK  ] Mounted POSIX Message Queue File System.
+[  OK  ] Mounted Debug File System.
+[  OK  ] Mounted Configuration File System.
+[  OK  ] Mounted FUSE Control File System.
+[  OK  ] Mounted Temporary Directory.
+[  OK  ] Started Load Random Seed.
+[  OK  ] Started Load/Save Random Seed.
+[  OK  ] Reached target Local File Systems.
+         Starting Recreate Volatile Files and Directories...
+         Starting Trigger Flushing of Journal to Persistent Storage...
+[  OK  ] Started Recreate Volatile Files and Directories.
+         Starting Update UTMP about System Reboot/Shutdown...
+[  OK  ] Started Trigger Flushing of Journal to Persistent Storage.
+[  OK  ] Started Update UTMP about System Reboot/Shutdown.
+[  OK  ] Reached target System Initialization.
+[  OK  ] Reached target Timers.
+[  OK  ] Listening on D-Bus System Message Bus Socket.
+[  OK  ] Reached target Sockets.
+[  OK  ] Reached target Basic System.
+         Starting Permit User Sessions...
+         Starting D-Bus System Message Bus...
+[  OK  ] Started D-Bus System Message Bus.
+         Starting Login Service...
+         Starting Cleanup of Temporary Directories...
+[  OK  ] Started Permit User Sessions.
+[  OK  ] Started Cleanup of Temporary Directories.
+         Starting Console Getty...
+[  OK  ] Started Console Getty.
+[  OK  ] Reached target Login Prompts.
+[  OK  ] Started Login Service.
+[  OK  ] Reached target Multi-User System.
+
+Fedora release 20 (Heisenbug)
+Kernel 3.9.2-200.fc18.x86_64 on an x86_64 (console)
+
+fedora login:
+