about summary refs log tree commit diff
path: root/corepkgs
diff options
context:
space:
mode:
authorEelco Dolstra <e.dolstra@tudelft.nl>2003-07-16T21·24+0000
committerEelco Dolstra <e.dolstra@tudelft.nl>2003-07-16T21·24+0000
commit54664b6fb74e964d70530d13e25459751d0c63fb (patch)
tree9b305d680ebec562274d718feaedf8a51c3f4b75 /corepkgs
parent335aa1c35d8835619b465df3f5629b435bac157d (diff)
* The write() system call can write less than the requested
  number of bytes, e.g., in case of a signal like SIGSTOP.  
  This caused `nix --dump' to fail sometimes.

  Note that this bug went unnoticed because the call to `nix 
  --dump' is in a pipeline, and the shell ignores non-zero 
  exit codes from all but the last element in the pipeline.  
  Is there any way to check the result of the initial elements
  in the pipeline?  (In other words, is it at all possible to 
  write reliable shell scripts?)

Diffstat (limited to 'corepkgs')
-rw-r--r--corepkgs/nar/nar.sh2
1 files changed, 2 insertions, 0 deletions
diff --git a/corepkgs/nar/nar.sh b/corepkgs/nar/nar.sh
index 059bca8ba134..a7b6be8aaa0e 100644
--- a/corepkgs/nar/nar.sh
+++ b/corepkgs/nar/nar.sh
@@ -1,3 +1,5 @@
 #! /bin/sh
 
+echo "packing $path into $out..."
 /nix/bin/nix --dump --file "$path" | bzip2 > $out || exit 1
+