Fossil SCM
Corrections to information about running Fossil in a chroot jail.
Commit
f1a480e130fecefc11da95418812cc10bd21a7e9
Parent
f35b46d4cb49d34…
1 file changed
+4
-3
+4
-3
| --- www/server.wiki | ||
| +++ www/server.wiki | ||
| @@ -346,15 +346,16 @@ | ||
| 346 | 346 | Note also that Linux implements "getloadavg()" by accessing the "/proc/loadavg" |
| 347 | 347 | file in the "proc" virtual filesystem. If you are running a Fossil instance |
| 348 | 348 | inside a chroot() jail on Linux, you will need to make the "/proc" file |
| 349 | 349 | system available inside that jail in order for this feature to work. On |
| 350 | 350 | the self-hosting Fossil repository, this was accomplished by adding a line |
| 351 | -to the "/etc/mtab" or "/etc/fstab" file that looks like: | |
| 351 | +to the "/etc/fstab" file that looks like: | |
| 352 | 352 | <blockquote><pre> |
| 353 | -chroot_jail_proc /home/www/proc proc r 0 0 | |
| 353 | +chroot_jail_proc /home/www/proc proc ro 0 0 | |
| 354 | 354 | </pre></blockquote> |
| 355 | -Pathnames should be adjusted for individual systems, of course. | |
| 355 | +The /home/www/proc pathname should be adjusted so that the "/proc" component is | |
| 356 | +in the root of the chroot jail, of course. | |
| 356 | 357 | <p> |
| 357 | 358 | To see if the load-average limiter is functional, visit the [/test_env] page |
| 358 | 359 | of the server to view the current load average. If the value for the load |
| 359 | 360 | average is greater than zero, that means that it is possible to activate |
| 360 | 361 | the load-average limiter on that repository. If the load average shows |
| 361 | 362 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -346,15 +346,16 @@ | |
| 346 | Note also that Linux implements "getloadavg()" by accessing the "/proc/loadavg" |
| 347 | file in the "proc" virtual filesystem. If you are running a Fossil instance |
| 348 | inside a chroot() jail on Linux, you will need to make the "/proc" file |
| 349 | system available inside that jail in order for this feature to work. On |
| 350 | the self-hosting Fossil repository, this was accomplished by adding a line |
| 351 | to the "/etc/mtab" or "/etc/fstab" file that looks like: |
| 352 | <blockquote><pre> |
| 353 | chroot_jail_proc /home/www/proc proc r 0 0 |
| 354 | </pre></blockquote> |
| 355 | Pathnames should be adjusted for individual systems, of course. |
| 356 | <p> |
| 357 | To see if the load-average limiter is functional, visit the [/test_env] page |
| 358 | of the server to view the current load average. If the value for the load |
| 359 | average is greater than zero, that means that it is possible to activate |
| 360 | the load-average limiter on that repository. If the load average shows |
| 361 |
| --- www/server.wiki | |
| +++ www/server.wiki | |
| @@ -346,15 +346,16 @@ | |
| 346 | Note also that Linux implements "getloadavg()" by accessing the "/proc/loadavg" |
| 347 | file in the "proc" virtual filesystem. If you are running a Fossil instance |
| 348 | inside a chroot() jail on Linux, you will need to make the "/proc" file |
| 349 | system available inside that jail in order for this feature to work. On |
| 350 | the self-hosting Fossil repository, this was accomplished by adding a line |
| 351 | to the "/etc/fstab" file that looks like: |
| 352 | <blockquote><pre> |
| 353 | chroot_jail_proc /home/www/proc proc ro 0 0 |
| 354 | </pre></blockquote> |
| 355 | The /home/www/proc pathname should be adjusted so that the "/proc" component is |
| 356 | in the root of the chroot jail, of course. |
| 357 | <p> |
| 358 | To see if the load-average limiter is functional, visit the [/test_env] page |
| 359 | of the server to view the current load average. If the value for the load |
| 360 | average is greater than zero, that means that it is possible to activate |
| 361 | the load-average limiter on that repository. If the load average shows |
| 362 |