From owner-freebsd-bugs Sun Feb 26 03:38:58 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id DAA20080 for bugs-outgoing; Sun, 26 Feb 1995 03:38:58 -0800 Received: from alpha.enc.edu (alpha.enc.edu [199.93.252.250]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id DAA20074 for ; Sun, 26 Feb 1995 03:38:56 -0800 Received: by alpha.enc.edu (AIX 3.2/UCB 5.64/4.03 rev 11/30/94) id AA36020; Sun, 26 Feb 1995 06:36:51 -0500 Date: Sun, 26 Feb 1995 06:36:51 -0500 (EST) From: "Charles N. Owens" To: bugs list FreeBSD Subject: Bootpd bug in 2.0-951222-SNAP Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: bugs-owner@FreeBSD.org Precedence: bulk Using that late December Snapshot (I'm not sure if I have the date right), I've noticed some nasty behaviour with bootpd. It seems to work fine initially, but within a few hours of it's startup it begins to flake out. It stops responding to some addresses, and SEEMS to interfere with bootp service running on a different (non-FreeBSD) server. I was able to achieve a band-aid solution by having cron kill and restart bootpd every hour, but this is less than optimum. If this has been fixed, the please let me know. I would think that we'd want to get this fixed before the 2.1 release. Bootp is (in my opinion) a pretty fundamental service for a unix box. Please reply via email, as I do not subscribe to this list. Thanks, --- ------------------------------------------------------------------------- Charles Owens Email: owens@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X -------------------------------------------------------------------------