From owner-freebsd-hackers Sun Feb 21 0:43: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 3BB5610E6E for ; Sun, 21 Feb 1999 00:43:02 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id AAA18826; Sun, 21 Feb 1999 00:42:51 -0800 (PST) (envelope-from dillon) Date: Sun, 21 Feb 1999 00:42:51 -0800 (PST) From: Matthew Dillon Message-Id: <199902210842.AAA18826@apollo.backplane.com> To: Kevin Day Cc: hackers@FreeBSD.ORG Subject: Re: ESTALE the best approach? References: <199902210737.BAA21850@home.dragondata.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Anyone have any comments on this? Only cron is maintained here. All the other programs are maintained by their authors or groups elsewhere. There isn't much we can do about them. Also, most of these are IRC tools. IRC tools are notoriously badly written. To give you an example, there was an eggdrop floating around for months about a year ago which had hacked in signal(SIGSEGV, handler) to make the program ignore segv violations because the programmer who made the mod was too clueless to understand what sigsegv actually meant. -Matt Matthew Dillon : :I've found that at least these programs cannot deal with ESTALE in some :manner: : :cron :apache httpd :eggdrop :afio :bnc :ircii :bitchx : : : :Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message