Re: ** HEADS UP ** portmap daemon renamed to rpcbind
On Mon, Apr 09, 2001 at 08:49:59PM -0700, Rodney W. Grimes wrote: Question: Does the rpcbind program in -current have the same problem or has it already been fixed by whomever you imported the code from? (If it hasn't been fixed I'll be happy to fix it. I'm hoping it has, though). Given the length of time that this problem has existed some how I doubt it... I'm pretty sure it hasn't given that the Solaris NIS+ implementation (at least as of 2.6) actually embeded both the port and the IP address of the call back TCP port when making requests for large tables. I'm pretty sure it did this due to the fact that they were too lazy to select the sending IP. The really painful thing is that the IP port pair is encoded in ascii as dotted sextuples (123.124.125.126.32.98 = 123.124.125.126:8290). -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 PGP signature
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
Ok guys. I just had to fix a problem with portmap in -stable related to binding to specific IP addresses so replies to UDP packets come 'from' the proper IP address (for multi-homed hosts). Question: Does the rpcbind program in -current have the same problem or has it already been fixed by whomever you imported the code from? (If it hasn't been fixed I'll be happy to fix it. I'm hoping it has, though). -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
Ok guys. I just had to fix a problem with portmap in -stable related to binding to specific IP addresses so replies to UDP packets come 'from' the proper IP address (for multi-homed hosts). This has been a problem with portmap for as long as I can remember (back to the SunOS 3.5 days) and if you have finally fixed it WONDERFULL!!! I hope you have commited it, or well soon, to -stable, as this one has surely been one to send many a young admin screaming from his cubicle yelling ``but it should work, it really should just work''. Question: Does the rpcbind program in -current have the same problem or has it already been fixed by whomever you imported the code from? (If it hasn't been fixed I'll be happy to fix it. I'm hoping it has, though). Given the length of time that this problem has existed some how I doubt it... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
:I hope you have commited it, or well soon, to -stable, as this one has :surely been one to send many a young admin screaming from his cubicle :yelling ``but it should work, it really should just work''. Yah, it's in just under the wire. I was tearing my hair out today trying to figure out why NFS wasn't drilling through two firewalls to one of our exodus machines (for a /usr/src and /usr/obj mount). It took about an hour to finally figure out that there was nothing wrong with the firewalls and portmap on the inside was trying to respond with an internal (10.*) network address instead of the external IP address the portmap request came in on! I didn't check first because I just assumed portmap was being talked to over TCP -- but it isn't always. It's exactly the same issue that nfsd had, but worse because various rpc related utilities seem to use a half hazzard mix of tcp and udp connections.I'm really getting quite annoyed at the whole rpcbind/portmap mechanism, it would be nice to see the world un-adopt portmap and just go with hardwired ports. I'll be able to look at -current's rpcbind this weekend. Right now I'm trying to reproduce a socket related crash with a program Terry emailed me today, and there are two other people with 4.3-RC related crashes I've been trying to help track down over the last few daysd and not having much luck with. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
Peter Wemm([EMAIL PROTECTED])@2001.03.28/06:24:34(epoch+985757074s): FYI: SYNOPSIS portmap [-d] [-v] SYNOPSIS rpcbind [-dilLs] yup, so i think it makes sense, to have the daemon called rpcbind, since it would probably break other people's configuration after making world. /k -- die rechtschreibreform macht spas! KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
I do not. -v could easily be added to what is now rpcbind (even if it
was ignored). -d mean the same thing for both. there's then no reason
to change its name.
Well, my feeling on the matter, since everyone gets to have an opinion
today, is that we should stick with rpcbind: it's what everyone else who
uses TIRPC calls it (as well as the entire source code tree). Given that
it's not going to be MFC'd to RELENG_4, and everything in the universe is
changing in -CURRENT, this minor change to improve our compliance with
${THERESTOFTHEWORLD} isn't a big problem. However, for consistency, it
probably is the case that someone should go slap s/portmap/rpcbind/
s/PORTMAP/RPCBIND/ strategically through /etc and associated man pages.
Maybe adding a compatibility check that maps PORTMAP into RPCBIND, and
then prints a message on boot in the style of nsswitch.
Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED] NAI Labs, Safeport Network Services
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
Warner Losh([EMAIL PROTECTED])@Tue, Mar 27, 2001 at 12:40:18AM -0700: In message [EMAIL PROTECTED] Greg Lehey writes: : Play the ball, not the man. : : I don't have an objection to the change, I was just asking. And : "because System V does it this way" has never been a good answer for : us. And no, I'm not picking on Doug, just making a point. I see no reason why the name can't remain portmap. does it take parameters? then it would make sense to have it named rpcbind... /k -- "Dope will get you through times of no money better that money will get you through times of no dope." -- Gilbert Shelton KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
"Karsten W. Rohrbach" wrote: Warner Losh([EMAIL PROTECTED])@Tue, Mar 27, 2001 at 12:40:18AM -0700: In message [EMAIL PROTECTED] Greg Lehey writes: : Play the ball, not the man. : : I don't have an objection to the change, I was just asking. And : "because System V does it this way" has never been a good answer for : us. And no, I'm not picking on Doug, just making a point. I see no reason why the name can't remain portmap. does it take parameters? then it would make sense to have it named rpcbind... Pardon me being dense, but what does that have to do with anything? portmap took a -v flag, or are you talking about something different? -- Perhaps the greatest damage the American system of education has done to its children is to teach them that their opinions are relevant simply because they are their opinions. Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
Warner Losh wrote: In message [EMAIL PROTECTED] Greg Lehey writes: : Play the ball, not the man. : : I don't have an objection to the change, I was just asking. And : "because System V does it this way" has never been a good answer for : us. And no, I'm not picking on Doug, just making a point. I see no reason why the name can't remain portmap. My previous comment was mostly an attempt at humor, in case anyone missed that. :) I have no problem with keeping the name the same as it is in netbsd to make code sharing easier. If this were something that users interacted with directly I'd fight harder, but as it is portmap is basically always started from rc*. We'll have another round of pain from people who fail to properly update /etc, but we have enough land mines there already to make this point moot. Doug -- Perhaps the greatest damage the American system of education has done to its children is to teach them that their opinions are relevant simply because they are their opinions. Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
Doug Barton([EMAIL PROTECTED])@Tue, Mar 27, 2001 at 10:05:40AM -0800: "Karsten W. Rohrbach" wrote: Warner Losh([EMAIL PROTECTED])@Tue, Mar 27, 2001 at 12:40:18AM -0700: In message [EMAIL PROTECTED] Greg Lehey writes: : Play the ball, not the man. : : I don't have an objection to the change, I was just asking. And : "because System V does it this way" has never been a good answer for : us. And no, I'm not picking on Doug, just making a point. I see no reason why the name can't remain portmap. does it take parameters? then it would make sense to have it named rpcbind... Pardon me being dense, but what does that have to do with anything? portmap took a -v flag, or are you talking about something different? the idea is, that if rpcbind takes parameters different from portmap it would make sense to call rpcbind rpcbind because people's boxes will start to barf when rpcbind is called portmap, they make world, and skip reading the rpcbind paragraph in UPDATING ;-) does this make sense? /k -- Hugh Hefner is a virgin. KR433/KR11-RIPE -- http://www.webmonster.de -- ftp://ftp.webmonster.de To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
"Karsten W. Rohrbach" wrote: the idea is, that if rpcbind takes parameters different from portmap it would make sense to call rpcbind rpcbind because people's boxes will start to barf when rpcbind is called portmap, they make world, and skip reading the rpcbind paragraph in UPDATING ;-) does this make sense? Yes. "Takes parameters different from portmap," makes much more sense than "takes parameters." :) Thanks, Doug -- Perhaps the greatest damage the American system of education has done to its children is to teach them that their opinions are relevant simply because they are their opinions. Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
On Mon, Mar 26, 2001 at 05:24:14PM +0930, Greg Lehey wrote: On Sunday, 25 March 2001 at 23:48:10 -0800, Doug Barton wrote: Greg Lehey wrote: On Wednesday, 21 March 2001 at 10:44:38 -0800, David O'Brien wrote: The Portmapper binary has been renamed from `portmap' to `rpcbind'. Why? So we can be more like sysV This is good? If it's the best path to NFS over IPv6, which seems to be the issue, then sure it's good. Play the ball, not the man. -- Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
On Monday, 26 March 2001 at 18:19:06 +1000, Andrew Reilly wrote: On Mon, Mar 26, 2001 at 05:24:14PM +0930, Greg Lehey wrote: On Sunday, 25 March 2001 at 23:48:10 -0800, Doug Barton wrote: Greg Lehey wrote: On Wednesday, 21 March 2001 at 10:44:38 -0800, David O'Brien wrote: The Portmapper binary has been renamed from `portmap' to `rpcbind'. Why? So we can be more like sysV This is good? If it's the best path to NFS over IPv6, which seems to be the issue, then sure it's good. Play the ball, not the man. I don't have an objection to the change, I was just asking. And "because System V does it this way" has never been a good answer for us. And no, I'm not picking on Doug, just making a point. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
In message [EMAIL PROTECTED] Greg Lehey writes: : Play the ball, not the man. : : I don't have an objection to the change, I was just asking. And : "because System V does it this way" has never been a good answer for : us. And no, I'm not picking on Doug, just making a point. I see no reason why the name can't remain portmap. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
On Wednesday, 21 March 2001 at 10:44:38 -0800, David O'Brien wrote: The Portmapper binary has been renamed from `portmap' to `rpcbind'. Why? Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
* Greg Lehey [EMAIL PROTECTED] [010325 15:33] wrote: On Wednesday, 21 March 2001 at 10:44:38 -0800, David O'Brien wrote: The Portmapper binary has been renamed from `portmap' to `rpcbind'. Why? We've upgraded to Sun's TIRPC code, this includes rpcbind as a replacement for portmapper. -- -Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]] Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ** HEADS UP ** portmap daemon renamed to rpcbind
Greg Lehey wrote: On Wednesday, 21 March 2001 at 10:44:38 -0800, David O'Brien wrote: The Portmapper binary has been renamed from `portmap' to `rpcbind'. Why? So we can be more like sysV -- Perhaps the greatest damage the American system of education has done to its children is to teach them that their opinions are relevant simply because they are their opinions. Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
** HEADS UP ** portmap daemon renamed to rpcbind
The Portmapper binary has been renamed from `portmap' to `rpcbind'. The name change was taken care of in /etc/defaults/rc.conf and in the auto-dependacy code in /etc/rc. HOWEVER, you may need to edit your /etc/hosts.allow and make the name change there. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
