Path: utzoo!utgpu!watmath!uunet!wuarchive!cs.utexas.edu!tut.cis.ohio-state.edu!ukma!cwjcc!cwns1!chet
From: chet@cwns1.CWRU.EDU (Chet Ramey)
Newsgroups: gnu.bash.bug
Subject: Re: core dump after interrupted username completion
Message-ID: <913@cwjcc.CWRU.Edu>
Date: 26 Nov 89 20:45:28 GMT
References: <8911251056.AA19997@slembe.uio.no>
Sender: news@cwjcc.CWRU.Edu
Reply-To: chet@cwns1.INS.CWRU.Edu (Chet Ramey)
Distribution: gnu
Organization: Case Western Reserve Univ. Cleveland, Ohio, (USA)
Lines: 22

In article <8911251056.AA19997@slembe.uio.no> hhe@IFI.UIO.NO writes:
>	First, I type part of an username and press TAB for completion.
>	The completion takes a while (our system has >2000 users), so
>	I press ^C and interrupt the completion.
>
>	Then, I write the username in full with a trailing slash and press
>	M-? (filename completion) to see the user's files. Core dump....

As reported by Paul Placeway here some time ago, this is a bug in YP,
not bash.  The Sun getpw* routines close and re-open a socket to the YP
server when they think they need to, which is not always correct.  Based
on this assumption, they inappropriately free resources, which is why bash
dumps core.

Chet Ramey


-- 
Chet Ramey
Network Services Group				"Where's my froggie?"
Case Western Reserve University
chet@ins.CWRU.Edu