Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!pyrdc!gmu90x!dolqci!vrdxhq!grebyn!rriwro!martin
From: martin@rriwro.UUCP (Martin Hobson)
Newsgroups: comp.unix.xenix
Subject: Re: Bad hertz value
Message-ID: <34@rriwro.UUCP>
Date: Wed, 9-Sep-87 22:45:37 EDT
Article-I.D.: rriwro.34
Posted: Wed Sep  9 22:45:37 1987
Date-Received: Sat, 12-Sep-87 08:51:34 EDT
References: <381@mrecvax.UUCP> <209@peaks.UUCP>
Reply-To: martin@.UUCP (Martin Hobson)
Organization: Riverside Research, Arlington VA
Lines: 34
Keywords: error

In article <209@peaks.UUCP> bdw@peaks.UUCP (bruce welker) writes:
>In article <381@mrecvax.UUCP>, tron@mrecvax.UUCP (Carlos Mendioroz) writes:
>> I've been porting some packages (news, smail, ...) to SCO XENIX V 2.1.3
>> and I'm getting this 'Bad herts value' error from some programs; 
>> [ more stuff ]
>
>	I've seen this problem at work while starting up nested vi's while
>	logged in from an XT. Iwould be interested in whatever light can
>	be thrown on it...
>
>		bdw
>		as ...!hao!boulder!peaks!bdw


We ran into this problem when doing things like 'su - user' from the
root account, which would result in large numbers of 'Bad Hertz Value'
messages being generated, garbled output, and failing programs. We traced
this problem to a failure to declare the environment variable 'HZ' prior
to starting up a csh process.

It appears that csh absolutely MUST have a value declared for HZ, or it
will break. We fixed the problem by adding the command:

setenv HZ 50

to our /etc/cshrc file - which is invoked for a login c-shell only. So,
check your environment to be sure the HZ variable is set correctly.

Hope this helps,
-- 
Martin Hobson                                  |  "It's hard to believe
Riverside Research - Computer Systems Center   |   grown-ups do this for
(703)-247-3680                                 |   a living" - anon.
UUCP:  seismo!decuac!grebyn!rriwro!martin      |