>In any case, try running the command like this:
>top 2>errors.out
>
>Then, stop the process by doing a Ctrl+C for instance, and take a look at
>the contents of the errors.out file which should then contain a printout
>of the errors the system ran into. I use this trick pretty much every
>time I run into a problem, and so far it has proven to be extremely
>helpful.
In this case it doesn't do any good to do a ^C, as the program stops on
its own, and also, since there are errors, they would appear on the screen.
But, just for the hell of it, I did an output into a file. When I cat'd
the file, the same thing happened, i.e., the screen was cleared. But, the
file was 38 bytes long. Editing the file produces:
bad data in /var/run/utmp^[[H^[[J^[[H^[[1m
The stupid program clears the screen so the error can't be seen. A result
of clearing the screen when it normally finishes.
I wonder when my utmp file got corrupted. :-(
>Again, please correct me if I'm wrong, since I'm here to help when I can
>and learn from the gurus. ;-)
>Nitebirdz
MB
--
e-mail: [EMAIL PROTECTED]
Bart: Hey, why is it destroying other toys? Lisa: They must have
programmed it to eliminate the competition. Bart: You mean like
Microsoft? Lisa: Exactly. [The Simpsons - 12/18/99]
Visit - URL:http://www.vidiot.com/ (Your link to Star Trek and UPN)
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
