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 E62701383DE for ; Fri, 11 Jan 2013 00:55:05 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DB47421C013; Fri, 11 Jan 2013 00:54:48 +0000 (UTC) Received: from mail-ie0-f180.google.com (mail-ie0-f180.google.com [209.85.223.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0ED9F21C001 for ; Fri, 11 Jan 2013 00:53:18 +0000 (UTC) Received: by mail-ie0-f180.google.com with SMTP id c10so1654985ieb.25 for ; Thu, 10 Jan 2013 16:53:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding; bh=0Zdx8H+8OedRt6B3JLHTBxsZla9OQiuIPjbQxiz52lA=; b=kFijTpqjKJLExYY0M03WgvB4dYAxwVsBIn1JgVLZhwf5BcIaq1/l1Qy7u1DZSSZ+9T d+AUoz4vbuxWPffF17O8sLbyPyRwuLYNjXrL4dqFB8glCAea39QwohXIMdYtRhb7/Y94 k8AuTP2YQvhae7s2O9agWj/5qhh2ZXAmPLawwOiDbL1OpoqEL44C5Z0VHInEjmkKRg78 ESMxTWL83XPfcO5T22gu50E2x1OTYEBt6gbyObm5CAPySi9Cn2JMKZ5vHtK5KjQEWCFh FxaULOyvPP8E+gLXJqPKidhsMbmj6K7s9XHrUSF6DkSGP5ePYXU6QkKvGJzB3tuD0aOC zQbw== 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.50.5.236 with SMTP id v12mr7364262igv.6.1357865598332; Thu, 10 Jan 2013 16:53:18 -0800 (PST) Received: by 10.64.32.195 with HTTP; Thu, 10 Jan 2013 16:53:17 -0800 (PST) In-Reply-To: <201301102346.29777.robin.atwood@attglobal.net> References: <201301091812.33767.robin.atwood@attglobal.net> <201301102346.29777.robin.atwood@attglobal.net> Date: Thu, 10 Jan 2013 18:53:17 -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: 4fc1d706-6761-4679-b0ca-d9e225d78d68 X-Archives-Hash: 103e33be3b786d55e75e911cc6549c49 On Thu, Jan 10, 2013 at 10:46 AM, Robin Atwood wrote: > On Thursday 10 January 2013, Canek Pel=C3=A1ez Vald=C3=A9s wrote: > >> On Wed, Jan 9, 2013 at 5:12 AM, Robin Atwood >> wrote: > >> > I have temporarily shelved my problem with mounting since my work-arou= nd > >> > seems adequate. But I have some questions about logging. Journald work= s > >> > fine 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 > >> > have 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-processin= g. > >> > I have the correct syslog-ng service defined and syslog-ng.conf has be= en > >> > 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 t= o > >> > do 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.service > >> > >> 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. > > > > Thanks for the tips, now I can get more output to tty1 if I want. I still > can't get any systemd messages to syslog-ng, however. A bit of a mystery. Stupid question, the syslog-ng.service is running correctly? What does the following command say: systemctl status syslog-ng.service 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