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