Fossil SCM
added note about numeric/symbolic port-specifiers when using Fossil from (x)inetd, and reminder to enable/restart daemon after config changes
Commit
fbbf640b4e8387a42277a369b49710ea2cc32602
Parent
14302b6cc7d4278…
1 file changed
+18
-1
+18
-1
| --- www/server.wiki | ||
| +++ www/server.wiki | ||
| @@ -53,11 +53,11 @@ | ||
| 53 | 53 | </blockquote> |
| 54 | 54 | <a name="inetd"></a> |
| 55 | 55 | <h2>Fossil as an inetd/xinetd or stunnel service</h2><blockquote> |
| 56 | 56 | <p> |
| 57 | 57 | A Fossil server can be launched on-demand by inetd or xinetd using |
| 58 | -the [/help/http|fossil http] command. To launch Fossil from inetd, modify | |
| 58 | +the [/help/http|fossil http] command. To launch Fossil from inetd, modify | |
| 59 | 59 | your inetd configuration file (typically "/etc/inetd.conf") to contain a |
| 60 | 60 | line something like this: |
| 61 | 61 | <blockquote> |
| 62 | 62 | <pre> |
| 63 | 63 | 12345 stream tcp nowait.1000 root /usr/bin/fossil /usr/bin/fossil http /home/fossil/repo.fossil |
| @@ -69,10 +69,23 @@ | ||
| 69 | 69 | Obviously you will |
| 70 | 70 | need to modify the pathnames for your particular setup. |
| 71 | 71 | The final argument is either the name of the fossil repository to be served, |
| 72 | 72 | or a directory containing multiple repositories. |
| 73 | 73 | </p> |
| 74 | +<p> | |
| 75 | +For systems where the port-specification must be a symbolic name and cannot be | |
| 76 | +numeric, add the desired name and port to /etc/services, e.g.: | |
| 77 | +<blockquote> | |
| 78 | +<pre> | |
| 79 | +fossil 12345/tcp #fossil server | |
| 80 | +</pre> | |
| 81 | +</blockquote> | |
| 82 | +and use the symbolic name ('fossil' in this example) instead of the numeral ('12345') | |
| 83 | +in inetd.conf. For details, see the relevant section in your system's documentation, e.g. | |
| 84 | +the [https://www.freebsd.org/doc/en/books/handbook/network-inetd.html|FreeBSD Handbook] in | |
| 85 | +case you use FreeBSD. | |
| 86 | +</p> | |
| 74 | 87 | <p> |
| 75 | 88 | If your system is running xinetd, then the configuration is likely to be |
| 76 | 89 | in the file "/etc/xinetd.conf" or in a subfile of "/etc/xinetd.d". |
| 77 | 90 | An xinetd configuration file will appear like this:</p> |
| 78 | 91 | <blockquote> |
| @@ -96,10 +109,14 @@ | ||
| 96 | 109 | In both cases notice that Fossil was launched as root. This is not required, |
| 97 | 110 | but if it is done, then Fossil will automatically put itself into a chroot |
| 98 | 111 | jail for the user who owns the fossil repository before reading any information |
| 99 | 112 | off of the wire. |
| 100 | 113 | </p> |
| 114 | +<p> | |
| 115 | +Inetd or xinetd must be enabled, and must be (re)started whenever their configuration | |
| 116 | +changes - consult your system's documentation for details. | |
| 117 | +</p> | |
| 101 | 118 | <p> |
| 102 | 119 | [https://www.stunnel.org/ | Stunnel version 5] is an inetd-like process that |
| 103 | 120 | accepts and decodes SSL-encrypted connections. Fossil can be run directly from |
| 104 | 121 | stunnel in a manner similar to inetd and xinetd. This can be used to provide |
| 105 | 122 | a secure link to a Fossil project. The configuration needed to get stunnel5 |
| 106 | 123 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -53,11 +53,11 @@ | |
| 53 | </blockquote> |
| 54 | <a name="inetd"></a> |
| 55 | <h2>Fossil as an inetd/xinetd or stunnel service</h2><blockquote> |
| 56 | <p> |
| 57 | A Fossil server can be launched on-demand by inetd or xinetd using |
| 58 | the [/help/http|fossil http] command. To launch Fossil from inetd, modify |
| 59 | your inetd configuration file (typically "/etc/inetd.conf") to contain a |
| 60 | line something like this: |
| 61 | <blockquote> |
| 62 | <pre> |
| 63 | 12345 stream tcp nowait.1000 root /usr/bin/fossil /usr/bin/fossil http /home/fossil/repo.fossil |
| @@ -69,10 +69,23 @@ | |
| 69 | Obviously you will |
| 70 | need to modify the pathnames for your particular setup. |
| 71 | The final argument is either the name of the fossil repository to be served, |
| 72 | or a directory containing multiple repositories. |
| 73 | </p> |
| 74 | <p> |
| 75 | If your system is running xinetd, then the configuration is likely to be |
| 76 | in the file "/etc/xinetd.conf" or in a subfile of "/etc/xinetd.d". |
| 77 | An xinetd configuration file will appear like this:</p> |
| 78 | <blockquote> |
| @@ -96,10 +109,14 @@ | |
| 96 | In both cases notice that Fossil was launched as root. This is not required, |
| 97 | but if it is done, then Fossil will automatically put itself into a chroot |
| 98 | jail for the user who owns the fossil repository before reading any information |
| 99 | off of the wire. |
| 100 | </p> |
| 101 | <p> |
| 102 | [https://www.stunnel.org/ | Stunnel version 5] is an inetd-like process that |
| 103 | accepts and decodes SSL-encrypted connections. Fossil can be run directly from |
| 104 | stunnel in a manner similar to inetd and xinetd. This can be used to provide |
| 105 | a secure link to a Fossil project. The configuration needed to get stunnel5 |
| 106 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -53,11 +53,11 @@ | |
| 53 | </blockquote> |
| 54 | <a name="inetd"></a> |
| 55 | <h2>Fossil as an inetd/xinetd or stunnel service</h2><blockquote> |
| 56 | <p> |
| 57 | A Fossil server can be launched on-demand by inetd or xinetd using |
| 58 | the [/help/http|fossil http] command. To launch Fossil from inetd, modify |
| 59 | your inetd configuration file (typically "/etc/inetd.conf") to contain a |
| 60 | line something like this: |
| 61 | <blockquote> |
| 62 | <pre> |
| 63 | 12345 stream tcp nowait.1000 root /usr/bin/fossil /usr/bin/fossil http /home/fossil/repo.fossil |
| @@ -69,10 +69,23 @@ | |
| 69 | Obviously you will |
| 70 | need to modify the pathnames for your particular setup. |
| 71 | The final argument is either the name of the fossil repository to be served, |
| 72 | or a directory containing multiple repositories. |
| 73 | </p> |
| 74 | <p> |
| 75 | For systems where the port-specification must be a symbolic name and cannot be |
| 76 | numeric, add the desired name and port to /etc/services, e.g.: |
| 77 | <blockquote> |
| 78 | <pre> |
| 79 | fossil 12345/tcp #fossil server |
| 80 | </pre> |
| 81 | </blockquote> |
| 82 | and use the symbolic name ('fossil' in this example) instead of the numeral ('12345') |
| 83 | in inetd.conf. For details, see the relevant section in your system's documentation, e.g. |
| 84 | the [https://www.freebsd.org/doc/en/books/handbook/network-inetd.html|FreeBSD Handbook] in |
| 85 | case you use FreeBSD. |
| 86 | </p> |
| 87 | <p> |
| 88 | If your system is running xinetd, then the configuration is likely to be |
| 89 | in the file "/etc/xinetd.conf" or in a subfile of "/etc/xinetd.d". |
| 90 | An xinetd configuration file will appear like this:</p> |
| 91 | <blockquote> |
| @@ -96,10 +109,14 @@ | |
| 109 | In both cases notice that Fossil was launched as root. This is not required, |
| 110 | but if it is done, then Fossil will automatically put itself into a chroot |
| 111 | jail for the user who owns the fossil repository before reading any information |
| 112 | off of the wire. |
| 113 | </p> |
| 114 | <p> |
| 115 | Inetd or xinetd must be enabled, and must be (re)started whenever their configuration |
| 116 | changes - consult your system's documentation for details. |
| 117 | </p> |
| 118 | <p> |
| 119 | [https://www.stunnel.org/ | Stunnel version 5] is an inetd-like process that |
| 120 | accepts and decodes SSL-encrypted connections. Fossil can be run directly from |
| 121 | stunnel in a manner similar to inetd and xinetd. This can be used to provide |
| 122 | a secure link to a Fossil project. The configuration needed to get stunnel5 |
| 123 |