RE: Piping unpipable output. [Now that it's piped]

[Christian Lavoie]

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

Re: Piping unpipable output.

[Jens B. Jorgensen]

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 21

 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

--
Jens B. Jorgensen
[EMAIL PROTECTED]

Re: Piping unpipable output.

[tko]

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 'typescript' 
in the current directory. 

-- 
-= Sent by Debian 1.3 Linux =-
Thomas Kocourek  KD4CIK 
@[EMAIL PROTECTED]@westgac3.dragon.com Remove @_@ for correct Email address
--... ...-- ...  -.. .  -.- -.. - -.-. .. -.-

Piping unpipable output.

[Christian Lavoie]

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
UIN: 947212
E-Mail: [EMAIL PROTECTED]

Re: Piping unpipable output.

[Havoc Pennington]

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 21

That should be the correct magic incantation. :-)

Havoc

Re: Piping unpipable output.

[David Z. Maze]

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' only sends standard output to file;
standard error still gets displayed on the console.  In a
Bourne-compatible shell (ash/bash/ksh/zsh), you can do 'cmd 2file' to 
send standard error (only) to file, 'cmd file' to send both standard 
out and standard error to file, 'cmd 21' to send standard error to
the same place as standard output, 'cmd 21 |less' to send that
output through less, etc.  csh/tcsh are less
powerful/flexible/forgiving here.

-- 
 _
/ \   Dad was reading a book called
|  David Maze | _Schroedinger's Kittens_.  Asexual
| [EMAIL PROTECTED]   |  reproduction?  Only one cat is in the box.
| http://donut.mit.edu/dmaze/ |   -- Abra Mitchell
\_/