[EMAIL PROTECTED] wrote:
>Hi,
>
>There are many logs(debug information) when fgfs is initializing/running, but the
>logs go fast in the terminal and it is hard to read them. I use fgfs > file, but the
>content in the file is not the logs.:-).
>Is there any way to dump them into a file for later analysizing?
>
>
For [t]csh I think you want to do "fgfs >& logfile"
For [ba]sh you want to do "fgfs > logfile 2>&1"
The issue here is that log messages are getting dumped to stderr, not
stdout. Running "command > file" only captures stdout. These more
complex forms also capture stderr to the same file.
I'm tempted to post the following "fun with unix" link, but it's
extremely dated, both in terms of it's politics, and a lot of these
don't work the same with current versions of unix ... but go dredge up
an old Sparc 5 of mid 90's vintage and I bet they will all work exactly
as described ...
http://www.joke-archives.com/computers/funwithunix.html
Regards,
Curt.
--
Curtis Olsonhttp://www.flightgear.org/~curt
HumanFIRST Program http://www.humanfirst.umn.edu/
FlightGear Project http://www.flightgear.org
Unique text:2f585eeea02e2c79d7b1d8c4963bae2d
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
