crash-reporter: Capture and send recent update_engine logs when it crashes

crash_reporter_logs.conf

Index: crash_reporter_logs.conf
diff --git a/crash_reporter_logs.conf b/crash_reporter_logs.conf
new file mode 100644
index 0000000000000000000000000000000000000000..221554dfb8b57b36aacd01875ddb103bb1a1b0e2
--- /dev/null
+++ b/crash_reporter_logs.conf
@@ -0,0 +1,8 @@
+# Be careful to only run common unix commands here as these commands

[petkov, 2010/12/13 19:27:57]

it doesn't hurt to add a Chromium OS copyright.

[kmixter1, 2010/12/14 03:39:49]

Done.

+# will be run when a crash has recently occurred and we should avoid

[petkov, 2010/12/13 19:27:57]

briefly document the format somewhere -- either her, or in the header file? a
one-liner will do.

[kmixter1, 2010/12/14 03:39:49]

Done.

+# running anything that might cause another crash.
+update_engine:tail -c 50000 /var/log/update_engine.log

[petkov, 2010/12/13 19:27:57]

since update engine starts a new log every time it's started, can we do
something similar to what we do for chrome:system to collect data from the last
few logs? I think the command below will include the last 5 logs, at most 50KB
total.

cat $(ls -1tr /var/log/update_engine | tail -5 | sed
s.^./var/log/update_engine/.) | tail -c 50000

[kmixter1, 2010/12/14 03:39:49]

Done.

+
+# The following rules are only for testing purposes.
+crash_log_test:echo hello world
+crash_log_recursion_test:sleep 1 && /home/autotest/tests/crash_log_recursion_test