bernt@kvatro.no (Bernt Marius Johnsen) (06/12/91)
I do the following command on a VAX/VMS using TCP/IP software from Wollongong: > rsh durin -l chipsy (cd v12_dev; tar -xvf ../VHM.tar; rm ../VHM.tar) I get the following output from SCO 3.1.1: > tar: blocksize = 20 [... file list deleted ...] > Bad Hertz Value > Using 100 from <sys/param.h> > Bad Hertz Value > Using 100 from <sys/param.h> Everything seems to be ok, but I don't like the "Bad Hertz Value" message. Does someone know why I get this message? The same rsh command is completely ok when I change from our SCO computer (Compaq 386/20e) to a Sun386i. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Bernt M. Johnsen, Senior Systems Engineer KVATRO AS, Pirsenteret, N-7005 Trondheim, NORWAY E-mail: bernt@kvatro.no / Phone: +47 7 520090 / Fax: +47 7 520140 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Bernt M. Johnsen, Senior Systems Engineer KVATRO AS, Pirsenteret, N-7005 Trondheim, NORWAY E-mail: bernt@kvatro.no / Phone: +47 7 520090 / Fax: +47 7 520140 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bernt@kvatro.no (Bernt Marius Johnsen) (06/12/91)
I do the following command on a VAX/VMS using TCP/IP software from Wollongong: > rsh durin -l chipsy (cd v12_dev; tar -xvf ../VHM.tar; rm ../VHM.tar) I get the following output from SCO 3.1.1: > tar: blocksize = 20 [... file list deleted ...] > Bad Hertz Value > Using 100 from <sys/param.h> > Bad Hertz Value > Using 100 from <sys/param.h> Everything seems to be ok, but I don't like the "Bad Hertz Value" message. Does someone know why I get this message? The same rsh command is completely ok when I change from our SCO computer (Compaq 386/20e) to a Sun386i. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Bernt M. Johnsen, Senior Systems Engineer KVATRO AS, Pirsenteret, N-7005 Trondheim, NORWAY E-mail: bernt@kvatro.no / Phone: +47 7 520090 / Fax: +47 7 520140 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
jim@shograf.com (jim morris) (06/15/91)
From article <BERNT.91Jun12112411@freya.kvatro.no>, by bernt@kvatro.no (Bernt Marius Johnsen): > I do the following command on a VAX/VMS using TCP/IP software from > Wollongong: > >> rsh durin -l chipsy (cd v12_dev; tar -xvf ../VHM.tar; rm ../VHM.tar) > > I get the following output from SCO 3.1.1: > >> tar: blocksize = 20 > [... file list deleted ...] >> Bad Hertz Value >> Using 100 from <sys/param.h> This is a bug that SCO has documented for at least the last 2 releases of TCP/IP. They don't seem to want to fix it. The latest release notes (1.1.3) have downgraded all the TCP/IP BUGS!! (including this one) to "INCONVENIENCES" SCO SUPPORT .... THIS IS A DAMN BUG not an inconvenience!! It only happens if your login shell on SCO is csh, if you change it to sh it works fine. A NOTE TO SCO... Please FIX your BUGS, don't call them inconveniences!!! Sloppy programming and QA is not easily swept under the carpet!!! SCO users you could try ESIX or Interactive, I know ESIX try to fix their bugs. (At least they used to last year). I can't see how interactive could be worse! I have never seen this bug any any other system. -- Jim Morris, E-Mail: jim@shograf.com Voice: (415) 903-3887 _ SHO graphics. Practical PEX
rvdp@sow.econ.vu.nl (Ronald van der Pol) (06/20/91)
bernt@kvatro.no (Bernt Marius Johnsen) writes:
& Everything seems to be ok, but I don't like the "Bad Hertz Value"
& message. Does someone know why I get this message? The same rsh
& command is completely ok when I change from our SCO computer (Compaq
& 386/20e) to a Sun386i.
That is the difference between the PC market and the workstation
market. One has network support fully integrated, the other not...
--
Ronald van der Pol
rvdp@sow.econ.vu.nl
rvdp@cs.vu.nlgeorg@norisc.UUCP (Georg Biehler) (06/21/91)
jim@shograf.com (jim morris) writes: > > > > I get the following output from SCO 3.1.1: > > > >> tar: blocksize = 20 > > [... file list deleted ...] > >> Bad Hertz Value > >> Using 100 from <sys/param.h> > Just to put off the heat: Turn to root and edit "/etc/cshrc". Put in a line "setenv HZ 100". This will fix all your problems. -Georg