Fossil SCM
(Typo) www/server/debian/service.md fix spelling.
Commit
f73188a5b840ce97af0f872d3563261a6bfd606fc3abcdbd263bda3751610fcc
Parent
e73731ffb777466…
1 file changed
+1
-1
+1
-1
| --- www/server/debian/service.md | ||
| +++ www/server/debian/service.md | ||
| @@ -183,11 +183,11 @@ | ||
| 183 | 183 | to the system level. We need to start this socket listener at the root |
| 184 | 184 | level because of the low-numbered TCP port restriction we brought up |
| 185 | 185 | above. |
| 186 | 186 | |
| 187 | 187 | This configuration says more or less the same thing as the socket part |
| 188 | -of an `inted` entry [exemplified elsewhere in this | |
| 188 | +of an `inetd` entry [exemplified elsewhere in this | |
| 189 | 189 | documentation](../any/inetd.md). |
| 190 | 190 | |
| 191 | 191 | Next, create the service definition file in that same directory as |
| 192 | 192 | `[email protected]`: |
| 193 | 193 | |
| 194 | 194 |
| --- www/server/debian/service.md | |
| +++ www/server/debian/service.md | |
| @@ -183,11 +183,11 @@ | |
| 183 | to the system level. We need to start this socket listener at the root |
| 184 | level because of the low-numbered TCP port restriction we brought up |
| 185 | above. |
| 186 | |
| 187 | This configuration says more or less the same thing as the socket part |
| 188 | of an `inted` entry [exemplified elsewhere in this |
| 189 | documentation](../any/inetd.md). |
| 190 | |
| 191 | Next, create the service definition file in that same directory as |
| 192 | `[email protected]`: |
| 193 | |
| 194 |
| --- www/server/debian/service.md | |
| +++ www/server/debian/service.md | |
| @@ -183,11 +183,11 @@ | |
| 183 | to the system level. We need to start this socket listener at the root |
| 184 | level because of the low-numbered TCP port restriction we brought up |
| 185 | above. |
| 186 | |
| 187 | This configuration says more or less the same thing as the socket part |
| 188 | of an `inetd` entry [exemplified elsewhere in this |
| 189 | documentation](../any/inetd.md). |
| 190 | |
| 191 | Next, create the service definition file in that same directory as |
| 192 | `[email protected]`: |
| 193 | |
| 194 |