All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <lkml@tlinx.org>
To: linux-newbie@vger.kernel.org
Subject: way to "duplicate" console contents to a file?
Date: Sun, 04 Mar 2007 16:02:17 -0800	[thread overview]
Message-ID: <45EB5E09.2040609@tlinx.org> (raw)


Is there a way to have my console messages duplicated and saved in a file?

I know about sending messages to "console" in [n]syslogd, but I'm
looking for the ability to essentially see a _copy_ of what is on the
screen.  There are messages that pop out on the console that I'd like to
view remotely, *and*, I would like to be able to review the startup
messages after the kernel has booted and while it is going through the
RC scripts.  Occasionally (often) I have some rc script that caused some
unexpected or weird output on boot that only "spews" its output onto the
console.  Even the running of the "rc" scripts -- that output seems to
be limited to the console.

Even for info that goes to the console, I'm only partly lucky in being
able to scroll back -- sometimes can't scroll back enough, or something
on occasion mungs the part of the scrollback buffer I want to view.

It know "dmesg" and boot.[o]msg show the kernel's startup messages, but 
maybe
it's when it stop's recording to klog and switches over to syslog that info
written to the console is no longer recorded.

I'd "sorta" like a "console" file like is in boot.msg for the kernel
boot -- something that is appended to for each session, the
re-initialized.  But startup scripts and sometimes drivers and such,
_appear_ to write messages to either /dev/console, /dev/tty, or
stderr/out with it mapped to the console.

I'd prefer not to disturb the way messages are displayed on the console
so when I am in front of the computer it will appear "normal" -- but
want the ability to display those messages when logged in remotely (more
normal case).

Ideas? Clue sticks? :-)
Thanks,
Linda

-
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-05  0:02 UTC|newest]

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