tree 3cc1efe40df7e0e068238461b662dd3dbcf7d09a
parent c64e43ebdf03b938b3ab9a7db100e1b8b72e833b
author Mike Frysinger <vapier@chromium.org> 1380222735 -0400
committer chrome-internal-fetch <chrome-internal-fetch@google.com> 1383597896 +0000

tweak syslog error message style

The current error message format uses angle brackets like so:
2013-09-26T11:54:23.931018-07:00 localhost bootcache[3789]: bootcache /mnt/host/source/src/platform/bootcache/bootcache.c:eopen<154> open /sys/devices/virtual/block/dm-0/dm/valid: No such file or directory<2>

For kernel hackers, those angle brackets look wrong.  It implies that
some log message was incorrectly split across lines.  In reality, the
code is trying to just show some numbers.

Even then, it's a little weird.  The format is:
	progname src_file:func<lineno> error message...
But it's much more common (imo) to use the format:
	progname src_file:lineno:func error message...

So tweak the format slightly to avoid these angle brackets.  Now we have:
2013-09-26T12:22:25.853974-07:00 localhost bootcache[3753]: bootcache /mnt/host/source/src/platform/bootcache/bootcache.c:154:eopen open /sys/devices/virtual/block/dm-0/dm/valid: No such file or directory (errno=2)

BUG=None
TEST=booted a system and reviewed /var/log/messages

Change-Id: Iab08241ef2f8804981e662124044424b0279ff04
Reviewed-on: https://chromium-review.googlesource.com/170772
Reviewed-by: Don Garrett <dgarrett@chromium.org>
Reviewed-by: Luigi Semenzato <semenzato@chromium.org>
Commit-Queue: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>