If I use the executable sac (not compiled by my own), then when I use ,like
sac <<end
input
end
sac just stop there and do nothing, is this also sth related to 32-bit/64-bit? because the sac we got is generally compiled in 32-bit machine?
thanks for any help.
xinlei
-
Xinlei
If you add in the quit command, sac will return, otherwise it will hang.
And yes, this is on the list of things to fix, but it is not related
to the 64//32 bit issue.
sac <<end
input
quit
end
Cheers,
Brian Savage
savage<at>uri.edu
On Feb 27, 2007, at 3:55 PM, <xsun<at>uiuc.edu> <xsun<at>uiuc.edu> wrote:
If I use the executable sac (not compiled by my own), then when I
use ,like
sac <<end
input
end
sac just stop there and do nothing, is this also sth related to 32-
bit/64-bit? because the sac we got is generally compiled in 32-bit
machine?
thanks for any help.
xinlei
_______________________________________________
sac-help mailing list
sac-help<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/sac-help
-
I found the use of "here-document" not to be working at all (with Sac 100.1)
A workaround I use is putting the commands into a temporary file which can
then be called with SAC:
cat << eof > ./tmp
input
quit
eof
sac ./tmp
Andreas
On 2/28/07, Brian Savage <savage<at>uri.edu> wrote:
Xinlei
If you add in the quit command, sac will return, otherwise it will hang.
And yes, this is on the list of things to fix, but it is not related
to the 64//32 bit issue.
sac <<end
input
quit
end
Cheers,
Brian Savage
savage<at>uri.edu
-