All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: Satyam Sharma <satyam.sharma@gmail.com>,
	netdev@vger.kernel.org, hpa@zytor.com
Subject: Re: Netconsole and logging everything from /dev/console
Date: Fri, 16 Nov 2007 12:50:36 -0600	[thread overview]
Message-ID: <20071116185036.GH19691@waste.org> (raw)
In-Reply-To: <20071116174315.GA20401@deprecation.cyrius.com>

On Fri, Nov 16, 2007 at 06:43:15PM +0100, Martin Michlmayr wrote:
> I'm supporting a number of consumer devices (e.g. small NAS devices)
> in Debian.  They typically don't export the serial console and don't
> have any other output devices.  We perform the installation via SSH
> on such devices and start SSH automatically when the system boots so
> people can login.  This works pretty well but sometimes a device stops
> to boot for no good reason.  This is usually really hard to debug
> since we don't have any logs at all.
> 
> I could activate netconsole in order to see kernel messages but then I
> still wouldn't see anything that's printed by the ramdisk and later
> when services are started.  Ideally, I'd like to have an option for
> netconsole to show every message that is also shown on the console.
> 
> Do you think that would be possible?

It is, definitely, you just need to wire up a tty struct's write
method to netconsole's and add it to the console registration. But I
haven't had any time to work on this in a while.

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2007-11-16 18:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-16 17:43 Netconsole and logging everything from /dev/console Martin Michlmayr
2007-11-16 18:50 ` Matt Mackall [this message]
2007-11-17 19:31   ` Martin Michlmayr
  -- strict thread matches above, loose matches on Subject: below --
2008-10-30 14:39 Ferenc Wagner
2008-10-30 15:16 ` Martin Michlmayr

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=20071116185036.GH19691@waste.org \
    --to=mpm@selenic.com \
    --cc=hpa@zytor.com \
    --cc=netdev@vger.kernel.org \
    --cc=satyam.sharma@gmail.com \
    --cc=tbm@cyrius.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.