From 2417859932f3cd92b3256b81c98eaeca445773cd Mon Sep 17 00:00:00 2001 From: worldofpeace Date: Thu, 13 Dec 2018 12:15:56 -0500 Subject: doc/breakpointHook: correct typos --- doc/stdenv.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'doc/stdenv.xml') diff --git a/doc/stdenv.xml b/doc/stdenv.xml index c54901a93ebf0..cab76ef1104c2 100644 --- a/doc/stdenv.xml +++ b/doc/stdenv.xml @@ -2500,17 +2500,17 @@ addEnvHooks "$hostOffset" myBashFunction This hook will make a build pause instead of stopping when a failure - happen. It prevents nix from cleaning up the build environment immediately and + happens. It prevents nix from cleaning up the build environment immediately and allows the user to attach to a build environment using the - cntr command. On build error it will print the - instruction that are neccessary for cntr. Installing + cntr command. Upon build error it will print + instructions on how to use cntr. Installing cntr and running the command will provide shell access to the build sandbox of failed build. At /var/lib/cntr the - sandbox filesystem is mounted. All commands and files of the system are + sandboxed filesystem is mounted. All commands and files of the system are still accessible within the shell. To execute commands from the sandbox use the cntr exec subcommand. Note that cntr also needs to be executed on the machine that is doing the build, which might - be not the case when remote builders are enabled. + not be the case when remote builders are enabled. cntr is only supported on Linux-based platforms. To use it first add cntr to your environment.systemPackages on NixOS or alternatively to -- cgit 1.4.1