What are reasonable blockers for making journald the default logger in F19?

[John.Florian at dart.biz]

> From: Lennart Poettering <mzerqung at 0pointer.de>
> On Wed, 17.10.12 10:44, Matthew Miller (mattdm at fedoraproject.org) wrote:
> > b. All utilities should always work sensibly with grep (this is not 
the
> >    case on F18 right now)
> 
> Hmm? How so? Bug?

I see this as well.  For example:

# journalctl | head
Logs begin at Wed, 17 Oct 2012 10:53:26 -0400, end at Wed, 17 Oct 2012 
13:30:01 -0400.
Oct 17 10:53:26 localhost systemd-journal[48]: Allowing runtime journal 
file....
Oct 17 10:53:26 localhost kernel: Initializing cgroup subsys cpuset
Oct 17 10:53:26 localhost kernel: Initializing cgroup subsys cpu
Oct 17 10:53:26 localhost kernel: Linux version 3.6.1-1.fc18.i686 
(mockbuil...12
Oct 17 10:53:26 localhost kernel: e820: BIOS-provided physical RAM map:
Oct 17 10:53:26 localhost kernel: BIOS-e820: [mem 
0x0000000000000000-0x0000...le
Oct 17 10:53:26 localhost kernel: BIOS-e820: [mem 
0x000000000009e000-0x0000...ed
Oct 17 10:53:26 localhost kernel: BIOS-e820: [mem 
0x00000000000f0000-0x0000...ed
Oct 17 10:53:26 localhost kernel: BIOS-e820: [mem 
0x0000000000100000-0x0000...le

Adding the -a option prevents the truncation at around column 80, but it 
shouldn't be necessary.  Seems like -a should be automatic if a pipe is 
involved.

#  rpm -qf $(which journalctl)
systemd-194-1.fc18.i686
--
John Florian

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20121017/942bea55/attachment.html>