From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.saout.de ([127.0.0.1]) by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F58Sw5E5G6dV for ; Mon, 9 Jul 2012 08:34:39 +0200 (CEST) Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Mon, 9 Jul 2012 08:34:38 +0200 (CEST) Received: by wgbdr13 with SMTP id dr13so11107429wgb.1 for ; Sun, 08 Jul 2012 23:34:38 -0700 (PDT) Message-ID: <4FFA7B7A.2030101@gmail.com> Date: Mon, 09 Jul 2012 08:34:34 +0200 From: Milan Broz MIME-Version: 1.0 References: <4FFA5DEA.4040607@holgerdanske.com> In-Reply-To: <4FFA5DEA.4040607@holgerdanske.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] dm-crypt boot messages List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Christensen Cc: dm-crypt@saout.de On 07/09/2012 06:28 AM, David Christensen wrote: > dm-crypt: > > Are dm-crypt boot messages written to a log? dmesg doesn't seem to have > them, and "grep -r sda1_crypt /var/log" yields nothing... Kernel dm-crypt uses standard kernel log facility, so all errors are be visible in kernel log (but it is quiet if there is no problem). Userspace (cryptsetup/LUKS) uses std out/std err it is upt to initsystem to catch these messages (e.g. plymouth or systemd does this IIRC). There is no direct option to use system syslog in cryptsetup. Milan