[SAC-HELP] start sac "silently"

[Keith Richards-Dinger]

How about just piping SAC's stdout through a couple of
grep commands:

sac | grep -v "Version 100.1" | grep -v "Copyright" > logfile

And maybe you want to pipe stderr instead of or in
addition to stdout.

-Keith

On 2/22/07, andreas wessel <awbochum at gmail.com> wrote:
> 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
> >
> >
>
>
> _______________________________________________
> sac-help mailing list
> sac-help at iris.washington.edu
> http://www.iris.washington.edu/mailman/listinfo/sac-help
>
>