From owner-freebsd-security Mon Sep 21 11:22:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA28151 for freebsd-security-outgoing; Mon, 21 Sep 1998 11:22:18 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from mail.gamespot.com (ns2.gamespot.com [206.169.18.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA28146 for ; Mon, 21 Sep 1998 11:22:15 -0700 (PDT) (envelope-from ian@gamespot.com) Received: from localhost (ian@localhost) by mail.gamespot.com (8.9.0/8.9.0) with SMTP id LAA13411 for ; Mon, 21 Sep 1998 11:20:40 -0700 (PDT) Date: Mon, 21 Sep 1998 11:20:39 -0700 (PDT) From: Ian Kallen To: freebsd-security@FreeBSD.ORG Subject: corrupted libwrap? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I maintain a machine on a network that's poorly staffed. On occasion, the hub that it's connected to will get unplugged for a long time, in this case, a day. Meantime, the machine was power cycled. So when the machine is powered back up and the hub is powered up (is that so much to ask?), the system complains about libwrap, like so: % telnet freebsd.hopeless.net Trying 192.169.1.55... Connected to freebsd.hopeless.net. Escape character is '^]'. ld.so failed: Can't find shared library "libwrap.so.7.6" Connection closed by foreign host. But libwrap.so.7.6 _is_ in /usr/local/lib -- I can rememedy it by reinstalling tcp wrappers (or maybe there's some mumbo jumbo that's needed with ld?). It's just annoying and it's happened twice since upgrading 2.2.2 to 2.2.7. Has anybody else seen and fixed this? I have a feeling the people at this facility are going to be incompetent for the foreseeable future, randomly unplugging things and other stupid antics, but I'd like to keep tcpd on without it being susceptible to this. -Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message