Date: Wed, 15 Feb 1995 17:21:46 -0800 From: Bill Paul <wpaul> To: CVS-commiters, cvs-usrsbin Subject: cvs commit: src/usr.sbin/ypbind ypbind.c Message-ID: <199502160121.RAA21857@freefall.cdrom.com>
next in thread | raw e-mail | index | archive | help
wpaul 95/02/15 17:21:46 Modified: usr.sbin/ypbind ypbind.c Log: ypbind jumbo patch :) The existing ypbind exhibits some truly anti-social behavior. After initially establishing a binding with an NIS server, the following events take place: - ypbind waits for 60 seconds before trying to broadcast a ping again - after the 60 seconds expires, ypbind sends out broadcasts every 5 seconds come hell or high water. These broadcasts travel far and wide, even to NIS servers in other domains which dutifully log the packets even though they don't respond to them. This leads to lots of unnecessary traffic and bloated log files. This behavior has been fixed/changed. Here's what happens now: - We still broadcast every 5 seconds at startup, just like before. - Once bound, we send out packets once every 60 seconds to the server we're bound to AND NO ONE ELSE. - If we fail to receive a reply from our server within FAIL_THRESHOLD seconds, we assume our server has croaked and go back to broadcasting everywhere every 5 seconds again until somebody answers. FAIL_THRESHOLD is currently set to 20 seconds. Other fixes/improvements: - ypbind now logs 'server not responding' and 'server OK' messages where appropriate. Thanks to Thomas Graichen <graichen@omega.physik.fu-berlin.de> for reporting the problem and guilt-tripping me into fixing it. :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199502160121.RAA21857>