factory_test_init: split output into verbose log and console data

factory.conf

 # Copyright (c) 2011 The Chromium OS Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 description   "Chrome OS factory startup stub"
 author        "chromium-os-dev@chromium.org"
 
 start on stopped udev-addon
 stop on starting halt or starting reboot
 
 script
   modprobe i2c-dev
   cd /usr/local/autotest
   eval $(./site_tests/suite_Factory/startx.sh)
   date >>/var/log/factory.log
   if [ ! -e factory_started ]; then
     touch factory_started
     cp -f site_tests/suite_Factory/control .
     OPT=""
   else
     OPT="-c"
   fi
-  ./bin/autotest -t factory $OPT control >>/var/log/factory.log 2>&1
+  FACTORY_LOG_FILE=/var/log/factory.log
+  CONSOLE_LOG_FILE=/var/log/factory_console.log
+  # Factory log will be uploaded so we must always preserve previous results.
+  # Console log is just for UI to display, no need to be saved across sessions;
+  # however in order to support writing by multiple processes, the file must be
+  # opened in "append" mode. So we must first delete it then use >> to append.
+  rm -f "$CONSOLE_LOG_FILE"
+  ./bin/autotest -t factory $OPT control 2>&1 |
+    tee -a "$FACTORY_LOG_FILE" |
+    grep --line-buffer "FACTORY" >>"$CONSOLE_LOG_FILE"

[jrbarnette, 2011/03/30 18:14:40]

Are you sure the pattern "FACTORY" is restrictive enough?  I'm
assuming that the string FACTORY is a prefix on the line, but
this pattern will match any line that includes FACTORY, even if
it isn't a prefix.

[Hung-Te, 2011/03/31 02:17:10]

 A sample of the data format:
01:21:28 ERROR| FACTORY: factory_ui setup done, starting gtk.main()...

 However since this is simply for "showing data on console (for operator to get
some visual feedback)", I think more is better than less.

 end script
 
 pre-stop script
   pkill python
   pkill X
 end script