From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 21A24138BD3 for ; Mon, 3 Nov 2014 00:22:43 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3E19EE08BD; Mon, 3 Nov 2014 00:22:33 +0000 (UTC) Received: from mail-lb0-f169.google.com (mail-lb0-f169.google.com [209.85.217.169]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9E8F4E089B for ; Mon, 3 Nov 2014 00:22:31 +0000 (UTC) Received: by mail-lb0-f169.google.com with SMTP id p9so2841430lbv.0 for ; Sun, 02 Nov 2014 16:22:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=lmjJf7bzmfeA5f73NgZcOOTwBF0CHZTb74AuVQuI5Jo=; b=OA09p8G+2GH0eYXICdco7dHzVTfGq3EwzMpyd4ySgBGc70h2Yx5qrSf4ixY60PwiMD AOnzMKuxhE90ozawqgdCCpsFqjqHeD7EW4F1ZC89A2DDalhwC/to6ALjy8RiB9sP0DRN E9rW3gLQjecudVUpFAqCjAR0NW7TyNMl1ta3PEwPB8r6HOv+BLCCns/k8buZAPiQK3Wv GU+UlGePvb60MIKBxbRqhn2446xCfBZAUiJUA7ZXbjQO4RqrFyhclr9n9Jed/O3VlQBQ fvxzNRTUTU8UvnyzY0xUe3ZFbiB75yd7cJg9g3ImBKlwC34Etf+GkI0hK8IceMTYv/gU /eQA== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.112.144.228 with SMTP id sp4mr45883546lbb.58.1414974150011; Sun, 02 Nov 2014 16:22:30 -0800 (PST) Received: by 10.152.22.168 with HTTP; Sun, 2 Nov 2014 16:22:29 -0800 (PST) In-Reply-To: References: <1721456.cxhDToZz1Z@andromeda> <5707050.LYlfBLMIFp@andromeda> Date: Sun, 2 Nov 2014 19:22:29 -0500 Message-ID: Subject: Re: [gentoo-user] alternative kernels From: Tom H To: Gentoo User Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 574ebd22-c744-4595-88a0-f4fbfc0a9fb8 X-Archives-Hash: 3fb27460b5c9ad7c8ba1a6c197d903ec On Fri, Oct 31, 2014 at 6:30 PM, Rich Freeman wrote: > On Fri, Oct 31, 2014 at 6:09 PM, Tom H wrote: >> The systemd line was always that if you wanted to ship your logs off >> to another box, use rsyslog. So I've never understood the embedding of >> an httpd in systemd. I guess that the httpd server's useful if if you >> want a basic send-the-logs-to-another-box-as-is, but that, if you want >> to filter or manipulate the journald output, you have to use rsyslog >> or syslog-ng. > > If you're going to implement a log manager there is no reason to not > let it export logs to a central manager. True. On second thought, I now remember that Lennart said that there was no intention to use syslog's udptcp output. So he hadn't ruled out http. And I misrepresented the systemd line. > As far as filtering/manipulating logs goes, you can do plenty of that > with journalctl already, and it supports dumping your logs in json so > you can do anything you want with them in another tool. There aren't > really any such tools around yet, but I'm sure we'll see them come up. You can filter/manipulate logs with journalctl - and nicely so - but you can't combine it with journal-gatewayd; the latter exports all the logs, as shown in the output of "journalctl". Maybe there'll be one day a tool to tweak the output of journal-gatewayd...