less spurious warnings at shutdown

* the storageserver didn't like getting the TERM signal both from
  runserver (via killpg) and sentinel, so it would print a warning
  to stderr.  But the warning didn't end with a newline.
* the line-splitter used by config-sentinel didn't handle input
  that didn't end with newline before EOF well, so the warning
  was never handled and sent to the vespa.log file earlier.
* only print warning if too many signals seen (> 2), and end
  it with a newline.
* don't ignore last byte of input if we can avoid it.

1 files changed, 2 insertions, 2 deletions

diff --git a/storageserver/src/apps/storaged/storage.cpp b/storageserver/src/apps/storaged/storage.cpp
index 8eb955ae930..1d84a73d1ed 100644
--- a/storageserver/src/apps/storaged/storage.cpp
+++ b/storageserver/src/apps/storaged/storage.cpp
@@ -129,9 +129,9 @@ namespace {
             if (sigtramp == 0) _exit(EXIT_FAILURE);
             // note: this is not totally safe, sigtramp is not protected by a lock
             sigtramp->handleSignal(sig);
-        } else {
+        } else if (_G_signalCount > 2) {
             fprintf(stderr, "Received another shutdown signal %u while "
-                    "shutdown in progress (count=%u)",
+                    "shutdown in progress (count=%u)\n",
                     sig, _G_signalCount);
         }
     }