commit 7afffa6447c83352b95ff91968ab2dc9ad64d38c
author Sean Dague <sean.dague@samsung.com> Sat Mar 15 13:50:36 2014 -0400
committer Sean Dague <sean.dague@samsung.com> Sat Mar 15 13:50:36 2014 -0400
tree 49ae0527c6bcf0850e6ec021d03987b666489af0
parent f10d8feca0bc5cf4d707f485bb35ecefa9e97560

change the order of the print/flush

It seems that we get a different behavior whether stdout is closed
in the parent process or not when it comes to buffering. If it's
closed we don't get the last line flushed out to the file, if it's
not closed we do. This was seen in the trove pg fail.

A complete shot in the dark, but I'd like to see if this is fixed
with being explicit with printing to the log before stdout.

Change-Id: Ie37299dbc88d549d34d85731e571a5b7ef181311

stack.sh

diff --git a/stack.sh b/stack.sh
index 09e9eec..7fa4d37 100755
--- a/stack.sh
+++ b/stack.sh
@@ -538,10 +538,10 @@
                     cmd | getline now
                     close("date +\"%Y-%m-%d %H:%M:%S.%3N | \"")
                     sub(/^/, now)
-                    print
                     print > logfile
-                    fflush("")
                     fflush(logfile)
+                    print
+                    fflush("")
                 }' ) 2>&1
         # Set up a second fd for output
         exec 6> >( tee "${SUMFILE}" )