As you were probably expecting, here's what was piped! =)
Any ideas what is going wrong?
Christian Lavoie
[EMAIL PROTECTED]
UIN: 947212
STDERR
Description: Binary data
STDOUT
Description: Binary data
XF86Config
Description: Binary data
Christian Lavoie writes:
[problem with capturing error messages from X server]
Christain, invoke 'script' before running 'startx'. When you get back to the
command line prompt (from startx), invoke 'exit' and everything which
appeared on your screen will be captured in a text file called 'typescr
Christian Lavoie wrote:
> I need to write down the output (actually, I need the error message) that
> the startx command gives me. (The nice 'startx >err' doesn't work...)
That's because errors go to stderr rather than stdout. All you need is:
startx > err 2>&1
> I installed the Xserver_agx (an
Christian Lavoie <[EMAIL PROTECTED]> writes:
CL> I need to write down the output (actually, I need the error
CL> message) that the startx command gives me. (The nice 'startx >err'
CL> doesn't work...)
There are two places program output can go: "standard output" and
"standard error". 'cmd >file'
On Thu, 10 Dec 1998, Christian Lavoie wrote:
> I need to write down the output (actually, I need the error message) that
> the startx command gives me. (The nice 'startx >err' doesn't work...)
>
Try:
startx >err 2>&1
That should be the correct magic incantation. :-)
Havoc
I need to write down the output (actually, I need the error message) that
the startx command gives me. (The nice 'startx >err' doesn't work...)
I installed the Xserver_agx (and all it needs) on a PS/2 system recently,
but haven't yet been able to get the X server to work
Christian Lavoie
6 matches
Mail list logo
