Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!mips!swrinde!sdd.hp.com!news.cs.indiana.edu!nstn.ns.ca!aucs.acadiau.ca!peter
From: peter@aucs.AcadiaU.ca (Peter Steele)
Newsgroups: comp.unix.questions
Subject: Any RARP experts out there?
Message-ID: <1991May31.142720.9792@aucs.AcadiaU.ca>
Date: 31 May 91 14:27:20 GMT
Reply-To: peter@aucs.acadiau.ca (Peter Steele)
Distribution: na
Organization: School of Computer Science, Acadia Univ., Nova Scotia
Lines: 19

We have a peculiar problem we can't seem to resolve. We want to
set up rarpd on another machine as a backup in case our current
rarpd server goes down. Presently, rarpd is running on an SLC (owl)
and is getting its ethers and hosts data over NIS from a Sun-4. This
is working fine, except if the Sun-4 goes down, so does owl's NIS
link to the Sun-4 and rarp requests start to fail.

We have another SLC (pony) which has its own local hard disk and is
not running NIS. I've brought up rarpd on this machine and have copied
the ethers and hosts files from the Sun-4. However, if we kill the
rarpd daemon on owl, rarp requests start to fail, even though rarpd
is running on pony.

I've done some experiments but I'm not getting anywhere. Can anyone
suggest what I should do to find out why rarp requests are not
being serviced by one SLC but is by another? Thanks.
-- 
Peter Steele  Postmaster  peter.steele@acadiau.ca   Tel: 902-542-2201
Software Analyst, Acadia University, Wolfville, NS  Fax: 902-542-7224