[SAC-HELP] start sac "silently"

[andreas wessel]

Yes, that does the trick, but it throws everything away.

But I'd like to have some of the output logged. Just not those startup
lines.


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.

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.

Thanks,
Andreas

On 2/23/07, Robert Casey <rob at iris.washington.edu> wrote:
>
>
>         Would    sac > /dev/null   behave properly?  Perhaps if you have
> your sac actions scripted, you don't need to see stdout.  I don't
> know if there is a dependency on SAC having control of the stdout
> pipe, though.
>
>         -Rob
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iris.washington.edu/pipermail/sac-help/attachments/20070223/b1653f69/attachment.html>