DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: David Christensen <dpchrist@holgerdanske.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt boot messages
Date: Mon, 09 Jul 2012 08:34:34 +0200	[thread overview]
Message-ID: <4FFA7B7A.2030101@gmail.com> (raw)
In-Reply-To: <4FFA5DEA.4040607@holgerdanske.com>

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

      reply	other threads:[~2012-07-09  6:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09  4:28 [dm-crypt] dm-crypt boot messages David Christensen
2012-07-09  6:34 ` Milan Broz [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FFA7B7A.2030101@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=dpchrist@holgerdanske.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox