Path: utzoo!attcan!uunet!world!decwrl!hayes.ims.alaska.edu!accuvax.nwu.edu!casbah.acns.nwu.edu!rr
From: roger@eccles.psych.nwu.edu (Roger Ratcliff)
Newsgroups: comp.unix.aix
Subject: Re: /usr/etd/biod 0 'is very bad for your health'
Keywords: biod, nfs, smit
Message-ID: <1028@casbah.acns.nwu.edu>
Date: 14 Nov 90 15:34:36 GMT
References: <12325@fsg.UUCP>
Sender: news@casbah.acns.nwu.edu
Reply-To: roger@eccles.psych.nwu.edu (Roger Ratcliff)
Organization: Northwestern University
Lines: 15

Our IBM SE managed to suggest setting the number to zero over the phone
then had to leave.  One of our local people suggested loggining in
as soon as a login was available (as root) then doing

exec mv /etc/rc.nfs /etc/rc.nfs.no

i.e., moving out the offending file that sets the number of biod to
zero then reboot and you are in to alter the file and set # biod to
something nonzero.

By the way, each system should come with a big warning message:

NEVER EVER mv libc.a.  You usually have to reload the system.

Roger