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 6CCFB1383A1 for ; Wed, 9 Jan 2013 17:50:22 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C27DC21C088; Wed, 9 Jan 2013 17:49:58 +0000 (UTC) Received: from mail-ie0-f177.google.com (mail-ie0-f177.google.com [209.85.223.177]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id E833E21C021 for ; Wed, 9 Jan 2013 17:48:16 +0000 (UTC) Received: by mail-ie0-f177.google.com with SMTP id k13so2455989iea.36 for ; Wed, 09 Jan 2013 09:48:16 -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:content-transfer-encoding; bh=UnWqS7fqW9xG1xWbZnE1tGX9Mcf41iYMW2+m0GljBaE=; b=yqCYK31yUQTU0nSpgzJh+ziJpIxkhI9uzpI9xoUsH5MtAw+63KlW30is3KEAGzI/by K19DGi/iq7XWnVo3rvMDxC99betD+1/KVLI0gL3agUCRNOk8hLXSJ/HPJqEvewcp3KVy MaHwKgCNTYXcKZ9zX8z+v6KlLG6/YBlrznq+edqJC9xu4z0bvuwFMTnAUAKubnCD+9k7 Rb+XX/ZKh6XCk8A297NBW8Fc4CBZxJlAq8S5jp7Gbl5ZS62KLg/UkKpdNcrsYof51IZM fLu4kjtB89uGM1S5rXQa+lOXMBpiAuqpEbBmnbZ+NPOBzOOdCMjBUiBdYs42QoMbqglJ RYtg== 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 Received: by 10.50.33.138 with SMTP id r10mr2357504igi.6.1357753696225; Wed, 09 Jan 2013 09:48:16 -0800 (PST) Received: by 10.64.32.195 with HTTP; Wed, 9 Jan 2013 09:48:16 -0800 (PST) In-Reply-To: <201301091812.33767.robin.atwood@attglobal.net> References: <201301091812.33767.robin.atwood@attglobal.net> Date: Wed, 9 Jan 2013 11:48:16 -0600 Message-ID: Subject: Re: [gentoo-user] Questions about systemd logging From: =?UTF-8?B?Q2FuZWsgUGVsw6FleiBWYWxkw6lz?= To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 5ce63344-fdcf-40e5-aa23-e3b29f3249a9 X-Archives-Hash: f0f6ae4c2c35c11734b83da9f956eb01 On Wed, Jan 9, 2013 at 5:12 AM, Robin Atwood w= rote: > I have temporarily shelved my problem with mounting since my work-around > seems adequate. But I have some questions about logging. Journald works f= ine > but what am I supposed to see on the main console? What do you mean by "main console"? tty1? tty12? /dev/console? > All I can see is a few > kernel messages which cease after the lvm service completes. There are no > service starting messages and no login prompt appears. The other ttys hav= e a > banner and prompt as usual. systemd by default only spawns 1 (one) tty, tty1: $ ls /etc/systemd/system/getty.target.wants/ getty@tty1.service That's the only login prompt spawned by default. The other virtual consoles get spawned automatically if you switch to them. In other words, if you never switch to the virtual console 2, there is no login prompt there. It will appear until you switch to it. systemd should switch to tty1 and launch getty@tty1.service automatically when the getty.target is reached in the boot process. I'm not really sure what the problem is; if you are concerned by the "[ OK ]" messages when booting, it is possible that systemd is so fast that you have no chance to see them (that happens in my laptop with a solid state harddrive). Also, if you have a splash (like plymouth), the whole point of the splash is that you don't see said messages. You can see a copy of the "boot log" in /var/log/boot.log; that it's what you are supposed to see when booting, but if you have a splash you won't, or maybe it will be so fast that you will miss it. > Secondly I want to merge the journal into syslog-ng for post-processing. = I > have the correct syslog-ng service defined and syslog-ng.conf has been > modified to use /run/systemd/journald/syslog as a source unix-stream. But= I > see no systemd messages appearing. In the Gentoo package all the > journald.conf statements are commented out, which ones are necessary to d= o > what I want. I have tried the "logging_to_syslog/kmsg" options but to no > effect, but there are many! I switched from syslog-ng to rsyslog around three years ago, and exclusively to the journal some months ago, so this is from memory: 1. You need to link your syslog service unit to /etc/systemd/system/syslog.service; for example: /etc/systemd/system/syslog.service -> /usr/lib/systemd/system/syslog-ng.ser= vice 2. You need to set LogTarget=3Dsyslog (or LogTarget=3Dsyslog-or-kmsg) in /etc/systemd/system.conf. You are configuring *systemd* to use a third party syslog; you don't need to configure the journal itself. man 5 systemd.conf man 1 systemd If I recall correctly, that's it. systemd automatically will buffer the early boot messages until your preferred syslog service start, and from that point on it will send the logs to it immediately. Hope it helps. Regards. --=20 Canek Pel=C3=A1ez Vald=C3=A9s Posgrado en Ciencia e Ingenier=C3=ADa de la Computaci=C3=B3n Universidad Nacional Aut=C3=B3noma de M=C3=A9xico