From: "Michael Kintzios" <michaelkintzios@lycos.co.uk>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] X without console log window?
Date: Mon, 13 Feb 2006 14:23:20 -0000 [thread overview]
Message-ID: <E409A0EB8A569347802C508C49C13439072FD2@BCV0X134EXC0003> (raw)
In-Reply-To: <20060213133341.7c2f89b4.hilse@web.de>
> -----Original Message-----
> From: Hans-Werner Hilse [mailto:hilse@web.de]
> Sent: 13 February 2006 12:34
> To: gentoo-user@lists.gentoo.org
> Subject: Re: [gentoo-user] X without console log window?
>
> > What's the purpose of this window? What is it meant to log
> - as far as
> > I can tell it just stays empty . . .
>
> That depends. It usually just outputs what is piped into
> /dev/xconsole.
> If nothing is piped in there, it won't display anything. But in most
> cases the syslog daemon is configured to output some message classes,
> if not all, to this device as well (additional to outputting
> to the log
> file and /dev/console). So it depends on syslog configuration whether
> syslog messages show up here. Other programs w/ the corresponding
> rights on /dev/xconsole can pipe their stuff there, too, of course.
Would you mind showing a default/typical/custom (whatever) config file
so that I can compare with mine?
--
Regards,
Mick
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-13 16:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 21:08 [gentoo-user] X without console log window? Urs Schuetz
2006-02-11 14:47 ` Hans-Werner Hilse
2006-02-11 20:52 ` Urs Schuetz
2006-02-13 11:24 ` Michael Kintzios
2006-02-13 12:33 ` Hans-Werner Hilse
2006-02-13 14:23 ` Michael Kintzios [this message]
2006-02-13 18:15 ` Hans-Werner Hilse
2006-02-13 23:28 ` [gentoo-user] " Mick
2006-02-15 20:20 ` Mick
2006-02-16 11:54 ` Hans-Werner Hilse
2006-02-22 11:49 ` Michael Kintzios
2006-02-22 22:39 ` [gentoo-user] " Mick
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=E409A0EB8A569347802C508C49C13439072FD2@BCV0X134EXC0003 \
--to=michaelkintzios@lycos.co.uk \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox