From owner-freebsd-hackers Tue Jan 7 10:10:14 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA02312 for hackers-outgoing; Tue, 7 Jan 1997 10:10:14 -0800 (PST) Received: from deliverator.io.com (deliverator.io.com [199.170.88.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA02307 for ; Tue, 7 Jan 1997 10:10:11 -0800 (PST) Received: from bermuda.io.com (sszabo@bermuda.io.com [199.170.88.7]) by deliverator.io.com (8.8.4/8.8.4) with ESMTP id LAA29622; Tue, 7 Jan 1997 11:26:13 -0600 (CST) Received: from localhost (sszabo@localhost) by bermuda.io.com (8.8.4/8.8.4) with SMTP id LAA02357; Tue, 7 Jan 1997 11:26:09 -0600 (CST) X-Authentication-Warning: bermuda.io.com: sszabo owned process doing -bs Date: Tue, 7 Jan 1997 11:26:09 -0600 (CST) From: Stephan Szabo To: Tom Samplonius cc: freebsd-hackers@freebsd.org Subject: Re: Question about ypbind In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 6 Jan 1997, Tom Samplonius wrote: > > On Mon, 6 Jan 1997, Stephan Szabo wrote: > > > > > We have been attempting to install NIS on a FreeBSD 2.1.5R system > > and have run into a problem with ypbind. When it is run, it dies on a > > SIGSEGV. Going through gdb a bit gave us the following: > > Program received signal SIGSEGV, Segmentation fault. > > [rest left off for brevity] > > Works fine for me. > > What params are you running ypbind with? What kind of server is ypbind > binding too (or trying to bind to)? Originally we were running ypbind -s, and then ypbind with no parameters to see if that would work. The server is another FreeBSD 2.1.5R system. The strange thing was that it had worked for a little while, and then stopped working, but no changes were made to our knowledge to the configuration of either machine. Stephan Szabo