stergios@Jessica.stanford.edu (stergios marinopoulos) (02/01/89)
On sun4 w/ os 4.01 the following script starts ok, but graph just prints a "se" and stops. I thought "THEEND" would define the end of the standard input and cause graph to print out its plot(5) info. Any ideas? #!/bin/csh -f graph -a -l My_label <<THEEND 1 10 2 20 3 30 4 40 5 60 6 60 7 70 8 80 9 90 THEEND stergios
hiebeler@rpics (Dave Hiebeler) (02/01/89)
In article <171@Portia.Stanford.EDU> stergios@Jessica.stanford.edu (stergios marinopoulos) writes: > >On sun4 w/ os 4.01 the following script starts ok, but graph just >prints a "se" and stops. I thought "THEEND" would define the >end of the standard input and cause graph to print out its >plot(5) info. Any ideas? > >#!/bin/csh -f >graph -a -l My_label <<THEEND >...[coordinate-stuff deleted] >8 80 >9 90 >THEEND I noticed a few months ago that "graph" does not work on our Sun 4/280 running 4.0. (It has since gotten the 4.0.1 fixes, but I haven't tried it again since then). I compared the output of "graph" on the sun-4 to the output from a sun-3, and it seems like the 4 just puts a header and a tail on the output, but with nothing in between. I didn't study it extensively, however; I just always pop my stuff over to a Sun-3 to "graph" it. (Inconvenient, yes, but tolerable). I don't know if the "plot" commands (i.e. "crtplot", etc) have any trouble. Has anyone else noticed this problem with "graph" under 4.0? Or is it already common knowledge? ---- Dave Hiebeler Internet: hiebeler@cs.rpi.edu (preferred address) R.D. Box 225A userfrzk%mts@itsgw.rpi.edu Chatham, NY 12037 Bitnet: userfrzk@rpitsmts.bitnet "xue zai xao" "Off we go, into the wilds you ponder..."
guy@auspex.UUCP (Guy Harris) (02/08/89)
> I noticed a few months ago that "graph" does not work on our >Sun 4/280 running 4.0. (It has since gotten the 4.0.1 fixes, >but I haven't tried it again since then). Try it now. 4.0.1 purports, in fact, to have two fixes to "graph" on Sun-4s, one of which is supposed to fix a bug described as "graph(1G) infinite loops". I think there was a compiler bug that caused this.