Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!NORTHSTAR.DARTMOUTH.EDU!tobeye From: tobeye@NORTHSTAR.DARTMOUTH.EDU (Anthony Edwards) Newsgroups: comp.soft-sys.andrew Subject: Re: bug in help (ATK) Message-ID: Date: 8 Nov 90 18:35:11 GMT Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 28 Excerpts from nebraska: 8-Nov-90 bug in help (ATK) james@engrs.unl.edu (513) > So, what's this about the help bug? Dav tells me that it has to do with the socket that help opens??? The Scenario was: Somebody was rlogin'd > to my machine, and happened to be running help. I then did a help, and > it went to his window... (it was a little longer than that, but that's > what really happened). > Is this supposedly in the list of things to do for Andrew (if you know?) I was going to send it to info-andrew, but, if they already know about > it it'd probably be kind of pointless... > Thanks > James Why don't you send the bug to info-andrew any way. We told them awhile back (before patch 1) and I've never seen anything come of it. The problem with their code is that they start a socket on the machine. When you type 'help' again, it goes to the same help window rather than opening a new window - that's their feature. The misfeature is that you can only have one help socket per machine - it isn't per user but per machine. What they should do is incorporate the user's id into the socket name. Ah, instead of you sending them a note, I'll just cc them on this one. - Anthony