Fossil SCM
Tiny tweaks to the systemd doc
Commit
0835ec45a481d4ecca9e4434609a58d8ba79495baa21e7bb3ac0c37430a0b398
Parent
faffd271927ee6e…
1 file changed
+1
-3
+1
-3
| --- www/server/debian/service.md | ||
| +++ www/server/debian/service.md | ||
| @@ -203,17 +203,15 @@ | ||
| 203 | 203 | |
| 204 | 204 | [Install] |
| 205 | 205 | WantedBy=multi-user.target |
| 206 | 206 | ``` |
| 207 | 207 | |
| 208 | -We’ll explain the “`@`” in the file name below. | |
| 209 | - | |
| 210 | 208 | Notice that we haven’t told `systemd` which user and group to run Fossil |
| 211 | 209 | under. Since this is a system-level service definition, that means it |
| 212 | 210 | will run as root, which then causes Fossil to [automatically drop into a |
| 213 | 211 | `chroot(2)` jail](../../chroot.md) rooted at the `WorkingDirectory` |
| 214 | -we’ve configured above, shortly each `fossil http` call starts. | |
| 212 | +we’ve configured above, shortly after each `fossil http` call starts. | |
| 215 | 213 | |
| 216 | 214 | The `Restart*` directives we had in the user service configuration above |
| 217 | 215 | are unnecessary for this method, since Fossil isn’t supposed to remain |
| 218 | 216 | running under it. Each HTTP hit starts one Fossil instance, which |
| 219 | 217 | handles that single client’s request and then immediately shuts down. |
| 220 | 218 |
| --- www/server/debian/service.md | |
| +++ www/server/debian/service.md | |
| @@ -203,17 +203,15 @@ | |
| 203 | |
| 204 | [Install] |
| 205 | WantedBy=multi-user.target |
| 206 | ``` |
| 207 | |
| 208 | We’ll explain the “`@`” in the file name below. |
| 209 | |
| 210 | Notice that we haven’t told `systemd` which user and group to run Fossil |
| 211 | under. Since this is a system-level service definition, that means it |
| 212 | will run as root, which then causes Fossil to [automatically drop into a |
| 213 | `chroot(2)` jail](../../chroot.md) rooted at the `WorkingDirectory` |
| 214 | we’ve configured above, shortly each `fossil http` call starts. |
| 215 | |
| 216 | The `Restart*` directives we had in the user service configuration above |
| 217 | are unnecessary for this method, since Fossil isn’t supposed to remain |
| 218 | running under it. Each HTTP hit starts one Fossil instance, which |
| 219 | handles that single client’s request and then immediately shuts down. |
| 220 |
| --- www/server/debian/service.md | |
| +++ www/server/debian/service.md | |
| @@ -203,17 +203,15 @@ | |
| 203 | |
| 204 | [Install] |
| 205 | WantedBy=multi-user.target |
| 206 | ``` |
| 207 | |
| 208 | Notice that we haven’t told `systemd` which user and group to run Fossil |
| 209 | under. Since this is a system-level service definition, that means it |
| 210 | will run as root, which then causes Fossil to [automatically drop into a |
| 211 | `chroot(2)` jail](../../chroot.md) rooted at the `WorkingDirectory` |
| 212 | we’ve configured above, shortly after each `fossil http` call starts. |
| 213 | |
| 214 | The `Restart*` directives we had in the user service configuration above |
| 215 | are unnecessary for this method, since Fossil isn’t supposed to remain |
| 216 | running under it. Each HTTP hit starts one Fossil instance, which |
| 217 | handles that single client’s request and then immediately shuts down. |
| 218 |