Yes, that does the trick, but it throws everything away. <br><br>But I'd like to have some of the output logged. Just not those startup lines.<br><br><br>I blame my suboptimal scripting strategy for the fact that I do some operation to 100 files by doing a for loop and then starting sac for each file. So in my logfile I have those Sac starting message 100 times.
<br><br>Removing it in the source might be worth a shot, but I didn't compile SAC myself in the first place as the binaries just worked.<br><br>Thanks,<br>Andreas<br><br><div><span class="gmail_quote">On 2/23/07, <b class="gmail_sendername">
Robert Casey</b> <<a href="mailto:rob@iris.washington.edu">rob@iris.washington.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br> Would sac > /dev/null behave properly? Perhaps if you have<br>your sac actions scripted, you don't need to see stdout. I don't<br>know if there is a dependency on SAC having control of the stdout
<br>pipe, though.<br><br> -Rob<br><br></blockquote></div><br>