| 1 |
commit: e6015978f8ee88ffadcdfaacc0d3c8b78ff02ba9 |
| 2 |
Author: Anthony G. Basile <blueness <AT> gentoo <DOT> org> |
| 3 |
AuthorDate: Sat Jul 4 14:15:52 2015 +0000 |
| 4 |
Commit: Anthony G. Basile <blueness <AT> gentoo <DOT> org> |
| 5 |
CommitDate: Sat Jul 4 14:15:52 2015 +0000 |
| 6 |
URL: https://gitweb.gentoo.org/proj/grss.git/commit/?id=e6015978 |
| 7 |
|
| 8 |
README: add blurb about cgroup. |
| 9 |
|
| 10 |
README | 7 ++++++- |
| 11 |
1 file changed, 6 insertions(+), 1 deletion(-) |
| 12 |
|
| 13 |
diff --git a/README b/README |
| 14 |
index c9af472..626f80d 100644 |
| 15 |
--- a/README |
| 16 |
+++ b/README |
| 17 |
@@ -70,9 +70,14 @@ Features: |
| 18 |
transcribe the steps one would manually take in a chroot in build the system |
| 19 |
into the build script, and grsrun will automatically repeat them. |
| 20 |
|
| 21 |
- * It is possible to script a GRS system to do the equivalent of catalyst runs. |
| 22 |
+ * It is possible to script a GRS system to do the equivalent of catalyst runs. |
| 23 |
[TODO: there is still one more build script directive required here, pivot_chroot.] |
| 24 |
|
| 25 |
+ * The use of Linux cgroup make management easy. There is no need to trap or |
| 26 |
+ propagate signals when writing the scripts that are to be run in the chroot. |
| 27 |
+ A simple SIGTERM to grsrun will ensure that all children process are properly |
| 28 |
+ terminated and that any bind-mounted filesystems are unmounted. |
| 29 |
+ |
| 30 |
* A GRS system acts as a "tinderbox-lite" in that build failures are reported. |
| 31 |
So as a GRS system evolves over time, as package are bumped, any breakages that |
| 32 |
are introduced will be caught and reported. |
Archives