From owner-freebsd-current  Thu Oct 24 11:32:34 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA12649
          for current-outgoing; Thu, 24 Oct 1996 11:32:34 -0700 (PDT)
Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA12641
          for <current@FreeBSD.org>; Thu, 24 Oct 1996 11:32:30 -0700 (PDT)
Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.7.5/8.7.3) id LAA07909; Thu, 24 Oct 1996 11:31:26 -0700 (PDT)
From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
Message-Id: <199610241831.LAA07909@GndRsh.aac.dev.com>
Subject: Re: /etc/rc* stuff
In-Reply-To: <199610241748.TAA13931@grumble.grondar.za> from Mark Murray at "Oct 24, 96 07:48:46 pm"
To: mark@grondar.za (Mark Murray)
Date: Thu, 24 Oct 1996 11:31:26 -0700 (PDT)
Cc: wpaul@skynet.ctr.columbia.edu, current@FreeBSD.org
X-Mailer: ELM [version 2.4ME+ PL25 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> I wrote that rndcontrol(8) program, so I'll fix it. It is a little too
> chatty by default. That will fix the extra `echo "."'
> 

Eitherway, the correct fix is to move the very last ``echo .'' into the
if block.


> M
> 
> Bill Paul wrote:
> > Just a couple of small nits:
> > 
> > - At the very end of /etc/rc.i386, we have this:
> > 
> > [begin snippage]
> > echo '.'
> > 
> > # interrupts for /dev/random device
> > if [ "X${rand_irqs}" != X"NO" ] ; then
> >         echo -n 'entropy source: '
> >         rndcontrol ${rand_irqs}
> > fi
> > 
> > echo '.' # probably bogus
> > [end snippage]
> > 
> >   The 'probably bogus' comment is true: if you don't have rand_irqs set
> >   to anything, you get an extra '.' printed on a line all by itself.
> >   This has bugged me for a while. (I'm funny that way.) What's the correct
> >   way to fix this? Should the entropy source message be part of the
> >   '386 specific' config messages or should it be a seperate caterory,
> >   and thus be on a line by itself? Put another way, should the first
> >   "echo '.'" go away, or should the 'probably bogus' one be moved inside
> >   the if/fi clause?
> > 
> > - Even though we have rpc.lockd and rpc.statd in the tree now, there
> >   are no knobs for it in /etc/sysconfig or /etc/rc. Shouldn't we be
> >   be starting them if NFS is turned on?
> > 
> > -Bill
> > 
> > -- 
> > =============================================================================
> > -Bill Paul            (212) 854-6020 | System Manager, Master of Unix-Fu
> > Work:         wpaul@ctr.columbia.edu | Center for Telecommunications Research
> > Home:  wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
> > =============================================================================
> >  "If you're ever in trouble, go to the CTR. Ask for Bill. He will help you."
> > =============================================================================
> --
> Mark Murray
> 46 Harvey Rd, Claremont, Cape Town 7700, South Africa
> +27 21 61-3768 GMT+0200
> Finger mark@grondar.za for PGP key
> 


-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation, Inc.                   Reliable computers for FreeBSD