Within X, how can I see console messages?

[Loren M. Lang]

On Sat, Feb 05, 2005 at 10:40:19AM -0600, John wrote:
> On Sat, Feb 05, 2005 at 02:51:34AM -0800, Loren M. Lang wrote:
> > On Fri, Feb 04, 2005 at 12:01:06PM -0500, Steven Friedrich wrote:
> > > I know I can Control-Alt-F1 to go back to the console, but is there a way to 
> > > see these messages in an xterm or something?
> > 
> > In addition to xconsole, there is a command dmesg which outputs the last
> > 4k of messages.  I run it if I suspect a problem and didn't have
> > xconsole running.  dmesg|tail helps limit the amount of messages.
> 
> OK - I have the opposite problem.  I have xconsole being started
> by xdm, which I like - that way I have the console messages visible
> even if no-one is logged in, and that's good.

Edit the xdm config files in /usr/X11R6/lib/X11/xdm which deal with
xdm loggin in and out to kill xconsole before it logs the user in.
There is a script in there that is run when the server start, a user
logs in, and out, etc.  Then if you need xconsole in kde, you can start
it on your own and kde will manage running it on every login.

> 
> My problem is that kde notices that I have an xconsole, and wants
> to start one on it's own when I log in.  The one xdm starts is
> persistent, though, so when kde tries to start it, too, and I always
> get one "xconsole <2>" that says "Console log for "[host] twice.
> 
> I'm using kde 3.3.2 and I don't remember this happening with 
> some previous versions.
> 
> I wasn't going to bug anyone, as everything works ok, and this is
> really just a minor annoyance, but since the subject of
> xconsole came up, I thought I'd ask.
> -- 
> 
> John Lind
> john at starfire.MN.ORG

-- 
I sense much NT in you.
NT leads to Bluescreen.
Bluescreen leads to downtime.
Downtime leads to suffering.
NT is the path to the darkside.
Powerful Unix is.

Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc
Fingerprint: B3B9 D669 69C9 09EC 1BCD  835A FAF3 7A46 E4A3 280C