crash_reporter_logs.conf - Issue 5814001: crash-reporter: Capture and send recent update_engine logs when it crashes

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: crash_reporter_logs.conf

Issue 5814001: crash-reporter: Capture and send recent update_engine logs when it crashes (Closed) Base URL: http://git.chromium.org/git/crash-reporter.git@master

Patch Set: Created 10 years ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

OLD	NEW
(Empty)
	1 # 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. it doesn't hurt to add a Chromium OS copyright. kmixter1 2010/12/14 03:39:49 Done. Show quoted text On 2010/12/13 19:27:57, petkov wrote: > it doesn't hurt to add a Chromium OS copyright. Done.
	2 # 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 he 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. Show quoted text On 2010/12/13 19:27:57, petkov wrote: > briefly document the format somewhere -- either her, or in the header file? a > one-liner will do. Done.
	3 # running anything that might cause another crash.

	4 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 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. Show quoted text On 2010/12/13 19:27:57, petkov wrote: > 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 Done.
	5

	6 # The following rules are only for testing purposes.

	7 crash_log_test:echo hello world

	8 crash_log_recursion_test:sleep 1 && /home/autotest/tests/crash_log_recursion_tes t

OLD	NEW

« crash_collector_test.cc ('K') | « crash_collector_test.cc ('k') | crash_sender » ('j') | user_collector.cc » ('J')