All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <lkml@tlinx.org>
To: linux-newbie@vger.kernel.org
Subject: Re: way to "duplicate" console contents to a file?
Date: Tue, 06 Mar 2007 08:36:49 -0800	[thread overview]
Message-ID: <45ED98A1.1050300@tlinx.org> (raw)
In-Reply-To: <200703060131.13669.eric@cisu.net>

Eric Bambach wrote:
> On Sunday 04 March 2007 18:02, Linda Walsh wrote:
>   
>> Is there a way to have my console messages duplicated and saved in a file?
>>     
> Have you looked into using the serial console and some sort of secondary 
> server to capture its output? It could be easily logged and stored. Serial 
> consoles are started very early in the boot process so you would get almost 
> all kernel message just after the kernel is invoked. Its a popular kernel 
> hacker debugging method.
>   
----
May end up using that method -- it's not idea though because it's
an "either/or" solution vs. a "co-solution".  Don't need the input
redirected, so much as just a log of output.

I wonder if something like klogd would be practical.  Something that stays
active and sweeps the display buffer of the console periodically and dumps
contents to file -- something like an "auditd" for the console (in the
respect that auditd takes messages from kernel and dumps to file).

Maybe would work best if console buff was kept in memory (kernel option
to use memory to allow as scroll-back).  Even so, I suppose it should be
possible to read out of video memory as well as writing into it (?)...

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2007-03-06 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-05  0:02 way to "duplicate" console contents to a file? Linda Walsh
2007-03-06  7:31 ` Eric Bambach
2007-03-06 16:36   ` Linda Walsh [this message]
2007-03-06 16:45     ` Rajat Jain

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=45ED98A1.1050300@tlinx.org \
    --to=lkml@tlinx.org \
    --cc=linux-newbie@vger.kernel.org \
    /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.