From owner-freebsd-bugs Wed Aug 14 17:03:43 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA04019 for bugs-outgoing; Wed, 14 Aug 1996 17:03:43 -0700 (PDT) Received: from print.elec.uq.edu.au (root@print.elec.uq.edu.au [130.102.96.6]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA04014 for ; Wed, 14 Aug 1996 17:03:40 -0700 (PDT) Received: (from clary@localhost) by print.elec.uq.edu.au (8.6.12/8.6.12) id KAA02318 for freebsd-bugs@freebsd.org; Thu, 15 Aug 1996 10:03:28 +1000 From: Clary Harridge Message-Id: <199608150003.KAA02318@print.elec.uq.edu.au> Subject: rarpd stops working on FreeBSD 2.1.5-RELEASE To: freebsd-bugs@freebsd.org Date: Thu, 15 Aug 1996 10:03:25 +1000 (EST) X-Mailer: ELM [version 2.4ME+ PL12 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk There is a bug which stops rarpd from responding to rarp requests When rarpd is configured and running it responds OK to rarp requests, however after some hours is stops responding. The only way to have FreeBSD as a reliable rarp server is to kill the rarp daemon regularly with cron and rerun rarpd. I suspect that the time at which rarp stops working may be related to the number of requests previously received. -- regards Dept. of Electrical Engineering, Clary Harridge University of Queensland, QLD, Australia, 4072 Phone: +61-7-3365-3636 Fax: +61-7-3365-4999 INTERNET: clary@elec.uq.edu.au