On Fri, Aug 31, 2012 at 1:14 AM, Garrett Cooper <yanegomi_at_gmail.com> wrote: > On Fri, Aug 31, 2012 at 1:05 AM, Борис Самородов <bsam_at_passap.ru> wrote: >> Hi All, >> >> I've it at 9.1-PRERELEASE and I've got a chance to test at CURRENT. >> It's the same (mind a line with "udp4 *:768" at sockstat info): >> ----- >> % sockstat -4l | grep rpcbind >> >> % grep rpcbind /etc/rc.conf.local >> rpcbind_flags="-h 192.168.119.6" >> rpcbind_enable="YES" >> >> % sudo /etc/rc.d/rpcbind start >> Starting rpcbind. >> >> % sockstat -4l | grep rpcbind >> root rpcbind 4265 9 udp4 127.0.0.1:111 *:* >> root rpcbind 4265 10 udp4 192.168.119.6:111 *:* >> root rpcbind 4265 11 udp4 *:768 *:* >> root rpcbind 4265 12 tcp4 127.0.0.1:111 *:* >> root rpcbind 4265 13 tcp4 192.168.119.6:111 *:* >> >> % uname -a >> FreeBSD bsam.wart.ru 10.0-CURRENT FreeBSD 10.0-CURRENT #31 r239793: Wed Aug >> 29 03:00:30 SAMT 2012 bsam_at_bsam.wart.ru:/usr/obj/usr/src/sys/BBX i386 > > This is a generic rc(5) bug: ... > Please file a PR against rc ASAP. Grr... that's right. /etc/defaults/rc.conf overwrites anything set in the environment. Please ignore the previous email. And FWIW, rpcbind doesn't in fact bind to specific addresses like you claim: $ sockstat -4 | grep rpcbind root rpcbind 1060 9 udp4 127.0.0.1:111 *:* root rpcbind 1060 10 udp4 192.168.20.2:111 *:* root rpcbind 1060 11 udp4 *:974 *:* root rpcbind 1060 12 tcp4 127.0.0.1:111 *:* root rpcbind 1060 13 tcp4 192.168.20.2:111 *:* Thanks, -GarrettReceived on Fri Aug 31 2012 - 06:22:20 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:30 UTC