On Mon, 2009-10-26 at 16:58 -0500, flyfisherman wrote: > tried that. tried both at same time and stdout and stderr separately. > it creates the file but they are empty. in the console the info > scrolls by too fast to read and you can't scroll back up. i can read > the last 20 or 25 lines in the console, but that doesn't have what i > need. since the data is there i don't understand why it won't log it. > Do a cut'n paste to post the complete command exactly as you typed it in. Just showing a snippet of it doesn't let us see what else in the command may be causing the problem. Martin
