Date: Sat, 18 Aug 2001 16:34:16 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: stable@freebsd.org Subject: Minor issue with portmap=NO vs 'ypwhich' Message-ID: <p05101001b7a47eae6226@[128.113.24.47]>
next in thread | raw e-mail | index | archive | help
This will probably seem like a dumb thing to report, but I'll mention it in case someone who knows about yp/NIS would want to comment on it. My .bashrc file is (pretty much) the same on the many different platforms that I work on, and as a matter of trouble-shooting on SOME of those platforms I do a 'ypwhich' in it. Most of those platforms do NOT run yp, but I still run it on all platforms and just catch the error for those hosts which are not running yp. I am NOT running yp on freebsd. With this week's -stable, /etc/defaults/rc.conf changes portmap_enable to be "NO". With portmap_enable off, ypwhich still errors out as it does with portmap_enable on, but it takes it much longer to figure out that yp is not running (30 seconds? 60 seconds?). So, I realize it's probably dumb to care about how quickly ypwhich completes on a machine which is NOT running yp, but it is a noticeable change, so I thought I'd mention it. It is easy for me to just fix my .bashrc so I wouldn't hit that long delay, or to just turn on portmap, for that matter (which is what I've done for the moment). So, this isn't a big issue for me. I'm just wondering if there are any other effects which might be more significant for other users. -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05101001b7a47eae6226>