home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!sdd.hp.com!ux1.cso.uiuc.edu!moe.ksu.ksu.edu!matt.ksu.ksu.edu!news
- From: probreak@matt.ksu.ksu.edu (James Michael Chacon)
- Newsgroups: comp.windows.x.i386unix
- Subject: Re: Proposed addition to FAQ
- Date: 22 Jan 1993 06:28:56 -0600
- Organization: Kansas State University
- Lines: 20
- Message-ID: <1jopa8INNipm@matt.ksu.ksu.edu>
- References: <1jmibuINN4gs@fnnews.fnal.gov>
- NNTP-Posting-Host: matt.ksu.ksu.edu
- Keywords: startup problems, etc.
-
- mengel@dcdmwm.fnal.gov (Marc Mengel) writes:
-
- >We should mention in the FAQ that when starting the X server to debug
- >problems you should run "X >& errors" in csh or "X > errors 2>&1" because
- >the output to stdout/stderr gets lost when the server starts up. This is
- >fairly obvious once you think of it; but you can spend days not finding out you
- >don't have a default font if you don't think of it...
-
- >-------
- >Marc Mengel
- >mengel@fnal.fnal.gov
-
- This is true, and I use it if I need the info when I am in X. But, 90-100%
- of the time when I exit X the information is still sitting on the screen.
-
- One thing I do at school is redirect all output into a file and then mail it
- to myself when I exit. That way I can't forget about it in some obscure
- directory or something.
-
- James
-